For a list of language expertise among Technical Services Division staff, see the Language Expertise list.
Online Dictionaries & Translation Tools
- Google Translate - particuarly useful for translating non-Roman languages, with the ability to either type or draw characters
- Oxford Language Dictionaries Online (UIUC only) - includes Chinese/English, French/English, German/English, Italian/English, Russian/English, and Spanish/English dictionaries
- Lexilogos Online Dictionaries - a directory of various online language dictionaries, continually updated with new content
Non-Latin Script in Records
The University of Illinois at Urbana-Champaign Library prefers use of records that include non-Latin script when appropriate. When non-Latin script is present in a bibliographic record, it should be accompanied by a parallel field with Romanized data (see Linking Fields, below). Romanization should adhere to the ALA-LC Romanization Tables.
The OCLC Connexion client currently supports the following non-Latin scripts:
- Arabic
- Armenian*
- Bengali*
- Chinese
- Cyrillic
- Devanagari*
- Ethiopic*
- Greek
- Hebrew
- Japanese
- Korean
- Syriac*
- Tamil*
- Thai*
*Languages above marked with an asterisk (*) are supported in the UTF-8 Unicode character set. All languages listed above are supported by Alma because all settings for Alma should be UTF-8 Unicode.
Additional instructions for using the above scripts is available in the OCLC Connexion International Cataloging Guide.
Linking Fields
The University of Illinois at Urbana-Champaign follows the PCC Guidelines for Creating Bibliographic Records in Multiple Character Sets. In accordance with these guidelines, non-Latin data in a bibliographic record should be accompanied by a parallel field with Romanized data. In OCLC Connexion, these appear as linked fields with the same tag.
To create linked fields in the OCLC Connexion Client:
- Enter non-Latin data in the appropriate field (e.g., non-Latin title information in field 245)
- Create a new field with the same tag (e.g., Romanized title information in a 2nd field 245)
- In either field, right click and select Link Fields
Alma supports the MARC 21 standard for alternate graphic representation using 880 linked fields. To link fields in Alma:
- Create a new record or open an existing record in the MD Editor.
- Select the rows of the two fields that you want to link.
- Make the first field the focus row.
- For the second field (the one to which you want to link), hold the Ctrl key and select the left mouse button in the row.
- Select the Link Fields option (Edit > Alternate Graphic Representation > Link Fields) and select a script from the list of options that appear.
- When the fields are linked, the system creates a $6 in each of the linked fields that contains the following linkage information:
- Field number and a sequence number such as 880-01 or 245-01
-
Script code for the language that you selected (see
this page for more details)
- Script direction such as r for right to left (see this page for more details)
- Select Save Record
Transliteration Macros
Macros that aid in transliteration of non-Latin scripts are available for the OCLC Connexion Client. While these macros can be helpful when dealing with non-Latin scripts, they can never be perfect. If using a macro for transliteration, it is still important to double-check the output.
Available Macros for OCLC Connexion:
- Joel Hahn's Transliteration Macros - select individual macros as needed, or install the transliteration zip file for multiple macros. Supported languages/scripts include: Armenian, Cyrillic, Devanagari, Ethiopic, Greek, Hebrew, Korean, Syriac, Thai, and Urdu.
- Pinyin Conversion Macro (Princeton University) - converts Chinese characters to Pinyin in a linked field
- Arabic & Persian: transliteration of Arabic and Persian is built in to Connexion via Edit > Transliterate
Non-Latin Script Keyboards
Entering non-Latin script into an OCLC record can be done via direct keyboard input, or it can be done by entering the non-Latin text into an online keyboard and then copying and pasting the text into the Connexion Client.
- Built-in keyboards - Change the language of your keyboard to enter non-Latin script directly. This is best done if you are already familiar with typing in a specific language. To add languages to your Windows machine:
- Click Start > Control Panel > Clock, Language and Region
- Under Region and Language select Change keyboards or other input method
- In the Languages tab, click Change keyboards
- Under the General tab, click Add and navigate to the appropriate language
- Toggle between installed languages using <Left Alt><Shift>, or change languages from the icon in the taskbar
- Branah.com Online Keyboards - Branah.com offers a variety of keyboards for non-Roman script languages. Use the keyboards to enter text and then copy/paste non-Latin script into OCLC Connexion records.
- Keyboards for many non-Latin scripts are also available via websites dedicated to a specific language. These offer the same ability to type in the non-Latin script and then copy/paste the text into OCLC Connexion.
After entering non-Latin script into an OCLC record, always validate using Edit > Validate. For scripts in the MARC-8 character set (Arabic, Greek, Hebrew, Cyrillic, & CJK), use Edit > MARC-8 Characters > Verify.
Additional Cataloging Resources
- ALA-LC Romanization Tables
- OCLC Connexion International Cataloging (PDF)
- PCC Guidelines for Creating Bibliographic Records with Multiple Character Sets (PDF)
- MARC 21: Language Codes
- MARC 21: Country Codes
- OCLC Connexion Transliteration Macros*
- Joel Hahn's Transliteration Macros - select individual macros as needed, or install the transliteration zip file for multiple macros. Supported languages/scripts include: Armenian, Cyrillic, Devanagari, Ethiopic, Greek, Hebrew, Korean, Syriac, Thai, and Urdu.
- Pinyin Conversion Macro (Princeton University) - converts Chinese characters to Pinyin in a linked field
- Arabic & Persian: transliteration of Arabic and Persian is built in to Connexion via Edit > Transliterate
*Note: while transliteration macros can be helpful when dealing with non-Roman scripts, they can never be perfect. If using a macro for transliteration, it is still important to double-check the output.