 Known Issue with Diacritics / non-Latin Characters
If the record has diacritics or non-Latin characters, the characters will not come through correctly unless you first load a record from OCLC. This issue is specific to the way Connexion brings in records from Alma and is not within our configuration control. It is recommended that if you are going to bring records into Connexion from Alma, you need to follow these steps: You must have your "File - Import Records - Record Characteristics" set to UTF-8. When you first open Connexion, please log onto OCLC, search for, and display a record in Connexion. What this does is force Connexion to check your preferred character set (which you should already have set to UTF-8 Unicode) so that records you get from Alma will be in UTF-8, not in MARC-8. - You can use a macro, as described below, to perform the OCLC load so that you don't have to remember to do it each time you log on.
If you do not load a record from OCLC before loading a record from Alma, you will get your Alma record in MARC-8, which means that almost all special characters will appear as garbage.
Note that there are NO issues with exporting records to Alma from Connexion. Summary: - Exporting from Connexion to Alma is fine
- Bringing in OCLC records into Alma via Search External Resources is fine
- From within Connexion, bringing in Alma records is problematic unless you follow the above steps
- If you still have trouble, it could be because you need to have the right font. Attached here is the Arial Unicode MS Font Font, which it you need to put it in the C:\Windows\Fonts folder.
| View file |
|---|
| name | ARIALUNI.TTF |
|---|
| height | 250 |
|---|
|
|