Details from OCLC: Library of Congress scripts

Language Support and Display Optimization

Record Manager and Connexion support numerous languages for cataloging. 

For optimal display in Connexion, we recommend using either Noto Sans or Nirmala UI font. Please review the recommendations below based on your Connexion client version and working language/script. 

Other fonts may provide a similar experience in Connexion, and OCLC's font recommendation does not suggest that other fonts would not work with a given language/script. If you experience display issues with a recommended font or find one that works better for a particular script, please contact OCLC Support so we can continue to improve our documentation and the experience of catalogers. 

Recommended font for Connexion 3.1 users for all languages/scripts: Noto Sans

* Please review the Known Issues for these fonts

If you do not have Google Noto Sans, it is free to download. For additional information about installing Google Noto Sans please see Google Noto fonts for Windows.

If you do not have Abyssinica SIL, it is free to download. For additional information about installing Abyssinica SIL, please see Abyssinica SIL Resource page.

Known Issues

OCLC has identified some characters that do not pass validation. Please see Unsupported characters for more information.

In Connexion 2.63, the double dagger delimiter character may display as an empty rectangle in some fields when using the Abyssinica SIL font. Despite its appearance, the character functions normally. It is still recognized as a delimiter, passes validation, and exports to UTF-8 Unicode format as expected. It can be entered using the keyboard shortcut "CTRL +D" or the Diacritics and Special Characters dialog. To visually confirm the character, switch your font to one that supports it, such as Nirmala UI or Noto Sans. 

Workarounds for entering unsupported characters

The workarounds described below can work as alternatives to entering nonsupported characters. Please consider the options carefully to choose the one that would best support your library.

Enter an equivalent character with a note

Enter a supported character that is visually or phonologically equivalent to the unsupported character, and add a note indicating that the form on the source differs from what was entered due to current system limitations. Example: If you want to use 𑪴, you could enter ᕹ (U+1579) (which represents the same sound in many contexts) and include the note: Character appears on the source as 𑪴; recorded here as ᕹ due until validation is upgraded.

Bracketed placeholder (most stable)

Entering the romanized name of the character in brackets avoids blocking errors and supports consistent downstream exchange. This may be less practical if many characters are affected. Example: [CANADIAN SYLLABICS NATTILIK HA].

Use transliteration/romanized form of script only

If appropriate for the record and consistent with your cataloging policy, you may choose to supply only the transliterated or romanized form for the affected data element and defer adding the script form until validation support is updated.

Hex entry via Connexion

Enter the hexadecimal value via Connexion, noting that in Record Manager, actions that refresh the record convert the hex reference into the actual character. This can then trigger validation errors and make ongoing editing burdensome. This generally works best only when no further Record Manager edits are required. For more information on working in Connexion, see the documentation for Connexion client.