LC-PCC
Policy Statements for Chapter 1: General Guidelines on Recording Attributes of Manifestations and Items
LC-PCC PS for 1.4
LANGUAGE AND SCRIPT
Font Features
LC practice/PCC practice: Do not attempt to replicate font features such as bold and italics through the use of underlining or other means of indicating such features.
Pre-Modern Forms of Letters
LC practice/PCC practice: In general, transcribe letters as they appear in the source. However, convert earlier forms of letters and earlier forms of diacritical marks into their modern form, as specified here. If there is any doubt as to the correct conversion of elements to modern forms, transcribe them from the source as exactly as possible. See also the section on Special Letters, Diacritical Marks, and Punctuation Marks
below.
below.The following represent a special case: i/j, u/v, uu, or vv/w. When these letters are used in Latin and some other languages without regard to their vocalic or consonantal value, so that "u" is used for a "v," etc., the transcription should be regularized. This means that for the bibliographic description of items published after 1800,
use j for consonants, e.g., jus, Julius;
use i for vowels, e.g., iter, ilias;
use v for consonants, e.g., vox, Victoria;
use u for vowels, e.g., uva, Ursa Major;
use w for consonantal uu or vv, e.g., Windelia.
Also regularize u/v, uu, or vv/w for publications of any date when recording elements, e.g., authorized access points, or citations from reference works.
For the transcription of any of these letters in bibliographic description for pre-1801 publications, apply Descriptive Cataloging of Rare Materials (Books)
(DCRM(B)). See Policy Statement 6.2.2.8 for the use of these letters in authorized access points for works, to assure that DCRM(B) titles file properly (i.e., together with the titles of post-1800 publications).
(DCRM(B)). See Policy Statement 6.2.2.8 for the use of these letters in authorized access points for works, to assure that DCRM(B) titles file properly (i.e., together with the titles of post-1800 publications).Characters That Cannot Be Reproduced by the Facilities Available
LC practice/PCC practice: Transcription requires as much fidelity to the source as the technical capacity within the cataloging agency will allow. The main purposes of these instructions are to categorize all the methods to be employed when encountering unusual symbols and characters, and to give specific directions for each in terms of the particular character set phenomenon encountered.
In the context of machine-readable catalog records note that "facilities available" means the totality of characters that can be represented in machine-readable form and displayed/printed using the "MARC-8 character set"; referred to hereafter as the "character set"). These characters can also be represented in the UCS/Unicode UTF-8 character set, but these guidelines apply only to that subset of the Unicode UTF-8 set that has a counterpart in MARC-8, i.e., the MARC-8 repertoire of UTF-8. Conventions appropriate to particular character set situations are given below. As judged appropriate, use notes to explain and use access points to provide additional access. In the special provisions below, notes are suggested as possible models for form, not to require the use of the note.
Super/Subscript Characters
LC practice/PCC practice: If the super/subscript placement of a character is not essential to avoid serious distortion or loss of intelligibility (e.g., n o, 2 e, M a), record the super/subscript character on the line in the regular manner (e.g., no., 2e). If a period is associated with the super/subscript letter (e.g., M. a) and the characters are the abbreviation of a single word, record the period as the last element (e.g., Ma.). In case of serious distortion or loss of intelligibility, record the character in super/subscript position for all such characters available in the character set, namely, Arabic numerals (0-9), the minus sign (-), parentheses ( () ), and the plus sign (+). In most other cases use the double underscore convention described in the section on Special Letters, Diacritical Marks, and Punctuation Marks; for superscript symbols, also see Policy Statement 1.7.5. Give the letter being represented in upper or lower case according to the source.
; for superscript symbols, also see Policy Statement 1.7.5. Give the letter being represented in upper or lower case according to the source.Greek and Other Non-Latin Script Letters, Ideographs, Etc.
LC practice/PCC practice: Romanize all occurrences of Greek and other non-Latin script letters in "regular" MARC variable fields (with the exception below) regardless of the facilities available. The non-Latin form of the letters may be supplied in parallel fields (MARC field 880) in bibliographic records, or as MARC field 4XX references in authority records. If the context shows that a Greek letter or letters is used to represent a letter in the International Phonetic Alphabet, however, see the section on Special Letters, Diacritical Marks, and Punctuation Marks.
) in bibliographic records, or as MARC field 4XX references in authority records. If the context shows that a Greek letter or letters is used to represent a letter in the International Phonetic Alphabet, however, see the section on Special Letters, Diacritical Marks, and Punctuation Marks.Exception: If the Greek or other non-Latin script letter(s) appears separately, give the name of the letter in the language of the context (if unknown in the language of the context, use English) enclosed within brackets rather than a simple romanization of the letter. For searching purposes, insure that the bracketed interpolation is not connected with other letters. Thus, if no space appears in the source on either side of the supplied bracketed information, put a space on either side of the bracketed interpolation unless this interpolation is already distinct from adjacent letters by the presence of characters that serve as separators. This provision is necessary, because brackets do not serve as separators for searching purposes. "Separators" in this context are defined as characters that divide groups of letters or numbers into multiple words in the context of constructing search queries. Characters not serving as separators are those that are deleted in "normalization"; see the characters marked "delete" in Appendix A of the Authority File Comparison Rules found at: http://www.loc.gov/aba/pcc/naco/normrule-2.html
Note: The following examples show the use of parallel fields to transcribe non-Latin scripts in MARC field 880; such fields are optional.
; such fields are optional.EXAMPLE
Preferred source
| The interpretation of the Hebrew word עם (people) in Samuel-Kings |
Transcription
| 245 14 | $6 880-01 $a The interpretation of the Hebrew word [ʻam] (people) in Samuel-Kings |
Possible parallel field
| 880 14 | $6 245-01/(B $a The interpretation of the Hebrew word עם (people) in Samuel-Kings |
Possible note
| 500 ## | $a In title, "[ʻam]" is expressed in Hebrew script. |
When a Greek, etc., letter is used in a word that is otherwise in the Latin script in the source and the intent is to pronounce the character, use the romanized form of the letter (instead of its name) in brackets.
EXAMPLE
Preferred source
| Oie wowapi waŋ Lakota-Ieska |
Transcription
| 245 10 | $a Oie wowapi wa n Lakota-Ieska |
The letter in this example is from the International Phonetic Alphabet; therefore, the double underscore convention is used (see the section on Special Letters, Diacritical Marks, and Punctuation Marks below)
Special Marks of Contraction in the Manuscript Tradition
LC practice/PCC practice: When special marks of contraction have been used by the printer in continuance of the manuscript tradition, expand affected words to their full form, enclosing supplied letters within brackets, as described in DCRM(B).
.Special Letters, Diacritical Marks, and Punctuation Marks
LC practice/PCC practice: Use the double underscore as the conventional means of signaling special letters (including superscript and subscript letters), diacritical marks, and punctuation marks for which there is no exact representation in the character set. Use the double underscore with the nearest roman equivalent in cases in which the roman equivalent is obvious, e.g., ɓ = b; ɗ = d; ɖ = d; ƒ = f; ħ = h; ŋ = n; ḽ = l; ṱ = t. When the nearest roman equivalent is not obvious, it is necessary to establish the equivalent using the list of equivalencies below. The equivalencies below have been established to date, mostly from the International Phonetic Alphabet (IPA). Note that the IPA uses some Greek letters; when it is judged by the context (usually some form of linguistic study) that the Greek letter probably derives from its use in the IPA, use the double underscore convention or the equivalency indicated below, not the convention for Greek letters given above.
α = a
ɮ = d
ε = e
ɸ = f
ɤ = g
ь = i
Ь = I
ḽ = l
ɔ = o
σ = s
ʃ = s
ɵ = t
ʊ = u
ʋ = v
β = v
ɥ = w
Note that the use of the double underscore convention does not always insure a one-for-one equivalency; the intent, instead, is to signal those cases in which the character used in the catalog record is not an exact replication of the character in the source.
Exception: Do not use the double underscore convention in the following cases; use instead the equivalent indicated:
Old German small "e" (Fu ℯrsten) = umlaut (Fürsten)
"Scharfes s" or "ess-zet" (ß) written as ligature = ss (Ausslegung)
"Scharfes s" or "ess-zet" (ſʒ ) written as two letters = sz (Auszlegung)
Schwa (ə) = ä (e.g., as found in roman alphabet Azerbaijani)
Inch/inches, second/seconds = hard sign, double prime (tvërdyı˘ znak) (″)
Foot/feet, minute/minutes = soft sign, prime (miagkiı˘ znak) (ʹ)
Superscript or subscript period = dot above (·) or dot below (·)
IPA character for glottal stop (ʔ) = ayn (ʻ)
A vertical line ╷ below a letter (e) = dot below the letter (ẹ)
Guillemets (left and right pointing double angle quotation marks) = double quotation mark (")
[2017-01]
LC-PCC PS for 1.4
FIRST ALTERNATIVE
LC practice for Alternative (1st): For the elements identified at RDA 1.4, generally supply non-Latin scripts for the languages/scripts in the MARC-8 repertoire of UTF-8: Perso-Arabic script (e.g., Arabic, Persian, Pushto, Urdu); Hebrew, Yiddish; Chinese, Japanese, Korean; Cyrillic-based scripts; and Greek. If following minimal level cataloguing guidelines, the records for these languages/scripts may be fully romanized. At this time, all other languages/scripts must be fully romanized following the ALA-LC Romanization Tables: Transliteration Schemes for Non-Roman Scripts, approved by the Library of Congress and the American Library Association, with note to the exceptions recorded at: http://hdl.loc.gov/loc.standards/docs.roman.
, generally supply non-Latin scripts for the languages/scripts in the MARC-8 repertoire of UTF-8: Perso-Arabic script (e.g., Arabic, Persian, Pushto, Urdu); Hebrew, Yiddish; Chinese, Japanese, Korean; Cyrillic-based scripts; and Greek. If following minimal level cataloguing guidelines, the records for these languages/scripts may be fully romanized. At this time, all other languages/scripts must be fully romanized following the ALA-LC Romanization Tables: Transliteration Schemes for Non-Roman Scripts, approved by the Library of Congress and the American Library Association, with note to the exceptions recorded at: http://hdl.loc.gov/loc.standards/docs.roman.See the Policy Statements for 5.4, 9.2.2.5.3, and 11.2.2.12 for information on access points for titles of works and expressions, persons, and corporate bodies as found in authority and bibliographic records.
, 9.2.2.5.3, and 11.2.2.12 for information on access points for titles of works and expressions, persons, and corporate bodies as found in authority and bibliographic records.PCC practice for Alternative (1st): Follow the PCC Guidelines for Creating Bibliographic Records in Multiple Character Sets applicable to the PCC program:
applicable to the PCC program:CONSER records: generally supply non-Latin scripts for the languages/scripts in the MARC-8 repertoire of UTF-8: Perso-Arabic script (e.g., Arabic, Persian, Pushto, Urdu); Hebrew, Yiddish; Chinese, Japanese, Korean; Cyrillic-based scripts; and Greek. All other languages/scripts must be fully romanized following the ALA-LC Romanization Tables: Transliteration Schemes for Non-Roman Scripts, approved by the Library of Congress and the American Library Association, with note to the exceptions recorded at: http://hdl.loc.gov/loc.standards/docs.roman.
, approved by the Library of Congress and the American Library Association, with note to the exceptions recorded at: http://hdl.loc.gov/loc.standards/docs.roman.BIBCO records: Scripts beyond the MARC-8 repertoire of UTF-8 may be used by BIBCO libraries when they are supported by the input system.
[2012-09]