
Contents:

0F1.  General rule

0F2.  Romanization

0F1.  General rule

0F1.1.

In the following areas, transcribe information from the publication itself in the language and script (wherever feasible) in which it appears there:

Title and statement of responsibility (FN0-2)

Edition

Publication, distribution, etc.

Series

0F1.2.

Give interpolations into these areas in the language and script of the other information in the area, except for prescribed interpolations and other cases specified in these rules (e.g., 4B5, 4B6.2, 4C6.2).  If the other information in the area is romanized, give interpolations according to the same romanization.

0F1.3.

Give any other information (other than titles, citations, signatures, and quotations in notes) in the language and script of the cataloging agency.

0F2.  Romanization

0F2.1.

If it is not feasible to transcribe from the publication using a nonroman script, romanize the text according to the ALA-LC Romanization Tables.  Do not enclose the romanized text within square brackets.  Make a note to indicate that the romanized text appears in nonroman script in the publication (see 7B2.2).

Transcription:

Dionysiou oikoumens perigsis

Note:  Title in Greek script

Source:

Hendecasyllabwn

Transcription:

Hendecasyllabōn

Note:  In the title, the ō in Hendecasyllabōn is printed in Greek script

0F2.2.

Optionally, if it is feasible to transcribe from the publication using a nonroman script, also provide parallel romanized fields using the ALA-LC Romanization Tables.  Do not enclose the romanized text within square brackets, but make a note indicating that the romanization does not appear in the source.

Note:  Romanization supplied by cataloger

LC Rare Book Team Guidelines:  Usually exercise option.  Further discussion about the main rule's (0F2.1) requirement for a note (7B2.2).  DCRB 0F, AACR2 1.0E and LCRI 1.0E leave adding a note to cataloger's judgment.  Barbara is investigating what appropriate Madison teams do (note or not and when if so).  At the 8/15 meeting, Barbara reported that other LC teams follow LCRI 1.7B2 and do not make a note if the item is written in the primary script for the language (see no. 5 under "Special Application/LC practice").  Something similar existed in old DCRB (0F noted above and 7B2.1 and 7C2) but was changed in the revision to DCRM(B).  We recommend LC practice to continue to follow LCRI 1.7B2.

See also:

0.  General Rules
http://www.itsmarc.com/crs/mergedProjects/rarebks/rarebks/0f._language_and_script_of_the_description.htm
www.itsmarc.com
crawl=CC-MAIN-2017-47
14488
application/http; msgtype=response
sha1:C357O75NXUS76KQNZFKMDTMPWXBK6TPU
<urn:uuid:9fb5965c-2122-46a4-bf48-bfe7f788b1ac>
2017-11-21T06:15:23Z
204.111.112.52
application/xhtml+xml
sha1:JBUONSIYC7COCF5KDR7IZKTY2462PZIG
<urn:uuid:59143093-c5ab-43c4-a129-72872341e87c>
http://www.itsmarc.com/crs/mergedProjects/rarebks/rarebks/0f._language_and_script_of_the_description.htm
response
<urn:uuid:1e8362d3-4845-4812-be65-9589f6b28046>
robots: classic
hostname: ip-10-143-69-18.ec2.internal
software: Nutch 1.6 (CC)
isPartOf: CC-MAIN-2017-47
operator: Common Crawl Admin
description: Wide crawl of the web for November 2017
publisher: Common Crawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf