Skip to main content
OCLC Support

About non-Latin script in Record Manager

  1. Last updated
  2. Save as PDF
Find an overview of non-Latin cataloging in Record Manager.

Overview

In Record Manager, you can enter, edit, and view non-Latin script, also referred to as non-Roman script or vernacular.

Record Manager supports all Unicode characters for non-Latin cataloging. Unicode is the universal character encoding scheme for written characters and text. It defines a consistent way of encoding multi-script text that enables the exchange of text data internationally. MARC-8 encoding for scripts such as Arabic, Chinese, Cyrillic, Greek, Hebrew, Japanese, and Korean is a subset of Unicode. The scripts defined in MARC-8 are now expanded in OCLC interfaces to include the non-MARC-8 characters that are part of these scripts.

 For more information on MARC-8 characters, see the MARC-8 Code Tables.

Adding non-Latin script bibliographic records to WorldCat

Records added to WorldCat must meet MARC standards, regardless of the type of scripts you use to enter the data. You must catalog according to AACR2 practices. For implementing MARC standards in WorldCat records, see OCLC Bibliographic Formats and Standards.

Reasons to use paired fields

In the examples below, the language of cataloging is English, so Latin script is used in the bibliographic records with non-Latin script forms provided in paired fields.

  • Provide non-Latin script for transcribed data:
    • 245 10 $a Войнаимир
    • 245 10 $a Voĭna i mir
  • Provide non-Latin script for a transliterated access point:
    • 100 1 $a Zep, Alen, $e author.
    • 100 1 $a Зеб, Ален, $e author.
  • Provide a non-Latin script form of a subject access point:
    • 600 10 $a 福沢諭吉,a福沢諭吉,d 1887-1975 $v Diaries.
    • 600 10 $a Chiang, Kai-shek, $d 188701975 $v Diaries.

880 field

All instances of non-Latin script in WorldCat are stored in 880 fields through a conversion that is done automatically as you enter non-Latin characters.. In Record Manager, OCLC displays these as paired fields, so that you do not see the 880 field coding. Pairing may also be done manually. For more information, see Linking and unlinking non-Latin fields.

 Note: Records added via batch process should be checked to ensure the correctness of machine-imposed pairings when editing records with non-Latin script.

245 Latin script field

OCLC accepts records that contain only non-Latin script. However, the system requires a Latin script 245 field in bibliographic records. When no Latin script 245 field is present, a 245 field containing only angle brackets is supplied by the system to provide the required Latin script field. Example: 245 10 <>

066 field

The 066 field contains a symbol or four four-character script identification code that tells what non-Latin scripts are present in the record. The field is system-supplied.

Examples

  • 066 ‡ c Cher (Cherokee script)
  • 066 ‡ c Tibt (Tibetan script)
  • 066 ‡ c (S (Greek script)
  • 066 ‡ c Devi $c (N (Devanagari script and Basic Cyrillic)

The subfield $c is repeated if there are multiple non-Latin scripts in a record.