Every system, one registry.

Tongyong Pinyin System (2002)

Academia Sinica Tongyong Pinyin System (2002)

Romanization Table -- Amharic (1997)

ALA-LC Romanization Tables: Transliteration Schemes for Non-Roman Scripts. Randal K. Berry (ed.). Library of Congress, 1997.

Romanization Table -- Amharic (2011)

''

Romanization Table -- Arabic (1997)

ALA-LC Romanization table for Arabic

Romanization Table -- Assamese (1997)

ALA-LC Romanization table for Assamese

Romanization Table -- Assamese (2012)

ALA-LC Romanization table for Assamese

Romanization Table -- azerbaij (1997)

ALA-LC Romanization table for Arabic

Romanization Table -- Azerbaijani (1997)

ALA-LC Romanization Tables: Transliteration Schemes for Non-Roman Scripts. Randal K. Berry (ed.). Library of Congress, 1997.

Balinese Romanization Table (2025)

ALA-LC Balinese Romanization Table, 2025 version — strict transliteration per ISO 15919:2001 with PKU modifications. The vowel a is inherent after all consonants except terminal ones, replaced by combining vowel signs or cancelled by the vowel-suppressant adeg-adeg (word-finally the middle dot). The full consonant inventory: the aksara wresastra core, the Indic swalalita set, and the terminal consonants. Vowels include the vocalic and l̥ series and the pepet ə. Transcribed from the loc.gov document's complete text layer and verified against the rendered tables.

Romanization Table -- Byelorussian (1997)

Romanization Table -- Bengali (1997)

ALA-LC Romanization table for Bengali

Romanization Table -- Bengali (2017)

ALA-LC Romanization table for Bengali

Tibetan Romanization Table (2015)

ALA-LC Tibetan Romanization Table, 2015 version — the Wylie system. Every base consonant carries the inherent vowel a (Note 2); stacked consonants romanize as the consonant sequence with the implicit a of the final member; the thirteen vowel signs include the vocalic r and l and the a-chung lengthening (ā); the ʼa chung (འ) romanizes as the alif. Non-Tibetan retroflex and aspirate extensions per the special-letter section. Transcribed from the loc.gov document.

Batak Romanization Table (2012)

ALA-LC Batak Romanization Table, 2012 version (earlier: 2002). Fourteen consonant letters carry an implicit /a/ (suppressed by the pangolat or overridden by a vowel sign); I and U are pure vowels; the vowel signs e i o u follow the letter a when it is already present (aek); the ng and h consonant signs are codas that keep the implicit vowel. Dialect notes from the table: Mandailing S/H/CA and the ka letter (Mandailing HA), Dairi t/v readings. Transcribed from the loc.gov document; the PDF renders Batak glyphs through a shape-based substitute font, so the letter-to-codepoint correspondence follows the standard Batak block with the table's dialect footnotes (all 31 assignments verified against Unicode names).

Romanization Table -- Bulgarian (1997)

Cherokee Romanization Table (2012)

ALA-LC Cherokee Romanization Table, 2012 version (no earlier versions). One-to-one romanization of the complete Cherokee syllabary: six vowels, the twenty consonant series with their vowel-series syllables, the s letter, the hna/nah letters, and the digraph series qua/que/qui/quo/quu/quv, dla/tla and its series, tsa series, and the w and y series. Eighty-five syllabary characters, transcribed from the loc.gov document.

Romanization Table -- Church Slavic (2022)

ALA-LC romanization table for Church Slavic, 2022 version (earlier versions 2011 and 1997). Covers the full Church Slavonic alphabet including the yuses, ksi, psi, fita, izhitsa and the two uk forms, with the letters' numeric values annotated. Transcribed from the digitized table (pages 1-2).

Cham Romanization Table (2015 version)

ALA-LC Cham Romanization Table, 2015 version (no earlier versions). The table serves both Akhar Thrah (Eastern Cham) and Akhar Srak (Western Cham), whose letters share the Unicode Cham block. Thirty-five consonants and semivowels with living (hadiip) and dead (mâtai) forms, six independent vowels, the living vowel modifiers (Takai Akhar Hadiip) including the medials ya/ra/la/wa, the dead feet (Takai Akhar Mâtai) with inherent consonant or vowel endings, the Hua Bilau vowel elongator, the numerals zero through nine, twelve example words from the Cham calendar, and Notes 1-2.

Coptic Romanization Table (2014)

ALA-LC Coptic Romanization Table, 2014 version (no earlier versions). Covers the Coptic alphabet (Greek-derived and Demotic letters), the Old Coptic letters with their diacritic romanizations (diaeresis forms Ï Ü Ẍ, the K-diaeresis-below and dialect-p ni and crossed shei letters, the dialect-p alef to a modifier-letter apostrophe), the Old Nubian letters (ŋ ɲ w), the letter-numeral table (macron above for units, overline for thousands), and the note rules: the single prime inserted between two letters that could be misread as a digraph, and the ignoring of diacritics per the practice of the Journal of Coptic Studies except the iaude (ⲓ) and ua (ⲩ) diaereses.

Romanization Table -- Divehi (1997)

ALA-Library of Congress Divehi Romanization 1997 System

Romanization Table -- Divehi (2012)

ALA-Library of Congress Divehi Romanization 2012 System

Romanization Table -- Greek (1997)

ALA-LC Romanization table for Greek

Romanization Table -- Greek (2010)

ALA-LC Romanization table for Greek

Romanization Table -- Persian (1997)

ALA-LC Romanization table for Persian

Romanization Table -- Gujarati (1997)

ALA-LC Romanization table for Gujarati

Romanization Table -- Gujarati (2011)

ALA-LC Romanization table for Gujarati

Romanization Table -- Hindi (1997)

ALA-LC Romanization table for Hindi

Romanization Table -- Hindi (2011)

ALA-LC Romanization table for Hindi

Armenian Romanization Table (2022)

ALA-LC Armenian Romanization Table, 2022 version (earlier versions: 2011, 1997). The table is based on the phonetic values of Classical and East Armenian; the bracketed West Armenian variant values (B [P], G [K], D [T], Ts [Dz], K [G], Dz [Ts], Ch [J], P [B], J [Ch]) are intended solely for preparing references from West Armenian forms and are not encoded here — the primary rendering is encoded per row. The table covers the complete letter inventory (including the ու digraph, the Եւ/Եվ/և forms), the Note 3 soft-sign (prime) combinations, the punctuation transcription rules, and the letter-numeral table. The aspiration mark is U+02BB (ʻ); the soft sign is U+02B9 (ʹ).

Romanization Table -- Jawi/Pegon (2012)

ALA-LC Romanization table for Jawi/Pegon, 2012 version (earlier versions: 2011, 1997, both tables named Malay (in Jawi-Arabic script))

Javanese, Sundanese, and Madurese Romanization Table

ALA-LC romanization table covering Javanese, Sundanese and Madurese (the PDF carries no in-document version date; its metadata records conversion to MS Word on 2012-01-10). Twenty principal consonants in the hanacaraka order, each with a regular and an appended form (Note 1); the aksara murda and aksara rekan alternates (Note 4); the vowels and sandangan (taling e, pepet e with breve, wulu i, taling plus tarung o, suku u, tarung a-macron) with free-standing vowels (Note 5); the other signs wignyan h, layar r, cecak ng, pa-cerek re with breve, nga-lelet le with breve, pengkal (ya medial) and cakra (ra medial) (Note 5); the pangkon vowel suppressor (Note 1); the numerals zero through nine; and Notes 1-9. Glyphs corresponded to the Unicode Javanese block (the PDF's text layer renders the script in a legacy PUA font).

ALA/LC Systematic Romanization for Judeo-Arabic (2011)

ALA/LC Systematic Romanization for Judeo-Arabic, Jan. 31, 2011 (no earlier versions)

Japanese Romanization Table (2022)

ALA-LC Japanese Romanization Table, 2022 version (McCune-Reischauer). Encodes the Romanized/Kana Equivalent Charts (chart A, Standard; chart B, Non-traditional Japanese for foreign words) kana-by-kana, per section 2.1 ("words and parts of words written only in hiragana or katakana should be romanized as they appear") and section 2.4.2.1 ("Romanize kana-by-kana"), together with the deterministic orthographic rules of the same document: the lengthening-bar macron rule (2.5.1), the sokuon doubling rule (chart A note ii), the n-apostrophe rule (5.2), the kana repetition markers (4.4.1) and the punctuation and typographical equivalents (4.2-4.3). Transcribed from the loc.gov document's complete text layer.

Romanization Table -- Kannada (1997)

ALA-LC Romanization table for Kannada

Romanization Table -- Kannada (2011)

ALA-LC Romanization table for Kannada

Romanization Table -- Georgian Khutsuri (1997)

Values are shown for the Khutsuri alphabet.

Romanization Table -- Georgian Khutsuri (2011)

Values are shown for the Khutsuri alphabet.

Romanization Table -- Georgian Mkhedruli (1997)

Values are shown for the older Khutsuri and the modern Mkhedruli alphabets. There are no upper case letters in Mkhedruli.

Romanization Table -- Georgian Mkhedruli (2011)

Values are shown for the older Khutsuri and the modern Mkhedruli alphabets. There are no upper case letters in Mkhedruli.

Romanization Table -- Kazakh (2012)

ALA-LC Romanization table for Kazakh (in Arabic Script), 2012 version (no earlier versions)

Khmer Romanization Table (2013)

ALA-LC Khmer Romanization Table, 2013 version. Consonants carry the Indic values (k kh g gh ng c ch j jh ñ ...). A bare consonant takes the inherent vowel a (kak mak sak); the coeng subscript suppresses it and repeats the consonant value; the bantoc shortens the preceding vowel to an acute (kák). The series marks mos-soton (˝) and treysap (ʹ) romanize immediately after their consonant. Dependent vowels follow the consonant; nikahit am, reahmuk ah, and the yuukaleapintu grave per the table. Transcribed from the loc.gov document (the dependent-sign glyphs are visually corresponded to the Unicode Khmer block; the vowel-table's leading mark is table typography, not romanization).

Romanization Table -- Korean (1997)

1. General Practice The Library of Congress will continue to follow the McCune-Reischauer system to romanize Korean with the exceptions noted in this document. See: Romanization of the Korean Language: Based upon its Phonetic Structure by G.M. McCune and E.O. Reischauer ([S.l.: s.n., 1939?), reprinted from the Transactions of the Korea Branch of the Royal Asiatic Society. Full text of the original document is available online from the National Library of Australia Web site: http://www.nla.gov.au/librariesaustralia/cjk/download/ras_1939.pdf

Romanization Table -- Kurdish (2012)

ALA-LC Romanization table for Kurdish, 2012 version (earlier versions: 2004, 2002). Trilingual table (Roman Hawar / Cyrillic / Arabic); this map encodes the Arabic column into the Roman (Hawar) column.

Romanization Table -- Ladino (2025)

ALA-LC Romanization table for Ladino, 2025 version (earlier versions: 2011, 2005)

Lao Romanization Table (2012)

ALA-LC Lao Romanization Table, 2012 version. Consonants have initial and word-final values (parenthesized source finals occur only in loans and keep the initial value here). Inherent vowel a. ho hip is silent in clusters (ligatures included); subscript lo lut is silent except after ho hip. DO is ʻ word-initially, else a vowel. WO is positional per Note 4 (cluster w, u+a before a final, o word-finally after a vowel). Vowel romanizations always follow the consonant. Tone marks are not romanized. Transcribed from the loc.gov document's complete text layer.

Lepcha Romanization Table (2012-09)

ALA-LC Lepcha Romanization Table, September 2012 version (earlier version: 1997). Thirty-nine consonant and cluster letters in the guttural/palatal/cerebral/dental/labial arrangement plus semivowels, sibilants and the aspirate, with the inherent vowel a (Note 3); ten vowel values a ā i ī u ū e o ō â listed in their syllable-initial forms (Note 1); final superscripts k ng t n p m r l (Rule of application 1); the subjoined ya and ra mutations (Rules 2-3); and the glottal carrier of Note 2. Glyphs visually corresponded to the Unicode Lepcha block (the PDF's text layer carries no script codepoints).

Limbu Romanization Table (2011)

ALA-LC Limbu Romanization Table, 2011 version. Twenty-six consonants (the Sirijunga alphabet order) with the inherent vowel a; the syllable-initial vowel forms per the table; the dependent vowel signs (ᤠ ᤡ ᤢ ᤣ ᤤ ᤥ) carry the grammar values, noted per the table's Note 1. The Limbu glyphs are visually corresponded to the Unicode Limbu block (the PDF's text layer carries no script codepoints).

Romanization Table -- Malayalam (1997)

ALA-LC Romanization table for Malayalam

Romanization Table -- Malayalam (2012)

ALA-LC Romanization table for Malayalam

Romanization Table -- Marathi (1997)

ALA-LC Romanization table for Marathi

Romanization Table -- Marathi (2011)

ALA-LC Romanization table for Marathi

Romanization Table -- Serbian and Macedonian (1997)

ALA-LC Romanization table for Serbian and Macedonian.

Romanization Table -- Macedonian (2013)

ALA-LC Romanization table for Macedonian.

Manchu Romanization Table (2012)

ALA-LC Manchu Romanization Table, 2012 version (no earlier versions). The printed table gives each letter in its isolated, initial, medial and final forms; Manchu is a cursive script and all positional forms of a letter share one Unicode codepoint, so each row encodes one rule. The before-vowel variant letters of the printed table are distinct letters of the script and carry distinct codepoints: k (1) before a, o, and ū / k (2) before e, i, and u; likewise g (1)/(2), h (1)/(2), t (1)/(2), d (1)/(2), and f (3) before a and e only versus f. The letters and digraphs used in foreign words (kʻ, gʻ, hʻ before a and o; ts, dz, ž, sy, cy, jy per Chinese pinyin values) are shown in the table in isolated form. The Unicode correspondence follows the standard Mongolian block model: shared Mongolian letters, the Sibe letterforms that coincide with the Manchu forms, and the five Manchu-specific codepoints (Manchu I, KA, RA, FA, ZHA); the three foreign-letter forms kʻ gʻ hʻ correspond to the Todo KA/GAA/HAA codepoints, and ts, dz, ž to the Sibe TSA/ZA/ZHA codepoints.

Modern Manipuri (Meitei script) Romanization Table (2022)

ALA-LC Modern Manipuri (Meitei Mayek) Romanization Table, June 2022. Consonants carry the inherent vowel a; the seven final letters (katap) close syllables without a vowel; dependent vowel signs override; the heavy-tone mark romanizes as a dot below. Transcribed from the loc.gov document's complete text layer.

Romanization Table -- Mongolian Cyrillic Khalkha (1997)

In Mongolia, the Khalkha dialect, currently written in both Cyrillic and traditional Mongolian script (and at times in Latin for social networking), is predominant, while in Inner Mongolia, the language is dialectically more diverse and is written in the traditional Mongolian script.

Burmese Romanization Table (2011)

ALA-LC Burmese Romanization Table, 2011 version. Consonants carry the Indic values with the inherent vowel a (Devanagari-style); the asa/virama closes the syllable with an ʻ; medials y r v h romanize between the consonant and its vowel in the order y-or-r, then v, then h; anusvara ṃ; the dot-below and visarga tone marks romanize ʹ and ʺ. Modified conjunct ligatures are visual only — Unicode text spells the sequences, so no special rows are needed. Transcribed from the loc.gov document's text layer.

Romanization Table -- Oriya (1997)

ALA-LC Romanization table for Oriya

Romanization Table -- Oriya (2011)

ALA-LC Romanization table for Oriya

Romanization Table for Ottoman Turkish

ALA-LC Romanization table for Ottoman Turkish, based on the romanization system published by Eleazer Birnbaum in the Journal of the American Oriental Society, volume 87 (1967), with slight modifications. The source document carries no edition date; the 1997 attribute follows the ALA-LC 1997 system edition in which the table appears.

Romanization Table -- Panjabi (1997)

ALA-LC Romanization table for Panjabi

Romanization Table -- Panjabi (2011)

ALA-LC Romanization table for Panjabi

Romanization Table -- Pali (2012)

ALA-LC Romanization table for Pali

Romanization Table -- Prakrit (2012)

ALA-LC Romanization table for Prakrit

Romanization Table -- Pushto (2013)

ALA-LC Romanization table for Pushto, 2013 version (earlier versions: 2012, 1997)

Romanization Table -- Rusyn (2013)

ALA-LC romanization table for Rusyn / Carpatho-Rusyn (2013 version, no earlier versions). Reflects written variants of Rusyn from several regions. Transcribed from the digitized table (pages 1-2).

Romanization Table -- Russian (1997)

The ALA-LC Romanization tables for Slavic alphabets is a set of standards for romanization of texts in various writing systems used in North American libraries and publications. This version was published by the American Library Association and the Library of Congress in 1997. This article is about the ALA-LC method of transliteration of Russian-language text from Cyrillic script to Latin script. The formal, unambiguous version of the system requires some diacritics and two-letter tie characters which are often omitted in practice.

Romanization Table -- Russian (2012)

The ALA-LC Romanization tables for Slavic alphabets is a set of standards for romanization of texts in various writing systems used in North American libraries and publications. The latest version was published by the American Library Association and the Library of Congress in 2012.

Romanization Table -- Sanskrit (2012)

ALA-LC Romanization table for Sanskrit

Santali (in Ol script) Romanization Table (2017)

ALA-LC Santali (Ol Chiki) Romanization Table, 2017 version. Pure letter substitution: seven vowels, twenty-five consonants and marks including the relwa (ᱽ), the nasalization dot (ᱸ → m̐), the omitted low-pitch mark (ᱹ), and the prolongation mark (ᱻ, omitted). Transcribed from the loc.gov document's complete text layer.

Shan Romanization Table (2012)

ALA-LC Shan Romanization Table. Consonants carry the inherent vowel a (per Note 2); the full vowel-sign table (the tone-sign combinations ႆ act as vowel markers: ai āi oi); medials y r v in their documented order. Transcribed from the loc.gov document's text layer with the glyph column visually corresponded to the Shan/Myanmar-extended Unicode blocks (the PDF renders Shan glyphs through a shape-based substitute font).

Romanization Table -- Sinhalese (1997)

ALA-LC Romanization table for Sinhalese

Romanization Table -- Sinhalese (2011)

ALA-LC Romanization table for Sinhalese

Romanization Table -- Sindhi (2024)

ALA-LC Romanization table for Sindhi (in Arabic script), 2024 version (earlier versions: 2013, 2012, 1997)

Romanization Table -- Serbian and Macedonian (1997)

ALA-LC Romanization table for Serbian and Macedonian.

Romanization Table -- Serbian (2013)

Serbian uses the Cyrillic and Roman alphabets. When the Roman alphabet is used it is the same as Croatian.

Romanization Table -- Tamil (1997)

ALA-LC Romanization table for Tamil

Romanization Table -- Tamil (2011)

ALA-LC Romanization table for Tamil

Romanization Table -- Telugu (1997)

ALA-LC Romanization table for Telugu

Romanization Table -- Telugu (2011)

ALA-LC Romanization table for Telugu

Thai Romanization Table (2011)

ALA-LC Thai Romanization Table, 2011 version. Consonants have initial and word-final values; tones are not romanized; ho hip and the four tone-marking o-ang words are silent before a consonant; tho-thanthakhat + ro (ทร) = s. Rule 5: the inherent vowel (o, a, or ǭ) is determined from an authoritative dictionary — bare consonants therefore romanize without an inserted vowel, the composition point for a vocalization model. Transcribed from the loc.gov document's complete text layer.

Romanization Table -- Tigrinya (1997)

Romanization Table -- Tigrinya (2011)

Tamashek Romanization Table (2013)

ALA-LC Tamashek Romanization Table, 2013 version (no earlier versions). The Tuareg Tifinagh alphabet as used for Tamashek: five vowel letters plus schwa, the consonant inventory including the geminate letters (nn, ll) and the two dialect letters, the Ahaggar ǰ (U+2D4B) and the Tawellemmet ž (U+2D64). The source document renders the vernacular glyphs through a substitute font with no text layer for most cells; the codepoint assignments follow the Tuareg letter-to-codepoint unification, grounded on the twenty-one cells whose codepoints the text layer does carry (ⵀ ⵛ ⴹ ⵒ ⵗ ⵆ ⵘ ⵔ ⵙ ⴼ ⴶ ⵐ ⵂ ⵌ ⴾ ⵎ ⵏ ⵠ ⵣ ⵋ ⵤ).

Romanization Table -- Uighur (2015)

ALA-LC Romanization table for Uighur, 2015 version (earlier versions: 2011, 1997)

Romanization Table -- Ukrainian (1997)

The ALA-LC Romanization Tables, published by the American Library Association (1885) and Library of Congress (1905). Used to represent bibliographic information by US and Canadian libraries, by the British Library since 1975,[3] and in North American publications. The latest 1997 revision is very similar to the 1905 version.

Romanization Table -- Ukrainian (2011)

Deseret Romanization Table (2016)

ALA-LC Deseret Romanization Table, 2016 version (no earlier versions). The table is scoped to the Deseret script (the Deseret alphabet), not to any one language, so the language field carries the undetermined code; the alphabet was devised in the 1850s for English. Forty letters (six vowels and thirty-four consonants and vowel-length and diphthong forms), each mapping one-to-one; the letter values follow the printed table. The source document's text layer doubles every letter glyph in the vernacular column; a visual check of the rendered pages confirms a single letter per row, and the codepoints below are the Unicode Deseret block values corresponding to the table's letter order.

Romanization Table -- Urdu (2013)

ALA-LC Romanization table for Urdu (in Arabic script), 2013 version (earlier versions: 2011, 1997)

Vai Romanization Table (2010)

ALA-LC Vai Romanization Table, 2010 version. One-to-one romanization of the Vai syllabary as scoped by the table: 239 syllable characters across the e, i, a, o, u, ɔ and ɛ vowel series (including the nasalized syllables and the ŋã, kpã, gbɔ̃, kpɛ̃, gɛ̃, ŋgɛ̃, ŋɔ̃, ŋɛ̃ forms) plus the syllabic nasal ꘋ (ŋ). Nasalized Latin vowels are normalized to the precomposed tilded letters (ẽ ĩ ã õ ũ) where they exist and to the combining tilde for ɔ̃ and ɛ̃. The extended Latin letters ɓ ɗ ɛ ŋ ɲ ɔ follow the table's Note 1 (Unicode standard usage approved by NDMSO, 2007).

Moroccan Tamazight Romanization Table (2012)

ALA-LC Moroccan Tamazight Romanization Table, approved by CC:AAM 2012-01-22 (no version year printed on the document; the approval date is from the PDF metadata). The table follows, with minimal exceptions, the romanization method used by the Institut Royal de la Culture Amazighe (IRCAM) for texts published in the Central Atlas Tamazight and Standard Tamazight languages of Morocco, using neo-Tifinagh script. Characters needed to support the Tachelhit and Tarifit languages have also been included, so the scope covers all living Moroccan Tamazight languages in neo-Tifinagh. Forty-two letter rules plus the labialized digraphs and the labialization mark (tamatart). The spirant letters romanize with a macron below (ḇ ḡ ḏ ṯ, U+0331); the emphatic letters with a dot below (ḍ ḥ ṛ ṣ ṭ ẓ); the Tachelhit emphatic d with both marks.

Chinese Romanization Table (2012)

ALA-LC Chinese Romanization Table, 2012 version. The 2012 table follows the principles of the Pinyin system, replacing the Wade-Giles system of earlier editions, and does not indicate tone marks (Rules of Application 1). Separation of Syllables: the romanization of each Chinese character is separated by a space. This map encodes the character readings attested by the document's own examples, output as lowercase syllables separated by spaces, and the deterministic punctuation equivalents. Transcribed from the loc.gov document's complete text layer.

Correspondence of Wade-Giles to Pinyin (2012)

The Correspondence of Wade-Giles to Pinyin table from the ALA-LC Chinese Romanization Table, 2012 version (pages 9-21). The document presents the table "as a device to show the usual relationship between Wade-Giles and Pinyin romanizations", drawing the Wade-Giles syllabic readings from Di ming Han zi yi yin biao 地名漢字譯音表 (1971) and the ALA-LC romanization tables (1997), and the Pinyin equivalents from Xian dai Han yu ci dian 现代汉语词典 (1983). The list is printed as not exhaustive; every printed row is transcribed here in order. Transcribed from the loc.gov document's complete text layer.

Romanization Table -- Malay (in Jawi-Arabic script) (2011)

ALA-LC Romanization table for Malay (in Jawi-Arabic script), 2011 version (earlier version: 1997)

Toponymic Guidelines for Antarctica (1995)

In Antarctica geographical names are important elements of identification, orientation, localization and navigation, providing an essential reference system for logistic operations, including search and rescue measures, and for international scientific research. They facilitate information exchange in the field, in scientific publications and in administrative measures under the Antarctic Treaty System. Geographical names also reflect the history of Antarctic exploration. Toponymic Guidelines for Antarctica, Lyubomir Ivanov. Antarctic Place-names Commission of Bulgaria, Sofia, 1995.

Azeri Romanization (1939)

In 1939 Joseph Stalin ordered the Cyrillic alphabet to be used by Azeri speakers in the Soviet Union.

Azeri Romanization (1958)

In 1939 Joseph Stalin ordered the Cyrillic alphabet to be used by Azeri speakers in the Soviet Union.

Streamlined Romanization of Russian Cyrillic (Basic Streamlined System)

The streamlined approach to transliteration was initiated by the author with the development of the Streamlined System for the Romanization of Bulgarian, which was eventually codified by the Transliteration Act of 2009 (ДВ 2009) of the Bulgarian Parliament. The four purposes of the system below are in order of priority: 1. ensure a plausible phonetic approximation of Russian words by English speaking users, including those having no knowledge of the Russian language and no available additional explanations; 2. the system should allow for the retrieval of the original Cyrillic spellings as much as feasible; 3. transliterated Russian words should fit an English language environment i.e. not be perceived as too ‘un-English’; and 4. transliterated word forms should be streamlined and simple. (Ivanov 2003, Ivanov et al. 2010)

Streamlined Romanization of Russian Cyrillic (Optimized Streamlined System)

The streamlined approach to transliteration was initiated by the author with the development of the Streamlined System for the Romanization of Bulgarian, which was eventually codified by the Transliteration Act of 2009 (ДВ 2009) of the Bulgarian Parliament. The four purposes of the system below are in order of priority: 1. ensure a plausible phonetic approximation of Russian words by English speaking users, including those having no knowledge of the Russian language and no available additional explanations; 2. the system should allow for the retrieval of the original Cyrillic spellings as much as feasible; 3. transliterated Russian words should fit an English language environment i.e. not be perceived as too ‘un-English’; and 4. transliterated word forms should be streamlined and simple. (Ivanov 2003, Ivanov et al. 2010)

Japanese Modified Hepburn (1962)

The BGN (Modified Hepburn) System for the transliteration of Japanese has been in use by the Board on Geographic Names since about 1930 and has been extensively employed in the systematic standardization of thousands of geographic names of Japan in Romanized form.

Korean McCune-Reischauer (Hangul to Latin) (1943 Agreement)

Korean McCune-Reischauer (Korean to Latin) (1943 Agreement)

Republic of Bulgaria system for transliteration of Bulgarian geographical names with Roman letters

Streamlined System for Romanization of Bulgarian

Romanization of Adyghe (2012)

The BGN/PCGN system for Adyghe is designed for use in romanizing names written in the Adyghe Cyrillic alphabet. Adyghe, a language of the north-western Caucasian family, is principally spoken in Russia's republic of Adygeya and has been written in a modified Cyrillic script since 1938. Also known as West Circassian, Adyghe is notable for its rich density of consonant phonemes and corresponding paucity of vowels. Adyghe letters are addressed in the romanizations as per their articulation: glottalised consonants are marked with an apostrophe, labialized consonants with w, and retroflex consonants with an underbar. Phonemes shared with Kabardian are represented as per the BGN/PCGN Kabardian Romanization System.

Romanization of Amharic (1967)

Amharic is the principal and official language of Ethiopia. The BGN/PCGN system for Amharic was designed for use in romanizing names written in the Amharic alphabet. The Roman letters and letter combinations shown as equivalents to the Amharic characters reflect modern Amharic pronunciation.

Romanization of Arabic (1956)

This System was adopted by the BGN in 1946 and by the PCGN in 1956 and is applied by BGN and PCGN in the systematic romanization of Arabic geographical names in Bahrain, Egypt, Iraq, Jordan, Kuwait, Libya, Oman, Qatar, Saudi Arabia, Syria, the United Arab Emirates, Yemen, the West Bank and Gaza Strip. Uniform results in the romanization of Arabic are difficult to obtain, since vowel points and diacritical marks are generally omitted from both handwriting and printed script. It follows that for correct identification of the words which appear in any particular name, knowledge of its standard Arabic-script spelling including proper pointing, and recognition of dialectal and idiosyncratic deviations are essential. In order to bring about uniformity in the Roman-script spelling of geographical names in Arabic-language areas, the system is based insofar as possible on fully pointed Modern Standard Arabic (MSA). In the interest of clarity, vowel pointing to indicate short vowels has been applied to the examples given below, and examples of the, more usual, unpointed script have also been provided; it should also be noted that the dots which occur on some characters of the Arabic script are not vowels but rather are an integral part of the base consonant. Arabic script is written from right to left, and does not make a distinction between upper and lower case.

Romanization of Armenian (1981)

The BGN/PCGN system for Armenian was designed for use in romanizing names written in the Armenian alphabet. The Roman letters and letter combinations shown as equivalents to the Armenian characters reflect the eastern variety of Armenian, i.e. the language spoken in the Republic of Armenia.

Romanization of Avar (BGN/PCGN 2011 System)

The BGN/PCGN system for Avar is designed for use in romanizing names written in the Avar Cyrillic alphabet. Avar is a consonant-rich north-eastern Caucasian language, spoken principally in Russia’s republic of Dagestan. It has been written in a modified Cyrillic script since 1938 and, as other Caucasian languages, features glottalised consonants, and though these are not marked with a uniform marker in Avar Cyrillic, an apostrophe denotes the glottalised form of consonants in this romanization table.

Romanization of Avar (2011)

The BGN/PCGN system for Avar is designed for use in romanizing names written in the Avar Cyrillic alphabet. Avar is a consonant-rich north-eastern Caucasian language, spoken principally in Russia's republic of Dagestan. It has been written in a modified Cyrillic script since 1938 and, as other Caucasian languages, features glottalised consonants; an apostrophe denotes the glottalised form of consonants in this romanization table.

Table of Correspondences for Azerbaijani (Cyrillic-Roman) (1993 Agreement)

, also known as Azeri, is the official language of the Republic of Azerbaijan. In 1991, the Azerbaijani government adopted the Roman alphabet to replace the existing Cyrillic alphabet. The presentation below provides a table of correspondences between the former Cyrillic alphabet and the current Roman alphabet. When Azerbaijani Roman-alphabet spellings are not available, this table can be used to convert Azerbaijani Cyrillic spellings.

Table of Correspondences for Bashkir (Cyrillic-Roman) (2007 Agreement)

Bashkir is an official language within Respublika Bashkortostan, one of the republics of the Russian Federation. It will normally be encountered in Cyrillic script, in which case it should be romanized by means of the Cyrillic-Roman table of correspondences given below

ROMANIZATION OF BALUCHI -- BGN/PCGN 2008 System

The following is the BGN/PCGN-approved romanization system for deriving standard spellings of Baluchi geographic names. The romanization system is based on the Hunterian system of romanization, which has been used by the Surveys of India and Pakistan for romanizing Baluchi geographic names for more than one hundred years. The romanization system is compatible with all dialects of Baluchi, including Eastern Baluchi, Western Baluchi, and Southern Baluchi. The BGN/PCGN system laid out below includes diacritical marks in order that the original script can be derived from the romanized form (i.e. it is reversible). For desk users requiring a diacritic-free form, these diacritics can simply be removed. In almost every case the same basic Roman-script characters are kept as are used in the Hunterian system. The BGN/PCGN forms have further been designed to harmonize with the BGN/PCGN Urdu romanization system. In rigorous romanization (i.e. including diacritics), retroflexion is marked by a sub-dot, and aspiration is marked by an apostrophe, where confusion with fricative digraphs could arise. For letters used only in Arabic loan words, the rigorous forms have further been designed to harmonize with the BGN/PCGN Persian romanization system.

Romanization of Belarusian (1979)

The BGN/PCGN system for Belarusian (formerly referred to as Byelorussian) was designed for use in romanizing names written in the Belarusian Cyrillic alphabet. The Belarusian alphabet contains three characters not present in the Russian alphabet: і, ў, and ’. United States Board on Geographic Names Foreign Names Committee Staff, 1994. Romanization Systems and Roman-Script Spelling Conventions, p. 23.

Romanization of Bulgarian (1952)

This system was adopted by the BGN in 1949 and by the PCGN in 1952. It reflects the much simplified Bulgarian orthography as officially revised in February 1945. The Bulgarian alphabet contains all of the characters present in the Russian alphabet with the exception of ё, ы, and э. Notes 1, 2, and 3 are applicable to sources predating the orthographic reform of 1945.

Romanization of Bulgarian (2013 Agreement)

This system reflects the Bulgarian national system officially adopted by state decree in March 2009. It was adopted by BGN and PCGN in 2013, replacing the BGN/PCGN system of 1952.

Table of Correspondences for Chechen (Cyrillic-Roman) (2008 Agreement)

Chechen is an official language within Chechnya, one of the republics of the Russian Federation. It will normally be encountered in Cyrillic script, in which case it should be romanized by means of the Cyrillic-Roman table of correspondences given below.

Romanization of Chuvash (2011)

The BGN/PCGN system for Chuvash is designed for use in romanizing names written in the Chuvash Cyrillic alphabet. Chuvash is an official language within Chuvashiya, one of the republics of the Russian Federation.

Romanization of Chuvash (BGN/PCGN 2011 System)

The BGN/PCGN system for Chuvash is designed for use in romanizing names written in the Chuvash Cyrillic alphabet. Chuvash is an official language within Chuvashiya, one of the republics of the Russian Federation.

Roman-Script Spelling Convention of German (2000 Agreement)

Romanization of Maldivian (1972)

ROMANIZATION SYSTEM FOR MALDIVIAN BGN/PCGN 1972 System

Romanization of Maldivian (1988 Agreement, with 2009 modifications)

This romanization system supersedes the one that was approved by BGN and PCGN in 1972. An official system was submitted to PCGN by the Maldivian government in 1987 and approved by BGN and PCGN in 1988. The system presented here reflects the 1988 Agreement with minor modifications introduced by the government of the Maldives in 2009

Romanization of Dzongkha (2010 Agreement)

This romanization system for Dzongkha was developed by the Dzongkha Development Commission. Bhutan's Ministry of Home Affairs approved this system in 1997 and mandated that the Bhutanese government use standardized spellings of geographical names and official guidelines for romanization. The tabulation is derived from the version available on the UNGEGN Working Group on Romanization Systems website.

Romanization of Greek (1962)

BGN/PCGN Romanization table for Greek

Romanization of Greek (1996)

BGN/PCGN Romanization table for Greek

Romanization of Faeroese (1964)

The Faeroese language is a dialect of Icelandic and, like Icelandic, employs the letter eth (Ð ð). Unlike Icelandic, however, the Faeroese ð has the sound of y (as in "yes") before i, v before u, and is silent in all other cases. The Icelandic letter thorn (Þ þ) does not occur in the writing of Faeroese. To avoid the use of the unfamiliar symbol ð, the Board transliterates it as dh, as in Icelandic, even though its pronunciation in the two languages is not the same.

Roman-Script Spelling Convention of Faroese (1968 Agreement)

Romanization of Arabic (1956)

This System was adopted by the BGN in 1946 and by the PCGN in 1956 and is applied in the systematic romanization of geographic names in Bahrain, Egypt, Iraq, Jordan, Kuwait, Libya, Oman, Qatar, Saudi Arabia, Syria, the United Arab Emirates, and Yemen. Uniform results in the romanization of Arabic are difficult to obtain, since vowel points and diacritical marks are generally omitted from both manual and machine writing. It follows that for correct identification of the words which appear in any particular name, knowledge of its standard Arabic- script spelling including proper pointing, and recognition of dialectal and idiosyncratic deviations are essential. In order to bring about uniformity in the Roman-script spelling of geographic names in Arabic- language areas, the system is based insofar as possible on fully pointed modern standard Arabic. In the interest of clarity, vowel pointing has been applied to the examples below. Arabic is written from right to left, and does not make a distinction between upper and lower case.

Transliteration of Icelandic (1947)

The BGN and the PCGn in 1947 jointly agreed to the transliteration of two letters of the Icelandic alphabet which, although used in writing Old English, have disappeared from the modern English alphabet. The transliterated letters are the edh (Ð ð) and the thorn (Þ þ), pronounced as th in "thus" and th in "think," respectively. It was felt that it was better to transliterate these letters into familiar symbols than preserve such unfamiliar letters in the nomenclature.

Roman-Script Spelling Convention of Icelandic (1968 Agreement)

Romanization of Inuktitut (2013 Agreement)

The BGN/PCGN system for Inuktitut romanizes Canadian Aboriginal Syllabics (qaniujaaqpait) used for geographic names in Nunavut. The syllabic chart was approved by the Inuit Cultural Institute at Arviat in 1976. The BGN/PCGN agreement is dated 2013 and was checked for validity and accuracy in June 2018.

Romanization of Japanese -- Kana Modified Hepburn (1930)

Romanization of Georgian (1981)

BGN/PCGN system of 1981.

Romanization of Georgian (2009 Agreement, Georgia 2011 national system)

This romanization system corresponds to that devised in 2002 by the State Department of Geodesy and Cartography of Georgia and the Institute of Linguistics of the Georgian Academy of Sciences, and approved by Presidential Decree 109 of 24 February 2011. It represents the Mkhedruli alphabet, as presently used in Georgia. This system was adopted by BGN and PCGN in 2009, superseding the BGN/PCGN system of 1981.

Romanization of Kazakh (1979)

The BGN/PCGN system for Kazakh was designed for use in romanizing names written in the Kazakh Cyrillic alphabet. The Kazakh Cyrillic alphabet contains nine characters not present in the Russian alphabet: ә, ғ, қ, ң, ө, ұ, ү, һ and і.

Romanization of Kabardian (2011)

The BGN/PCGN system for Kabardian is designed for use in romanizing names written in the Kabardian Cyrillic alphabet. Kabardian, of the north-western Caucasian language family, is principally spoken in Russia's republics of Kabardino-Balkariya and Karachayevo-Cherkesiya and has been written in a modified Cyrillic script since 1936. Also known as East Circassian, Kabardian is notable for its rich density of consonant phonemes (most commentators agree on an inventory of 47 or 48) and corresponding paucity of vowels. Kabardian letters are addressed in the romanizations as per their articulation: glottalised consonants are marked with an apostrophe, and labialized consonants with w.

Romanization of Kyrgyz (1979)

The BGN/PCGN system for Kyrgyz Cyrillic was designed for use in romanizing names written in the Kyrgyz Cyrillic alphabet. The Kyrgyz Cyrillic alphabet contains three characters not present in the Russian alphabet: Ң , Ө, and Y.

Romanization of Korean for DPRK (Hangul-Latin) (1945 Agreement)

Romanization of Korean for ROK (Hangul-Latin) (2011 Agreement, MOCT System 2000)

Romanization of Korean for ROK (Korean-Latin) (2011 Agreement, MOCT System 2000)

Establishes a system for the transliteration of the characters of Korean script into Latin characters. Intended to provide a means for international communication of written documents.

Table of Correspondences for Karachay-Balkar (Cyrillic-Roman) (2008 Agreement)

Karachay-Balkar is an official language within Karachayevo-Cherkesiya and Kabardino-Balkariya, two of the republics of the Russian Federation. It will normally be encountered in Cyrillic script, in which case it should be romanized by means of the Cyrillic-Roman table of correspondences given below.

Romanization of Kurdish (2007)

The tabulation below is applicable to the Kurdish language as a whole. It is based for the most part on the Hawar Roman alphabet used in the Library of Congress Standard Kurdish Orthography Table, but it also incorporates certain non-Hawar elements found in A Kurdish-English Dictionary (Taufiq Wahby & C J Edmonds, OUP, 1966). The tabulation covers both major varieties of the Kurdish language: Kurmanji and Sorani. Kurmanji is spoken principally in Turkey and in Iraq north of the Great Zab River (Dahūk/Dihok Governorate). It is generally written in Roman script, and usually employs the Roman orthography. Sorani is spoken principally in Iraq south of the Great Zab river (Arbīl/Hewlêr and As Sulaymānīyah/Slêmanî governorates). It is generally written in Perso-Arabic script, and usually employs the Perso-Arabic script orthography. Kurdish forms of geographical names in Turkey will usually be found in Roman script, and so no romanization process will be required. The digraph options for consonant letters '\\u0686', '\\u0634', and '\\u063A' will not be encountered for such names. In Iraq, Syria, and Iran, Kurdish will usually be encountered in Perso-Arabic script, in which case it should be romanized into the corresponding Roman script form. Kurdish geographical names for places and features outside Turkey, found in Roman script form, should, where necessary and if possible, be tailored to fit the orthography of the Romanization shown below and should employ the digraph options for consonant letters '\\u0686', '\\u0634', and '\\u063A'.

Romanization for Macedonian (1981)

BGN/PCGN Romanization table for Macedonian.

Romanization for Macedonian (2013)

Macedonian was officially established as a written language in Yugoslavia during World War II and is now the official language of North Macedonia. This romanization system replaces the BGN/PCGN 1981 agreement and adheres to the most widely-accepted standardization of Macedonian orthography.

Romanization of Mongolian (1964)

This system was originated by the PCGN in 1957 and adopted as a BGN/PCGN System in 1964. It is intended for use in the romanization of geographic names in the "Mongolian People's Republic" but not to romanize Mongolian names in adjacent parts of China and the U.S.S.R.

Romanization for Nepali (2011 Agreement)

The BGN and the PCGN have adopted the Nepal Survey Department (NSD) system for the romanization of Nepali names. This system, below, should be applied to Nepali names for which Roman‐ script spellings in materials produced by the government of Nepal are not available.

Romanization of Ossetian (BGN/PCGN 2009 System)

The BGN/PCGN system for Ossetian is designed for use in romanizing names written in the Ossetian Cyrillic alphabet. Ossetian is a member of the north-eastern Iranian language group and has over half a million speakers. It has principally been written in a modified Cyrillic alphabet though a Roman alphabet was used between 1923 and 1938. The BGN/PCGN Romanization System is derived from the correspondences between that Roman alphabet and the Cyrillic alphabet used for Ossetian today, with modifications to suit an English-language user.

Romanization of Ossetian (2009)

The BGN/PCGN system for Ossetian is designed for use in romanizing names written in the Ossetian Cyrillic alphabet. Ossetian is a member of the north-eastern Iranian language group and has over half a million speakers. It has principally been written in a modified Cyrillic alphabet, though a Roman alphabet was used between 1923 and 1938. The BGN/PCGN Romanization System is derived from the correspondences between that Roman alphabet and the Cyrillic alphabet used for Ossetian today, with modifications to suit an English-language user.

Transliteration System for Persian (1958)

The BGN/PCGN 1958 System for the Persian alphabet was adopted by the BGN in 1946 and by the PCGN In 1958. It Is used for the romanization of standard geographic names in Iran. The Persian alphabet is the same as the Arabic alphabet except for the addition of four consonant symbols for sounds which do not occur in Arabic. Therefore, the same conversion values are used for the Persian alphabet as for the Arabic alphabet wherever phonetically valid. Where letters common to the two alphabets have different pronunciation in the two languages, conversion values reflecting the Persian pronunciation are provided in the Persian system. It may be noted that neither the system of pointing nor the conversion values for vowels and diphthongs are the same for Persian as for Arabic. Persian presents the same problems of vowel pointing as Arabic in that the short vowel symbols necessary for the proper rendering of short vowels, long vowels, and diphthongs are almost always omitted from written Persian. It follows that, in order to produce transliterations in terms of standard written Persian, the transliterator must be able to identify the words used in names and must know their standard written Persian spelling, their proper vowel pointing, and how to eliminate peculiarities due to dialectical variation. The notes and special rules explain details of transliteration not stated in the tables.

National Romanization System for Afghanistan (2007)

This romanization system agreed by BGN and PCGN in November 2007, accommodates the linguistic complexity of Afghanistan as manifest in its geographical names. The following tabulation shows the original Perso-Arabic script with accompanying Unicode value (columns 1a and b), the Yaghoubi romanization (column 2), the BGN/PCGN romanization with accompanying Unicode value (columns 3a and b), an English phonetic example (column 4), and an example toponym (columns 5b and c). [The Yaghoubi romanization system was developed in 1959 by Muzaffarud Din Yaqubi (commonly seen as Yaghoubi). It is a native official system designed to reflect Afghan names, both Dari and Pashto, and both pronunciation and genuine linguistic truth.] The tables function as both a romanization system for Afghanistan (i.e. with access to the original script, these tables can be applied to get a standardized Roman result - moving from columns 1 to 3) and as a means of converting the available Yaghoubi Roman-script spellings, as appear on the Fairchild Aerial Surveys map series, to standard BGN/PCGN spellings (moving from columns 2 to 3). The points used in Arabic to mark short vowels and certain other diacritical marks are infrequently written in Afghanistan. Consequently, a reference source may sometimes be required to aid correct identification of the standard spellings and proper vowels and elimination of dialectal and idiosyncratic variations. In the interests of clarity, the example columns show script with vowel pointing from Arabic to indicate the short vowels that are included alongside the unpointed form that will usually be encountered. However it should be noted that the pronunciation of short vowels will vary. Note: it is recommended that a font such as Scheherazade, available from www.sil.org, which includes the Unicode extended Arabic sub-range, be used to view this system. [Please note that the identification of a particular font does not represent an endorsement of any specific product or manufacturer.]

National Romanization System for Afghanistan -- Yaghoubi (2007)

This romanization system agreed by BGN and PCGN in November 2007, accommodates the linguistic complexity of Afghanistan as manifest in its geographical names. The following tabulation shows the original Perso-Arabic script with accompanying Unicode value (columns 1a and b), the Yaghoubi romanization (column 2), the BGN/PCGN romanization with accompanying Unicode value (columns 3a and b), an English phonetic example (column 4), and an example toponym (columns 5b and c). [The Yaghoubi romanization system was developed in 1959 by Muzaffarud Din Yaqubi (commonly seen as Yaghoubi). It is a native official system designed to reflect Afghan names, both Dari and Pashto, and both pronunciation and genuine linguistic truth.] The tables function as both a romanization system for Afghanistan (i.e. with access to the original script, these tables can be applied to get a standardized Roman result - moving from columns 1 to 3) and as a means of converting the available Yaghoubi Roman-script spellings, as appear on the Fairchild Aerial Surveys map series, to standard BGN/PCGN spellings (moving from columns 2 to 3). The points used in Arabic to mark short vowels and certain other diacritical marks are infrequently written in Afghanistan. Consequently, a reference source may sometimes be required to aid correct identification of the standard spellings and proper vowels and elimination of dialectal and idiosyncratic variations. In the interests of clarity, the example columns show script with vowel pointing from Arabic to indicate the short vowels that are included alongside the unpointed form that will usually be encountered. However it should be noted that the pronunciation of short vowels will vary. Note: it is recommended that a font such as Scheherazade, available from www.sil.org, which includes the Unicode extended Arabic sub-range, be used to view this system. [Please note that the identification of a particular font does not represent an endorsement of any specific product or manufacturer.]

Romanization of Pashto (1968)

Pashto is an Indo-Iranian language and is one of two nationally official languages in Afghanistan and one of five regionally recognised languages in Pakistan. The romanization system presented here may be applied to all Pashto geographical names. Although the BGN/PCGN policy for geographical names in Afghanistan is to apply the BGN/PCGN national system of romanization for Afghanistan (2007), which incorporates Dari elements, when applied to a Pashto geographical name, the romanized results of the BGN/PCGN national system for Afghanistan are the same as those of this Pashto romanization system1 . The Pashto alphabet uses a modified form of the Perso-Arabic script, and contains twelve additional consonants not present in standard Arabic, as well as three additional vowel characters and an additional vowel point. ڼ گ ښ ژ ږ ړ ډ ځ څ چ ټ پ :Consonants ٙ :Point Vowel; ې ۍ ى :Vowels The points used in Arabic to mark short vowels and certain other diacritical marks are not written in Pashto. Consequently, a reference source may sometimes be required to aid correct identification of the standard spellings and proper vowels and elimination of dialectal and idiosyncratic variations. In the interests of clarity, a column showing vowel pointing from Arabic to indicate short vowels has been included in the examples below, alongside the unpointed form that will usually be encountered. However it should be noted that the pronunciation of short vowels will vary. (Note: it is recommended that a font such as Scheherazade, available from www.sil.org, which includes the Unicode extended Arabic sub-range, be used to view this system2 .)

Table of Correspondences for Moldovan (Cyrillic-Roman) (2002 Agreement)

In 1990, the Moldovan authorities adopted the Roman alphabet to replace the existing Cyrillic alphabet. The presentation below provides a table of correspondences between the former Cyrillic alphabet and the current Roman alphabet. When Moldovan Roman-alphabet spellings are not available, this table can be used to convert Moldovan Cyrillic spellings. It should be noted that Moldovan is little used as a language label now, and is usually considered as Romanian.

Romanization of Rusyn (2016)

The BGN/PCGN system for Rusyn was designed for use in romanizing names written in the Rusyn alphabet. There are two primary dialects of the Rusyn language: Carpatho‐Rusyn and Pannonian Rusyn. The Rusyn alphabet is almost identical to the Ukrainian alphabet, but contains three characters not present in the Ukrainian alphabet: ё, ы, and ъ. These letters are also absent from the alphabet used by Pannonian Rusyn. This table applies to both dialects of Rusyn.

Romanization of Russian (1947)

The BGN/PCGN system for Russian was adopted by the BGN in 1944 and by the PCGN in 1947 for use in romanizing names written in the Russian Cyrillic alphabet.

Romanization of Yakut (2012)

Yakut, or Sakha, is a Turkic language spoken by the Yakut people of the Sakha (Yakutiya) Republic of the Russian Federation. The BGN/PCGN system romanizes names written in the Yakut Cyrillic alphabet.

Roman-Script Spelling Convention of Northern Sami (North Lappish) (1984 Agreement)

Transliteration of Serbian Cyrillic

Serbo-Croatian, the official national language of Yugoslavia, is a single literary language. In Serbian areas it is written in the cyrillic (Serbian) alphabet, while in Croatian areas it is written in the roman (Croatian) alphabet. Both the BGN and PCGN use the standard Croatian equivalents for formalizing the Serbian cyrillic alphabet whenever romanized names are not available.

Table of Correspondences for Serbian (Cyrillic-Roman) (2005 Agreement)

The tabulation below reflects the Serbian Cyrillic alphabet and the standard Roman script equivalents used in both Serbia and Montenegro.

Romanization System for Modern Syriac Script (BGN/PCGN 2011 System)

The modern Syriac script is used today by Assyrian writers of the neo-Aramaic language. This Romanization System may be applied to any toponyms written in this script as may be encountered in parts of northern Iraq, Syria, northern Iran and eastern Turkey. The Neo-Aramaic language has a degree of locally official status within Iraq, and accordingly some bilingual Arabic and modern Syriac signage may be encountered. The script is closely aligned to that of both Hebrew and Arabic, and, as these, is written from right to left. In this Romanization System, “strong” consonants have been marked with a sub-dot so as not to give a closer visual relation to either Arabic (which marks such consonants with a cedilla) or Hebrew (which marks these with an underbar). The equivalences where they exist in the Arabic and Hebrew scripts have also been shown only for a guide to the cognate root.

Romanization of modern Syriac script (2011)

The modern Syriac script is used today by Assyrian writers of the neo-Aramaic language. This Romanization System may be applied to any toponyms written in this script as may be encountered in parts of northern Iraq, Syria, northern Iran and eastern Turkey. The Neo-Aramaic language has a degree of locally official status within Iraq, and accordingly some bilingual Arabic and modern Syriac signage may be encountered. The script is closely aligned to that of both Hebrew and Arabic, and, as these, is written from right to left. In this Romanization System, 'strong' consonants have been marked with a sub-dot so as not to give a closer visual relation to either Arabic (which marks such consonants with a cedilla) or Hebrew (which marks these with an underbar). The equivalences where they exist in the Arabic and Hebrew scripts have also been shown only for a guide to the cognate root.

Table of Correspondences for Tatar (Cyrillic-Roman) (2007 Agreement)

Tatar is an official language within Respublika Tatarstan, one of the republics of the Russian Federation. It will normally be encountered in Cyrillic script, in which case it should be romanized by means of the Cyrillic-Roman table of correspondences given below.

Romanization of Tajik (1994)

The BGN/PCGN system for Tajik was designed for use in romanizing names written in the Tajik Cyrillic alphabet. The Tajik Cyrillic alphabet contains six characters not present in the Russian alphabet: ғ, ӣ, қ, ӯ, ҳ and ҷ. An orthographic reform of the Tajik Cyrillic alphabet was implemented under the auspices of the Academy of Sciences of Tajikistan. This reform was promulgated in a decree of 3 September 1998 by the government of the Republic of Tajikistan. The reform abolished the characters ц, щ, ь and ы (see notes 2 through 5).

BGN/PCGN 2002 agreement — Romanization of Thai (Royal Institute of Thailand system)

Romanization of Tigrinya (2007)

The BGN/PCGN system for Tigrinya is designed for use in romanizing geographical names written in Tigrinya (Ge’ez) characters. The Roman letters and letter combinations shown as ek’uivalents to the Tigrinya characters reflect modern Tigrinya pronunciation, while taking into account some conscious archaisms based on Ge’ez and liturgical practices.

TURKMEN Cyrillic script

Table of Correspondences for Turkmen (Cyrillic-Roman) (2000 Agreement)

In 1993, the Turkmen government adopted the Roman alphabet to replace the existing Cyrillic alphabet. The presentation below provides a table of correspondences between the former Cyrillic alphabet and the current Roman alphabet. When Turkmen Roman-alphabet spellings are not available, this table can be used to convert Turkmen Cyrillic spellings. This table of correspondences supersedes the BGN/PCGN 1979 romanization system for Turkmen.

Romanization of Udmurt (2011)

The BGN/PCGN system for Udmurt is designed for use in romanizing names written in the Udmurt Cyrillic alphabet. Udmurt (sometimes known as Votyak) is a member of the Permian branch of the Finno-Ugric languages and is an official language alongside Russian in the Russian Federation's republic of Udmurtiya; it has existed in written form since the late 18th century, and first appeared in its present Cyrillic orthography in 1905.

Romanization of Ukrainian (1965)

The BGN/PCGN system for Ukrainian was designed for use in romanizing names written in the Ukrainian alphabet. The Ukrainian alphabet contains five characters not present in the Russian alphabet: ґ, є, і, ї, and ’.

Romanization of Ukrainian (2019 Agreement)

The BGN/PCGN system for Ukrainian was designed for use in romanizing names written in the Ukrainian alphabet. It is an adoption of the Ukrainian national system in use since 2010, and supersedes the BGN/PCGN 1965 System for Ukrainian.

Romanization of Urdu (2007)

The following is the approved romanization system for deriving standard spellings of Urdu geographical names for Pakistan. It was jointly adopted by BGN and PCGN at the 23rd BGN/PCGN Conference in Washington, DC, in 2007 and it is based on the Hunterian romanization system for Urdu, which has been used by the Surveys of India and Pakistan for romanizing Urdu geographical names for more than one hundred years. The BGN/PCGN system laid out below includes diacritical marks in order that the original script can be derived from the romanized form (i.e. it is reversible). For desk users requiring a diacritic-free form, these diacritics can simply be removed. In every case the same basic Roman-script characters are kept as are used in the Hunterian system. The BGN/PCGN forms have further been designed to harmonize with the BGN/PCGN Persian romanization system.

Romanization of Uzbek Cyrillic (1979)

Table of Correspondences for Uzbek (Cyrillic-Roman) (2000 Agreement)

In 1995, the Uzbek government adopted the Roman alphabet to replace the existing Cyrillic alphabet. The presentation below provides a table of correspondences between the former Cyrillic alphabet and the current Roman alphabet. When Uzbek Roman-alphabet spellings are not available, this table can be used to convert Uzbek Cyrillic spellings. This table of correspondences supersedes the BGN/PCGN 1979 romanization system for Uzbek.

Romanization of Chinese (1979 Agreement)

Chinese characters that represent Mandarin Chinese names of geographical features in the People’s Republic of China (P.R.C.) and which appear in official sources published by the P.R.C. are romanized by the BGN and PCGN by means of the Hanyu Pinyin system. The principal source of approved readings for such characters is the dictionary Xinhua Zidian, published by Commercial Press, Beijing, China, in 2004. Chinese characters which represent Mandarin Chinese names of geographical features in Taiwan are either romanized by means of the Hanyu Pinyin system, or internationally recognised conventional names are used, in accordance with local conventions. For further details of romanization policy both for Chinese-speaking and minority-language areas of China, as well as Taiwan, please consult BGN or PCGN.

Indian script code for information interchange (ISCII) -- Assamese Romanization

IS 13194 (1991): Indian script code for information interchange - ISCII [LITD 20: Indian Language Technologies and Products]

Indian script code for information interchange (ISCII) -- Bengali Romanization

IS 13194 (1991): Indian script code for information interchange - ISCII [LITD 20: Indian Language Technologies and Products]

Indian script code for information interchange (ISCII) -- Devanagri Romanization

IS 13194 (1991): Indian script code for information interchange - ISCII [LITD 20: Indian Language Technologies and Products]

Indian script code for information interchange (ISCII) -- Gujrati Romanization

IS 13194 (1991): Indian script code for information interchange - ISCII [LITD 20: Indian Language Technologies and Products]

Indian script code for information interchange (ISCII) -- Kannada Romanization

IS 13194 (1991): Indian script code for information interchange - ISCII [LITD 20: Indian Language Technologies and Products]

Indian script code for information interchange (ISCII) -- Malayalam Romanization

IS 13194 (1991): Indian script code for information interchange - ISCII [LITD 20: Indian Language Technologies and Products]

Indian script code for information interchange (ISCII) -- Oriya Romanization

IS 13194 (1991): Indian script code for information interchange - ISCII [LITD 20: Indian Language Technologies and Products]

Indian script code for information interchange (ISCII) -- Panjabi(Gurmukhi) Romanization

IS 13194 (1991): Indian script code for information interchange - ISCII [LITD 20: Indian Language Technologies and Products]

Indian script code for information interchange (ISCII) -- Telegu Romanization

IS 13194 (1991): Indian script code for information interchange - ISCII [LITD 20: Indian Language Technologies and Products]

Indian script code for information interchange (ISCII) -- Tamil Romanization

IS 13194 (1991): Indian script code for information interchange - ISCII [LITD 20: Indian Language Technologies and Products]

BS 2979:1958 Transliteration of Cyrillic and Greek characters - Table A, Byelorussian (White R.) column (the British system)

BS 2979:1958, Table A, Byelorussian (White R.) column: the "British" system for (modern) Cyrillic. Table A is a five-column family table (East Slavonic: Russian, Ukrainian, Byelorussian; South Slavonic: Bulgarian, Serbian and Macedonian).

BS 2979:1958 Transliteration of Cyrillic and Greek characters - Table A, Bulgarian column (the British system)

BS 2979:1958, Table A, Bulgarian column: the "British" system for (modern) Cyrillic. Table A is a five-column family table (East Slavonic: Russian, Ukrainian, Byelorussian; South Slavonic: Bulgarian, Serbian and Macedonian).

BS 2979:1958 Transliteration of Cyrillic and Greek characters - Table D, Transliteration of Church Slavonic Cyrillic

BS 2979:1958, Table D: transliteration of Church Slavonic Cyrillic. The table covers the full Church Slavonic alphabet including the yuses, ksi, psi, fita and izhitsa, with the letters' numerical values annotated.

BS 2979:1958 Transliteration of Cyrillic and Greek characters - Table G, Transliteration of Greek characters

BS 2979:1958, Table G: a letter-for-letter system for Greek, aimed at cataloguers and providing a one-to-one correspondence between Greek and Roman characters in both directions.

PD 6505:1982 Guide to the romanization of Korean (BSI mechanical system)

BSI PD 6505:1982, Guide to the romanization of Korean. A mechanical, orthographic system: 14 consonants (the circle is silent initially and ng finally), 14 vowels including /ai/ /ei/ /yai/ /yei/, and the horizontal-stroke vowel rendered w; compound vowels are the plain concatenation of their components' values (\uC640 = oa, \uC65C = uei, \uC758 = wi). Not McCune-Reischauer. Transcribed visually from the scan (no text layer); letter tables and syllable mechanics from sections 2-3 read verbatim.

PD 6505:1982 Table VIII - The Romanization of All Letters in Sino-Korean Words

PD 6505:1982, Guide to the romanization of Korean, Table VIII (source p26): the Sino-Korean-specific layer of the guide. Values are McCune-Reischauer-style: o-breve for the ㅓ series, u-macron for ㅡ, w-compounds, the intervocalic voiced forms -g- -d- -b- -j- -r-, the syllable-final assimilation grid (-ngn- -ngm- -kt- -ls- -rh-), silent initial ㅇ, ㅆ romanized ss-, and a hyphen between syllables (the document's own convention in its bracketed examples). Transcribed visually from the scan at 8-10x. The guide's mechanical system (Part Four) is a separate map.

BS 2979:1958 Transliteration of Cyrillic and Greek characters - Table A, Serbian & Macedonian (Macedonian) column (the British system)

BS 2979:1958, Table A, Serbian & Macedonian (Macedonian) column: the "British" system for (modern) Cyrillic. Table A is a five-column family table (East Slavonic: Russian, Ukrainian, Byelorussian; South Slavonic: Bulgarian, Serbian and Macedonian). The column is shared with Serbian; this map adds the Macedonian-specific letters ѓ, ѕ and ќ to the shared rows.

BS 2979:1958 Transliteration of Cyrillic and Greek characters - Table E, Transliteration of Rumanian Cyrillic (Alfabetul Cirilic)

BS 2979:1958, Table E: transliteration of Rumanian Cyrillic (Alfabetul Cirilic), the Cyrillic alphabet used for Romanian until 1860. For transliteration of Moldavian in the modern orthography, the table's companion note directs the reader to Table C (ISO/R9) in Section 2.

BS 2979:1958 Transliteration of Cyrillic and Greek characters - Table A, Russian column (the British system)

BS 2979:1958, Table A, Russian column: the "British" system for (modern) Cyrillic. Table A is a five-column family table (East Slavonic: Russian, Ukrainian, Byelorussian; South Slavonic: Bulgarian, Serbian and Macedonian); this map is the Russian column. The Serbian and Macedonian column gives the latinica, the existing Latin alphabet of Serbo-Croat. British Standard confirmed December 1998; the BSI 05-2000 reprint is the digitized edition.

BS 2979:1958 Transliteration of Cyrillic and Greek characters - Table A, Serbian column (the British system)

BS 2979:1958, Table A, Serbian column: the "British" system for (modern) Cyrillic. Table A is a five-column family table (East Slavonic: Russian, Ukrainian, Byelorussian; South Slavonic: Bulgarian, Serbian and Macedonian). This map is the Serbian rows of the column; the Macedonian-specific letters (ѓ, ѕ, ќ) are a separate map.

BS 2979:1958 Transliteration of Cyrillic and Greek characters - Table A, Ukrainian column (the British system)

BS 2979:1958, Table A, Ukrainian column: the "British" system for (modern) Cyrillic. Table A is a five-column family table (East Slavonic: Russian, Ukrainian, Byelorussian; South Slavonic: Bulgarian, Serbian and Macedonian).

National System of Geographic Names Transmission into Roman Alphabet in Belarus

The national system of romanization for Belarusian was approved by the State Committee and Land Resources, Geodesy and Cartography, Republic of Belarus, on 20 March, 1998. This scheme was also supported by the Y. Kolas Institute of Linguistics and the Republic Committee on Toponymy at the Belarusian Academy of Sciences. While the system is still based on GOST 1983, it takes more precisely into account the peculiarities of the Belarusian orthography. The system is reversible though there may exist some ambiguous consonant combinations.

Transliteration of geographical names of the Republic of Belarus in letters of the Latin alphabet (2007)

RESOLUTION OF THE STATE COMMITTEE ON PROPERTY OF THE REPUBLIC OF BELARUS June 11, 2007 No. 38 Regulatory Legal Acts Of The National Bank, National Academy Of Sciences Of Belarus, Ministries, Other Republican Government Bodies 8/16668 (06/18/2007) On amendments and additions to the Instructions for the transliteration of geographical names of the Republic of Belarus in letters of the Latin alphabet Based on the Regulation on the State Property Committee of the Republic of Belarus, approved by the Decree of the Council of Ministers of the Republic of Belarus dated July 29, 2006 No. 958 "Issues of the State Committee on Property of the Republic of Belarus"

DIN 1460-2:2011-10, Tabelle 1 row 2: Abchasisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 2 (Abchasisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 1: Abasinisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 1 (Abasinisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 3: Adygeisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 3 (Adygeisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 31635:2011-07 Transliteration des arabischen Alphabets

DIN 31635:2011-07, section 6: transliteration of the Arabic alphabet, applicable to classical and modern standard Arabic. Based on the 1935 recommendation of the International Orientalists' Congress and nearly identical to ISO 233:1984, with additional provisions in the notes for transliteration work. The norm's Persian, Kurdish and Urdu sections are separate maps; its Ottoman-Turkish section gives references only.

DIN 1460-2:2011-10, Tabelle 1 row 4: Altaisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 4 (Altaisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 6: Awarisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 6 (Awarisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 5: Aserbaidschanisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 5 (Aserbaidschanisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 8: Baschkirisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 8 (Baschkirisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 9: Burjatisch (Mongolic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 9 (Burjatisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 54: Tschetschenisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 54 (Tschetschenisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 47: Schorisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 47 (Schorisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 55: Tschuktschisch (Paleo-Asiatic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 55 (Tschuktschisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 30: Krimtatarisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 30 (Krimtatarisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 56: Tschuwaschisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 56 (Tschuwaschisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 11: Darginisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 11 (Darginisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 12: Dunganisch ((St))

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 12 (Dunganisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 14: Eskimo (Asiatic (Siberian) Eskimo, Central Siberian Yupik) (Paleo-Asiatic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 14 (Eskimo (Asiatic (Siberian) Eskimo, Central Siberian Yupik)). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 15: Ewenisch ((Tg))

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 15 (Ewenisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 16: Ewenkisch ((Tg))

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 16 (Ewenkisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 31635:2011-07 section 8: Transliteration des Persischen (Farsi, Dari)

DIN 31635:2011-07, section 8: transliteration of Persian (Farsi, Dari). Section 8.1 states the norm is historically strongly tied to the Arabic transliteration of section 6 (shipped as din-ara-Arab-Latn-31635-2011); Tabelle 2 (rows 1-22, transliteration guidance) and Tabelle 3 (the 32-row letter table) are encoded here. The Persian letters pe gaf che zhe and the Persian kaf and yeh are included; the yeh is accepted in its Arabic (064A), Persian (06CC) and alif-maqsura (0649) forms.

DIN 1460-2:2011-10, Tabelle 1 row 17: Gagausisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 17 (Gagausisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 40: Nanaisch ((Tg))

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 40 (Nanaisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 31634:2011 Information und Dokumentation — Unschrift des griechischen Alphabets

Establishes a system for the transliteration and/or transcription of Greek characters into Latin characters. This system applies to the characters of the Greek script, independent of the period in which it is or was used, i.e. scripts from all periods of Classic or Modern Greek. It therefore allows for polytonic Greek, though it only acknowlegdges rough breathing, and ignores all other diacritics.

DIN 31636:2018-10 Information und Dokumentation - Umschrift des hebraeischen Alphabets

Information and documentation -- Romanization of the Hebrew alphabet. 2018-10 edition, replacing DIN 31636:2011-01. The norm fixes the rendering of the letters of the Hebrew alphabet (including Ivrit) in letters of the Latin alphabet. This map implements the Hebrew (including Ivrit) column over vocalized input; the Yiddish column of the same norm is a separate map.

DIN 33904:2018-10 Information and documentation -- Romanization Devanagari, Hindi

Hindi system. This standard specifies the transliteration of all languages of the Devanāgarī characters into Latin letters firmly. It is suitable for any application.

DIN 32706:2010-01 Information und Dokumentation - Umschrift des armenischen Alphabets

Information and documentation -- Romanization of the Armenian alphabet. The norm fixes the rendering of the letters of the Armenian alphabet in letters of the Latin alphabet and is suitable for all fields of application. It follows the principle of transliteration and is based on library practice and on ISO 9985:1996.

DIN 1460-2:2011-10, Tabelle 1 row 18: Inguschisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 18 (Inguschisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 32708:2014-08 Romanization of Japanese (Kana)

DIN 32708:2014-08, Romanization of Japanese: the modified Hepburn system of Kenkyusha's New Japanese-English Dictionary (3rd/4th ed.) applied to the two kana syllabaries in modern orthography (gendai kanazukai). Tabelle 1 (the one-mora syllables, including the historical kana), Tabelle 2 (the yoon syllables), Tabelle 3 (the gairaigo sequences, whose readings the norm itself marks as proposals), and Tabelle 4 (the subscripted kana, whose sokuon doubles the following consonant). Extracted mechanically from the standard's text layer; both syllabaries are accepted.

DIN 1460-2:2011-10, Tabelle 1 row 22: Karakalpakisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 22 (Karakalpakisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 32707:2010-01 Information und Dokumentation - Umschrift des georgischen Alphabets

Information and documentation -- Romanization of the Georgian alphabet.

DIN 1460-2:2011-10, Tabelle 1 row 20: Kabardinisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 20 (Kabardinisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 25: Kasym-Chantisch (Kasym Khanty) (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 25 (Kasym-Chantisch (Kasym Khanty)). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 36: Mittel-Ob-Chantisch (Middle-Ob Khanty) (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 36 (Mittel-Ob-Chantisch (Middle-Ob Khanty)). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 48: Schuryschkar- (Shuryshkar Khanty) (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 48 (Schuryschkar- (Shuryshkar Khanty)). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 50: Surgut-Chantisch (Surgut Khanty) (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 50 (Surgut-Chantisch (Surgut Khanty)). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 62: Wach-Chantisch (Wach Khanty) (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 62 (Wach-Chantisch (Wach Khanty)). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 39: Mongolisch (Mongolic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 39 (Mongolisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 10: Chakassisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 10 (Chakassisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 24: Kasachisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 24 (Kasachisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 27: Komi-Permjakisch (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 27 (Komi-Permjakisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 29: Korjakisch (Paleo-Asiatic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 29 (Korjakisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 23: Karatschaisch (Karachay) (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 23 (Karatschaisch (Karachay)). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 7: Balkarisch (Balkar) (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 7 (Balkarisch (Balkar)). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 32: Kurdisch (Kurdish (Cyrillic)) (Indo-European)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 32 (Kurdisch (Kurdish (Cyrillic))). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 31: Kumükisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 31 (Kumükisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 31635:2011-07 section 9: Transliteration des Kurdischen (Soranî und Kurmancî)

DIN 31635:2011-07, section 9: transliteration of Kurdish (Soranî and Kurmancî) in the Arabic script, agreeing with the transcription of the cited reference [5]. Tabelle 4 (vowels), Tabelle 5 (semivowels), the remarks 9.1.3 a-g and Tabelle 6 (the 32-row letter table) are encoded. The section covers Soranî and Kurmancî as written in Iraq and Iran; the Latin- and Cyrillic-script Kurmancî of Turkey, Syria and the former Soviet republics is out of scope by the norm's own statement.

DIN 1460-2:2011-10, Tabelle 1 row 28: Komi-Syrjänisch (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 28 (Komi-Syrjänisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 26: Kirgisisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 26 (Kirgisisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 33: Lakkisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 33 (Lakkisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 34: Lesgisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 34 (Lesgisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 33904:2018-10 Information and documentation -- Romanization Devanagari, Marathi

Marathi system. Information und Dokumentation - Transliteration Devanagari This standard specifies the transliteration of all languages of the Devanāgarī characters into Latin letters firmly. It is suitable for any application.

DIN 1460-2:2011-10, Tabelle 1 row 37: Mokscha-Mordwin. (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 37 (Mokscha-Mordwin.). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 42: Wiesen-Mari (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 42 (Wiesen-Mari). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 35: Mansisch (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 35 (Mansisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 45: Berg-Mari (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 45 (Berg-Mari). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 13: Ersa-Mordwinisch (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 13 (Ersa-Mordwinisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 33904:2018-10 Information and documentation -- Romanization Devanagari, Nepali

Nepali system. This standard specifies the transliteration of all languages of the Devanāgarī characters into Latin letters firmly. It is suitable for any application.

DIN 1460-2:2011-10, Tabelle 1 row 43: Niwchisch (Paleo-Asiatic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 43 (Niwchisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 44: Nogaisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 44 (Nogaisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 46: Ossetisch (Indo-European)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 46 (Ossetisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 33904:2018-10 Information and documentation -- Romanization Devanagari, Pali

Pali system. This standard specifies the transliteration of all languages of the Devanāgarī characters into Latin letters firmly. It is suitable for any application.

DIN 33904:2018-10 Information and documentation -- Romanization Devanagari, Prakit

Prakit system. This standard specifies the transliteration of all languages of the Devanāgarī characters into Latin letters firmly. It is suitable for any application.

DIN 1460-2:2011-10, Tabelle 1 row 38: Moldauisch (Moldavian (Cyrillic)) (Indo-European)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 38 (Moldauisch (Moldavian (Cyrillic))). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 19: Jakutisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 19 (Jakutisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 33904:2018-10 Information and documentation -- Romanization Devanagari, Sanskrit

Sanskrit system. This standard specifies the transliteration of all languages of the Devanāgarī characters into Latin letters firmly. It is suitable for any application.

DIN 1460-2:2011-10, Tabelle 1 row 49: Selkupisch ((S))

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 49 (Selkupisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 51: Tabassaranisch (Caucasus)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 51 (Tabassaranisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 33903:2016-02: Information und Dokumentation - Umschrift Tamil

This standard specifies the transcription of the letters of the Tamil alphabet in Latin letters. It is based on international standards as well as on the preprint of the alphabetical tables, which were published in 1976 with the introduction of the rules for alphabetical cataloging. It can be used in all areas, but in particular the aim is to standardize the library and publication area.

DIN 1460-2:2011-10, Tabelle 1 row 52: Tadschikisch (Indo-European)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 52 (Tadschikisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 57: Turkmenisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 57 (Turkmenisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 53: Tatarisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 53 (Tatarisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 58: Tuwinisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 58 (Tuwinisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 59: Udmurtisch (Uralic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 59 (Udmurtisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 60: Uigurisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 60 (Uigurisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 31635:2011-07 section 10: Transliteration von Urdu

DIN 31635:2011-07, section 10: transliteration of Urdu. Tabelle 7 (the 37-row letter table, including the four retroflex letters, the nasal letter and the badi ye) plus the transliteration hints 10.1 a-d: the vowel system (short a i u; long a-macron e i-macron o u-macron; diphthongs ai au), the dropped word-initial alif short-vowel carrier, nasal vowels marked by the following nasal letter, and aspiration written as in the original script.

DIN 1460-2:2011-10, Tabelle 1 row 61: Usbekisch (Turkic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 61 (Usbekisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 1460-2:2011-10, Tabelle 1 row 21: Kalmückisch (Mongolic)

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 21 (Kalmückisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

DIN 31636:2018-10 Information und Dokumentation - Umschrift des hebraeischen Alphabets (jiddische Spalte)

Information and documentation -- Romanization of the Hebrew alphabet, Yiddish column. 2018-10 edition, replacing DIN 31636:2011-01. This map implements the Yiddish column of Table 1 with the Yiddish vowel table (Table 4) and the Yiddish notes (section 9) of the norm. The Hebrew column is a separate map.

DIN 1460-2:2011-10, Tabelle 1 row 41: Nenzisch ((S))

DIN 1460-2:2011-10, Romanization of Cyrillic alphabets of non-Slavic languages, Tabelle 1, language row 41 (Nenzisch). The table assigns each Cyrillic letter of the language's alphabet a Latin letter or letter group; the column order follows DIN 1460:1982 (Slavic). Extracted mechanically from the standard's text layer; the mapping rows below are the table's own cells.

Survey Department Nepali Romanization System (1997)

Survey Department, Ministry of Land Management, Cooperatives and Poverty Alleviation, Government of Nepal.

ELOT 743:1982 Information and documentation -- Conversion of Greek characters into Latin characters (transliteration system)

ELOT 743:1982 transliteration table for Greek

ELOT 743:1982 Information and documentation -- Conversion of Greek characters into Latin characters (transcription system)

ELOT 743:1982 transcription table for Greek.

ELOT 743:2001 Information and documentation -- Conversion of Greek characters into Latin characters (transliteration system)

Reversible transliteration standard, ELOT

ELOT 743:2001 Information and documentation -- Conversion of Greek characters into Latin characters (transcription system)

Reversible transliteration standard, ELOT

Georgian State Department of Geodesy and Cartography Romanization System (2002)

The national system of romanization adopted in February 2002 by the State Department of Geodesy and Cartography of Georgia and the Institute of Linguistics, Georgian Academy of Sciences.

Byelorussian National Cartographic Authority 1992-3 System (based on GOST 1983)

Transliteration of geographical names of the Republic of Belarus with letters of the Latin alphabet (2000)

Act name: On approval of the Instructions for the transliteration of geographical names of the Republic of Belarus in letters of the Latin alphabet Type of act, adoption authority, date and number of adoption (publication): Resolution of the State Committee for Land Resources, Geodesy and Cartography of the Republic of Belarus of November 23, 2000 No. 15 National Registry Registration Number: 8/4488 Date of inclusion in the National Register: 11/30/2000 Source (s) of official publication: National Register of Legal Acts of the Republic of Belarus, 2001, No. 3, 8/4488 (published - January 11, 2001)

GOST 16876-71 Translation Rules Of Cyrillic Alphabet Letters With Latin Alphabet Letters (Table 1)

GOST 16876-71 (Russian: ГОСТ 16876-71) is a romanization system (for transliteration of Russian Cyrillic alphabet texts into the Latin alphabet) devised by the National Administration for Geodesy and Cartography of the Soviet Union. It is based on the scientific transliteration system used in linguistics. GOST was an international standard so it included provision for a number of the languages of the Soviet Union. GOST 16876-71 was used by the United Nations to develop its romanization system for geographical names, which was adopted for official use by the United Nations at the Fifth United Nations Conference on the Standardization of Geographical Names in Montreal, Quebec, Canada, in 1987. UN system relies on diacritics to compensate for non-Russian Cyrillic alphabets. In 1978, COMECON adopted GOST 16876-71 with minor modifications as its official transliteration standard, under the name of SEV 1362-78 (Russian: СЭВ 1362-78). In 1982, In accordance with Order No. 169 of April 16, 1982, GOST 16876-71 / ST SEV 1362-78 was put into effect on May 1, 1982. In 1983, In accordance with Order No. 231 of May 16, 1983, Additional guidelines was released (check notes[7]) In 2002, the Russian Federation along with a number of CIS countries abandoned the use of GOST 16876 in favor of ISO 9:1995, which was adopted as GOST 7.79-2000.

GOST 7.79-2000 System of standards for information, librarianship and publishing. Rules for transliteration of Cyrillic letters in the Latin alphabet

This standard applies to the rules of transliteration by means of the Latin alphabet of individual letters, words, expressions, as well as related texts in languages ​​whose writing is based on the Cyrillic alphabet. The rules in accordance with this standard are applied wherever it is required to provide an unambiguous representation of the Cyril text in Latin letters and the possibility of algorithmic recovery of the text in the original Cyrillic notation, in particular when transferring documents over computer networks. This standard does not apply to the rules for the transmission of the sound appearance of words written in Cyrillic in Latin letters.

Hong Kong Government Cantonese Romanisation

This system is commonly used for the transliteration of place names or person's names in Hong Kong, as pronounced in Cantonese. There will be more than one legitimate transliteration for the same syllable, or sometimes even for the same character. For example, the character 仔 can be transcribed as Chai or Tsai in this system. Some of the choice is context-dependent (e.g. the same character in the place name 灣仔 is almost always Chai, but more likely to be Tsai elsewhere). There will be more variations and unpredictable conversions in person's names, and these conventions need to be hard-coded.

ICAO Doc 9303 Machine Readable Travel Documents Part 3 -- Belorussian Cyrillic to Latin

Part 3 defines specifications that are common to TD1, TD2 and TD3 size machine readable travel documents (MRTDs) including those necessary for global interoperability using visual inspection and machine readable (optical character recognition) means. Since only Latin-alphabet characters are allowed in the VIZ, if mandatory data elements are in a national language that does not use the Latin alphabet, a transcription or transliteration shall also be provided. This document defines the transliteration mappings used to produce this transcription or transliteration.

ICAO Doc 9303 Machine Readable Travel Documents Part 3 -- Bulgarian Cyrillic to Latin

Part 3 defines specifications that are common to TD1, TD2 and TD3 size machine readable travel documents (MRTDs) including those necessary for global interoperability using visual inspection and machine readable (optical character recognition) means. Since only Latin-alphabet characters are allowed in the VIZ, if mandatory data elements are in a national language that does not use the Latin alphabet, a transcription or transliteration shall also be provided. This document defines the transliteration mappings used to produce this transcription or transliteration.

ICAO Doc 9303 Machine Readable Travel Documents Part 3 -- Persian Arabic to Latin

Part 3 defines specifications that are common to TD1, TD2 and TD3 size machine readable travel documents (MRTDs) including those necessary for global interoperability using visual inspection and machine readable (optical character recognition) means. Since only Latin-alphabet characters are allowed in the VIZ, if mandatory data elements are in a national language that does not use the Latin alphabet, a transcription or transliteration shall also be provided. This document defines the transliteration mappings used to produce this transcription or transliteration.

ICAO Doc 9303 Machine Readable Travel Documents Part 3 -- Hebrew to Latin

Part 3 defines specifications that are common to TD1, TD2 and TD3 size machine readable travel documents (MRTDs) including those necessary for global interoperability using visual inspection and machine readable (optical character recognition) means. Since only Latin-alphabet characters are allowed in the VIZ, if mandatory data elements are in a national language that does not use the Latin alphabet, a transcription or transliteration shall also be provided. This document defines the transliteration mappings used to produce this transcription or transliteration.

ICAO Doc 9303 Machine Readable Travel Documents Part 3 -- Macedonian Cyrillic to Latin

Part 3 defines specifications that are common to TD1, TD2 and TD3 size machine readable travel documents (MRTDs) including those necessary for global interoperability using visual inspection and machine readable (optical character recognition) means. Since only Latin-alphabet characters are allowed in the VIZ, if mandatory data elements are in a national language that does not use the Latin alphabet, a transcription or transliteration shall also be provided. This document defines the transliteration mappings used to produce this transcription or transliteration.

ICAO Doc 9303 Machine Readable Travel Documents Part 3 -- Transliteration of Multinational Latin-based Characters

Part 3 defines specifications that are common to TD1, TD2 and TD3 size machine readable travel documents (MRTDs) including those necessary for global interoperability using visual inspection and machine readable (optical character recognition) means. Section A of the document's transliteration scheme renders the multinational Latin-based characters; this map carries that folding for Latin-script input. The document's per-language Cyrillic tables are separate maps.

ICAO Doc 9303 Machine Readable Travel Documents Part 3 -- Russian Cyrillic to Latin

Part 3 defines specifications that are common to TD1, TD2 and TD3 size machine readable travel documents (MRTDs) including those necessary for global interoperability using visual inspection and machine readable (optical character recognition) means. Since only Latin-alphabet characters are allowed in the VIZ, if mandatory data elements are in a national language that does not use the Latin alphabet, a transcription or transliteration shall also be provided. This document defines the transliteration mappings used to produce this transcription or transliteration.

ICAO Doc 9303 Machine Readable Travel Documents Part 3 -- Serbian Cyrillic to Latin

Part 3 defines specifications that are common to TD1, TD2 and TD3 size machine readable travel documents (MRTDs) including those necessary for global interoperability using visual inspection and machine readable (optical character recognition) means. Since only Latin-alphabet characters are allowed in the VIZ, if mandatory data elements are in a national language that does not use the Latin alphabet, a transcription or transliteration shall also be provided. This document defines the transliteration mappings used to produce this transcription or transliteration.

ICAO Doc 9303 Machine Readable Travel Documents Part 3 -- Ukrainian Cyrillic to Latin

Part 3 defines specifications that are common to TD1, TD2 and TD3 size machine readable travel documents (MRTDs) including those necessary for global interoperability using visual inspection and machine readable (optical character recognition) means. Since only Latin-alphabet characters are allowed in the VIZ, if mandatory data elements are in a national language that does not use the Latin alphabet, a transcription or transliteration shall also be provided. This document defines the transliteration mappings used to produce this transcription or transliteration.

ISO 233:1984 Documentation -- Transliteration of Arabic characters into Latin characters

Is one of a series of International Standards dealing with the conversion of systems of writing, following the principles of stringent conversion in order to permit international information exchange. Its aim is to provide a means for international communication of written messages in a form which permits the automatic transmission and reconstitution of these by men or machines. Cancels and replaces ISO Recommendation R 233-1961

ISO 233-2:1993 documentation -- Transliteration of Arabic characters into Latin characters

Establishes a simplified system for the transliteration. This simplification of the stringent rules established by ISO 233:1984 is especially intended to facilitate the processing of bibliographic information (e.g. catalogues, indices, citations, etc.). Annex A gives the diacritical signs used (taken from the code table of ISO 5436:1983).

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Assamese)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Bengali)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 843:1997 Information and documentation -- Conversion of Greek characters into Latin characters (Table 1)

Establishes a system for the transliteration and/or transcription of Greek characters into Latin characters. This system applies to the characters of the Greek script, independent of the period in which it is or was used, i.e. scripts from all periods of Classic or Modern Greek. Replaces ISO/R 843.

ISO 843:1997 Information and documentation -- Conversion of Greek characters into Latin characters (Table 2)

Establishes a system for the transliteration and/or transcription of Greek characters into Latin characters. This system applies to the characters of the Greek script, independent of the period in which it is or was used, i.e. scripts from all periods of Classic or Modern Greek. Replaces ISO/R 843.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Gujarati)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Hindi)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Indic)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 3602:1989 documentation -- Romanization of Japanese (kana script)

Establishes a system for the romanization of the present-day Japanese written language. Unrestricted application for the system requires that the romanizer possess a detailed knowledge of the language in its present-day written form.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Kannada)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 9984:1996 Information and documentation -- Transliteration of Georgian characters into Latin characters

Establishes a system for the transliteration of Georgian characters into Latin characters to permit international information exchange, particularly by electronic means.

ISO/TR 11941:1996 Information and documentation -- Transliteration of Korean script into Latin characters (Method 1)

Establishes a system for the transliteration of the characters of Korean script into Latin characters. Intended to provide a means for international communication of written documents.

ISO/TR 11941:1996 Information and documentation -- Transliteration of Korean script into Latin characters (Method 2)

Establishes a system for the transliteration of the characters of Korean script into Latin characters. Intended to provide a means for international communication of written documents.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Malayalam)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Marathi)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Nepali)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Oriya)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Panjabi)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Pali in Bengali)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Pali in Devanagari)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Pali in Sinhala)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Pali in Thai)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Prakrit)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 223-3:1999 Persian language -- Simplified transliteration

This part of ISO 233 is one of a series of International Standards, dealing with the conversion of systems of writing. The aim of this part of ISO 233 and others in the series is to provide a means for international communication of written messages in a form which permits the automatic transmission and reconstitution of these, by men or machines. The system of conversion, in this case, must be univocal and entirely reversible. This means that no consideration should be given to phonetic and aesthetic matters or to certain national customs: all these considerations are, indeed, ignored by the machine performing the function. The adoption of this part of ISO 233 for international communication leaves every country free to adopt for its own use a national standard which may be different, on condition that it is compatible with this part of ISO 233. The system proposed herein should make this possible and be acceptable to international use if the graphisms it creates are such that they may be converted automatically into the graphisms used in any strict national systems. This part of ISO 233 may be used by anyone who has a clear understanding of the system and is certain that it can be applied without ambiguity. The result obtained will not give a correct pronunciation of the original text in a person’s own language, but it will serve as a means of finding automatically the original graphism and thus allow anyone who has knowledge of the original language to pronounce it correctly. Similarly, one can only pronounce correctly a text written in, for example, English or Polish, if one has a knowledge of English or Polish. The adoption of national standards compatible with this part of ISO 233 will permit the representation, in an international publication, of the morphemes of each language according to the customs of the country where it is spoken. It will be possible to simplify this representation in order to take into account the number of the character sets available on different kinds of machines. 1-Scope: This part of ISO 233 establishes a simplified system for the transliteration of Persian characters into Latin characters. This simplification of the stringent rules established by ISO 233:1984 is especially intended to facilitate the processing of bibliographic information ( e.g. catalogues, indices, citations, etc.) 2-Normative references: The following normative documents contain provisions which, though reference in this text, constitute provisions of this part of ISO 233. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. However, parties to agreements based on this part of ISO 233 are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. For undated references, the latest edition of the normative document referred to applies. Members of ISO and IEC maintain registers of currently valid International StandardsISO 233- 2, Information and documentation -- Transliteration of Arabic characters into Latin characters — Part 2: Arabic language — Simplified transliteration. ISO/IEC 10646-1, Information Technology — Universal Multiple-Octet Coded Character Set (UCS) — Part 1: Architecture and Basic Multilingual Plane.

ISO 9:1995 Information and documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages (Russian)

Establishes a system for the transliteration into Latin characters of Cyrillic characters constituting the alphabets of Slavic and non-Slavic languages. Table 3 includes in a single sequence, listed in the Cyrillic alphabetic order, the 118 single or diacritic-carrying characters that appear in one or another of the considered alphabets.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Sanskrit)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Tamil)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 15919:2001 Information and documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters (Telugu)

Script conversion is often required for documents such as historical and literary texts, geographical texts (including maps and atlases), bibliographies, catalogues, lists and passports (and other identification documents). Text in Devanagari script or other Indic scripts sometimes needs to be shown in Latin script, where users, or equipment that they are using, cannot read or write the text This International Standard applies to transliteration of Devanagari, and to Indic scripts related to Devanagari, independent of the period in which it is or was used.

ISO 11940:1998 Information and documentation -- Transliteration of Thai

Korean Democratic People's Republic of Korea Korean System (2002)

Jyutping Cantonese Romanisation Scheme

The Linguistic Society of Hong Kong Cantonese Romanisation Scheme, or known as Jyutping, was designed and proposed by the Linguistic Society of Hong Kong in 1993. Jyutping is a new Cantonese romanization system which has many advantages. It is multifunctional, systematic, user-friendly, compatible with all possible modern Cantonese sounds, and solely based on alphanumeric characters without any diacritics and strange symbols. Jyutping can also be used as a Chinese computer input method. Its basic principles are simple, easy to learn, and professional.

Transliteration of Mongolian Cyrillic characters into Latin

The standard MNS 5217:2012 is a standard of the Mongolian Agency for Standardization and Metrology for transliteration from Cyrillic Mongolian in Latin alphabet. It repeats and supplements the previous standard dating from 2003 (MNS 5217:2003). This standard differs from the ISO 9 system for Cyrillic adopted by Russia, Armenia, Azerbaijan, Belarus, Kazakhstan, Kyrgyzstan, Uzbekistan, Tajikistan and Turkmenistan.

Transliteration of Latin characters into Mongolian Cyrillic

Latin characters into Mongolian Cyrillic is the opposite transliteration of based on MNS 5217:2012. The standard MNS 5217:2012 is a standard of the Mongolian Agency for Standardization and Metrology for transliteration from Cyrillic Mongolian in Latin alphabet. The grammer of Khalkha Mongolian is required in order to make accurate translation of Latin characters into Mongolian Cyrillic because of no distinguish between /и, й, ъ, ь/ for "i" and /ш, щ/ for "sh" in the standard. In Mongolia, the Khalkha dialect, currently written in both Cyrillic and traditional Mongolian script (and at times in Latin for social networking), is predominant, while in Inner Mongolia, the language is dialectally more diverse and is written in the traditional Mongolian script.

Japanese Cabinet Romanisation of Japanese

The spelling method for Roman characters used when writing Japanese language is as follows. Preface 1. In general, when the language is written, the spelling shown in Table 1 shall be used. 2. The spelling methods listed in Table 2 can be used only when there is a situation that is difficult to change due to international relations or other conventional practices. 3. In either case of the preceding two paragraphs, the general introduction will apply.

Ministry of Culture and Tourism Korean Romanization System (2000)

Generation of Jamo from Hangul This is how the Hangul-to-Jamo maps are generated. Please refer to this page for details about Korean text handling in Unicode. http://gernot-katzers-spice-pages.com/var/korean_hangul_unicode.html This formula copied from the page above is used: [stem] ==== tail = mod (Hangul codepoint − 44032, 28) vowel = 1 + mod (Hangul codepoint − 44032 − tail, 588) / 28 lead = 1 + int [ (Hangul codepoint − 44032)/588 ] ==== [source,python] ---- import pandas as pd import re import math leadjamo = [chr(0x1100+i) for i in range(0,19)] # ᄀᄁᄂᄃᄄᄅᄆᄇᄈᄉᄊᄋᄌᄍᄎᄏᄐᄑᄒ voweljamo = [chr(0x1161+i) for i in range(0,21)] # ᅡᅢᅣᅤᅥᅦᅧᅨᅩᅪᅫᅬᅭᅮᅯᅰᅱᅲᅳᅴᅵ tailjamo = ['']+[chr(0x11A8+i) for i in range(0,27)] # ᆨᆩᆪᆫᆬᆭᆮᆯᆰᆱᆲᆳᆴᆵᆶᆷᆸᆹᆺᆻᆼᆽᆾᆿᇀᇁᇂ hanguls = [chr(i) for i in range(44032,55204)] tails = [tailjamo[(i-44032) % 28] for i in range(44032,55204)] vowels = [voweljamo[((i-44032-((i-44032) % 28)) % 588) // 28] for i in range(44032,55204)] leads = [leadjamo[math.floor((i-44032)// 588)] for i in range(44032,55204)] kr_df = pd.DataFrame({'Hangul':hanguls, 'Lead':leads,'Vowel':vowels, 'Tail':tails}) ---- Hangul Lead Vowel Tail 0 가 ᄀ ᅡ 1 각 ᄀ ᅡ ᆨ 2 갂 ᄀ ᅡ ᆩ 3 갃 ᄀ ᅡ ᆪ 4 간 ᄀ ᅡ ᆫ 5 갅 ᄀ ᅡ ᆬ 6 갆 ᄀ ᅡ ᆭ 7 갇 ᄀ ᅡ ᆮ 8 갈 ᄀ ᅡ ᆯ 9 갉 ᄀ ᅡ ᆰ

Ministry of Foreign Affairs of Japan Hepburn Romanization

The law (旅券法施行規則) requires the use of Hepburn romanization for passports. https://elaws.e-gov.go.jp/search/elawsSearch/elaws_search/lsg0500/detail?lawId=401M50000020011 ３ 前項の氏名はヘボン式ローマ字によって旅券面に表記する。 ただし、申請者がその氏名についてヘボン式によらないローマ字表記を希望し、 外務大臣又は領事官が、出生証明書等により当該表記が適当であり、かつ、 渡航の便宜のため特に必要であると認めるときは、この限りではない。

Maldivian (Divehi) Romanization system (1987)

In 1987 the Maldivian government adopted a system for the romanization of Maldivian. It was also approved by the BGN and the PCGN in 1988. Maldivian is written from right to left. Vowels are marked as diacritical marks accompanying a consonant character.

Transliteration system for Belarusian names in the population register (2008)

RESOLUTION OF THE MINISTRY OF INTERNAL AFFAIRS OF THE REPUBLIC OF BELARUS October 9, 2008, No. 288 8/19678 (10.23.2008) About 8/19678 approval of the Instructions for transliteration of surnames and proper names of citizens of the Republic of Belarus when their personal data is included in the population register

Transliteration system for Belarusian names (2010)

RESOLUTION OF THE MINISTRY OF INTERNAL AFFAIRS OF THE REPUBLIC OF BELARUS June 28, 2010 No. 200 8/22721 About approval of the Instructions on the organization of work of units of citizenship and migration of internal affairs bodies on the issuance, registration, exchange, invalidation, seizure, storage and destruction of a passport of a citizen of the Republic of Belarus

Transliteration system for Russian names in the population register (2008)

8/19678 On approval of the Instructions for transliteration of surnames and proper names of citizens of the Republic of Belarus when their personal data is included in the population register

Transliteration system for Russian names (2010)

RESOLUTION OF THE MINISTRY OF INTERNAL AFFAIRS OF THE REPUBLIC OF BELARUS June 28, 2010 No. 200 8/22721 On approval of the Instructions on the organization of work of units of citizenship and migration of internal affairs bodies on the issuance, registration, exchange, invalidation, seizure, storage and destruction of a passport of a citizen of the Republic of Belarus

Intelligence Community (IC) Standard for the Transliteration of Arabic Personal Names (2004)

ICS-630-01 Romanization of Arabic Personal Names (2015)

This system, adapted from the Board on Geographic Names, is the Intelligence Community (IC) standard for the transliteration of Arabic names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from modern standard Arabic that can then be linked to forensic information in ways that will help identify the referent of the name. Ambiguities can result from the Romanization of Arabic names because the Arabic source generally omits short vowel markings, double consonant marks, and other diacritics that would clearly distinguish the name. Linguists use their experience with the language and aids such as on-line tools and name dictionaries to determine the exact Arabic and the appropriate transliteration into the Roman alphabet. In cases where an individual's name has already been transliterated, that is to be indicated -- as found -- in parentheses immediately following its rendition in the transliteration standard (e.g., Muhammad Khulud ( Mohamed Khulood)). In addition, if the original Arabic- script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Arabic-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Mikhail, Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the online directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal of this system is to produce a consistent Romanized transcription of the name that is readable to the non- specialist. The system uses the 26 letters of the standard ( English) Roman alphabet plus the apostrophe. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Azeri Personal Names (2015)

This system is the Intelligence Community standard for the transliteration of Azeri person names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Azeri that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. For example: Rashad Sadykhov (also seen as Rashad Sadigov, Рашад Садыхов). This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Azeri-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on- line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Belarusian Personal Names (2015)

This system is the Intelligence Community (IC) standard for the transliteration of Belarusian names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Belarusian that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Belarusian-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Mikhail, Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the online directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name

Intelligence Community (IC) Standard for the Transliteration of Bulgarian Personal Names (2005)

ICS-630-01 Romanization of Bulgarian Personal Names (2015)

This system is the Intelligence Community standard for the transliteration of Bulgarian person names that will be applied to all final written reports and products for IC consumers. This standard matches both the Bulgarian national standard adopted in 2009 and the Board of Geographic Names / Permanent Committee on Geographic Names standard adopted in 2013. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Bulgarian that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. For example: Dobri Hristov (also seen as Dobri Khristov, Добри Христов). This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Bulgarian-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the online directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Chechen Cyrillic Personal Names (2015)

This system is the Intelligence Community (IC) standard for the transliteration of Chechen names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Chechen that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic or Arabic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. For example: Ilyas Akhmadkant (also seen as Ilyas Axmadkhant, Ильяс Ахмадкӏант). This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Chechen-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Mikhail, Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the online directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet plus the apostrophe. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

Intelligence Community (IC) Standard for the Transliteration of Farsi (Persian) Personal Names (2004)

ICS-630-01 Romanization of Persian Farsi Dari Personal Names (2015)

This system is the Intelligence Community (IC) standard for the transliteration of Persian (Farsi) and Dari names that is applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Persian (Farsi) and Dari that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Perso-Arabic script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. This convention is designed to ensure that vital forensic information is not lost while maintaining consistency. For names of individuals who are not part of the Persian-( Farsi) or Dari-speaking community, but whose names are encountered in Farsi or Dari, use the relevant IC transliteration standard for names from that language (e.g., Mikhail, Yitzhak, Abu- Murtada). Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the online CIA World Factbook and the online directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these online reference works should be used in place of the IC Standard, with the IC Standard included as a variant in parentheses at the first usage. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e., is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage (e.g., former president Mahmud Ahmadinezhad (Ahmadi-Nejad). The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet plus the apostrophe and hyphen. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with online tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

Intelligence Community (IC) Standard for the Transliteration of Hindi and Urdu Personal Names (2004)

IC STANDARDS FOR TRANSLITERATION OF HINDI AND URDU PERSONAL NAMES

ICS-630-01 Romanization of Hindi Urdu Personal Names (2015)

This system is the Intelligence Community (IC) standard for the transliteration of names from Hindi and Urdu that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from standard Hindi and Urdu that can then be linked to forensic information in ways that will help identify the referent of the name. There are typically a number of ways that names can be Romanized from either Devanagari (Hindi) or modified Arabic (Urdu) scripts. Ambiguities can result from the Romanization of Hindi and Urdu names for several reasons, including the fact that some sounds in South Asian languages (e.g., retroflex consonants, voiced aspirates) have no equivalent in English or other European languages. In the case of Urdu, as in the original Arabic source of many Islamic names, short vowel markings, double consonant marks and other diacritics that would clearly distinguish the name are almost always omitted from standard written texts. And many Islamic names of Arabic or Persian origin reflect spelling distinctions from those languages that are lost in modern Urdu pronunciation (e.g., three distinct Arabic letters all represent the identical sound [s] for Urdu speakers); transliterations might either maintain those spelling distinctions or ignore them entirely. And, as in the Arabic source, names containing the Arabic definite article ‘al’ (‘ul’) show anticipatory assimilation in pronunciation (e.g., Shams al Din > Shamsuddin); transliterations may either reflect spelling or pronunciation in such cases. Because Hindi and Urdu overlap so extensively, it is desirable to correlate Hindi and Urdu transliterations as much as possible. In the area of names, this can become problematic when the Urdu spelling accurately reflects original Arabic spelling while the Hindi spelling was phonetically-based, in essence, already a transliteration. This would argue for ignoring Arabic/Urdu spelling distinctions not reflected in pronunciation in either Urdu or Hindi (e.g., letter sin versus letter sad) while maintaining Arabic/Urdu spelling distinctions like Hindi also maintains (e.g., qaf as in Qutubbin versus kaf)). However, this is not always possible (see Hindi va versus Urdu wau). In cases where an individual’s name has already been transliterated, that is to be indicated – as found – in parentheses immediately following its rendition in the transliteration standard (e.g., Muhammad Khulud (Mohamed Khulood)). In addition, if the original Devanagari or Arabic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Hindi- or Urdu-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Mikhail, Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on-line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal of this system is to produce a consistent Romanized transcription of the name that is readable to the non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. Additionally, this system will be used in conjunction with on-line tools, name dictionaries and lists containing conventional spellings of names of well-known individuals

ICS-630-01 Romanization of Georgian Personal Names (2015)

This system is the Intelligence Community standard for the transliteration of Georgian names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Georgian that can then be linked to forensic information in ways that will help identify the referent of the name.

ICS-630-01 Romanization of Kazakh Personal Names (2015)

This system is the Intelligence Community standard for the transliteration of Kazakh person names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Kazakh that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. For example: Bekzat Sattarkhanov (also seen as Bekzat Sattarkanov, Бекзат Саттарханов). This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Kazakh-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on- line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Kyrgyz Personal Names (2015)

This system is the Intelligence Community standard for the transliteration of Kyrgyz person names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Kyrgyz that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. For example: Guljigit Kalykov (also seen as Guljigit Kalikov, Гульжигит Калыков). This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Kyrgyz-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on- line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Korean Personal Names (2015)

ICS-630-01 Romanization of Kurdish Personal Names (2011)

This system is the Intelligence Community standard for the transliteration of Kurdish names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Kurdish that can then be linked to forensic information in ways that will help identify the referent of a name. The system uses the 26 letters of the standard (English) Roman alphabet plus the apostrophe. Some ambiguities in the Romanized form will occur without the use of diacritics. Within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. The system is used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals. This system does not apply to names of Kurds from Turkey or other regions where Roman script is used. For non-Kurdish names, use the relevant IC transliteration standard for names from that language. Names of individuals from languages written in Roman letters are spelled as they are spelled in those languages. In cases where an individual's name has already been transliterated in a variant spelling, that variant is indicated in parentheses immediately following its rendition in the transliteration standard. If the original Cyrillic or Perso-Arabic-script spelling is known, that spelling should also appear in parentheses following the name, following best practices of the issuing organization and taking into consideration information system capabilities. This convention is designed to ensure that vital forensic information is not lost. For active senior government officials listed in the online CIA World Factbook and the online directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in those reference works are used in place of the IC Standard. For individuals no longer listed, the IC Standard spelling appears first, with the previous reference spelling in parentheses at first usage. There is an effort in the region to purge Kurdish of Arabic vocabulary, influencing how Kurdish names borrowed from Arabic appear, especially in official publications. Defer to the Kurdish IC Standard in these cases.

Intelligence Community (IC) Standard for the Transliteration of Macedonian Personal Names (2005)

Office of the Director Of National Intelligence Macedonian Personal Names 2004 System

ICS-630-01 Romanization of Macedonian Personal Names (2015)

This system is the Intelligence Community (IC) standard for the transliteration of Macedonian names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Macedonian that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Macedonian-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Mikhail, Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on- line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

Intelligence Community (IC) Standard for the Transliteration of Dari Personal Names (2004)

ICS-630-01 Romanization of Persian Farsi Dari Personal Names (2015)

This system is the Intelligence Community (IC) standard for the transliteration of Persian (Farsi) and Dari names that is applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Persian (Farsi) and Dari that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Perso-Arabic script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. This convention is designed to ensure that vital forensic information is not lost while maintaining consistency. For names of individuals who are not part of the Persian-( Farsi) or Dari-speaking community, but whose names are encountered in Farsi or Dari, use the relevant IC transliteration standard for names from that language (e.g., Mikhail, Yitzhak, Abu- Murtada). Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the online CIA World Factbook and the online directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these online reference works should be used in place of the IC Standard, with the IC Standard included as a variant in parentheses at the first usage. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e., is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage (e.g., former president Mahmud Ahmadinezhad (Ahmadi-Nejad). The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet plus the apostrophe and hyphen. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with online tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

Pashto Standardized Transliteration System for Personal Names (2011)

Pashto is a language characterized by its variability. The challenges of reaching a universally acceptable transliteration standard for personal names are posed both by the dialect spread trending roughly from the southwest to the northeast parts of its geographic area, and also by the competing influences of Dari and Urdu. Given the lack of any dominant standard on some points, it has been considered necessary to define a certain degree of flexibility within this standardization system in order to enable it to capture the variability of the language it seeks to reflect. A great effort has also been made to research and reflect common usage in the Pashto- speaking areas of Pakistan and Afghanistan, and to define rules which capture these trends to the best extent possible. However, a respect for the norms of usage has also been balanced with the need for consistency and intelligibility. Therefore, there are cases where a less common spelling will be the preferred usage under the guidance of this system. Lastly, specific names that cannot be incorporated gracefully into the rules described below are included with case-by-case preferred spellings in a list near the end of this document.

ICS-630-01 Romanization of Russian Personal Names (2015)

This system, adapted from the Board of Geographic Names (BGN) Romanization system for Russian (1947), is the Intelligence Community (IC) standard for the transliteration of Russian names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Russian that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. E.g., Sergey Nikolayevich Tyurin (Serguei Nicolaivitch Tiourine). In addition, if the original Cyrillic spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. This convention is designed to ensure that vital forensic information is not lost. For non-Russian names, use the relevant IC transliteration standard for names from that language. A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on-line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

Intelligence Community (IC) Standard for the Transliteration of Serbian Personal Names (2004)

Office of the Director Of National Intelligence Serbian Personal Names 2004 System

ICS-630-01 Romanization of Serbian Personal Names (2015)

This system is the Intelligence Community (IC) standard for the transliteration of Serbian names written in Cyrillic that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Serbian that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Serbian-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Mikhail, Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the online directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Tatar Personal Names (2015)

This system is the Intelligence Community standard for the transliteration of Tatar person names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Tatar that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. For example: Rustam Abdrashitov (also seen as Rustem Abdrashitov, Рустам Абдрашитов). This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Tatar-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on- line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Tajik Personal Names (2015)

This system is the Intelligence Community standard for the transliteration of Tajik names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Tajik that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. For example: Parvona Jamshedov (also seen as Parvona Dzhamshedov, Парвона Ҷамшедов). This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Tajik-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Mikhail, Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on- line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Turkmen Personal Names (2015)

This system is the Intelligence Community standard for the transliteration of Turkmen person names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Turkmen that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. For example: Azat Muhadov (also seen as Azat Muhadow, Азат Мухадов). This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Turkmen-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on- line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Uyghur Personal Names (2015)

This system is the Intelligence Community standard for the transliteration of Uyghur person names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Uyghur that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic-script or Arabic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. For example: Zordun Sabir (also seen as Zordun Sabeer, Зордун Сабир ,زوردون سابیر). This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Uyghur-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on-line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Ukrainian Personal Names (2015)

This system is the Intelligence Community (IC) standard for the transliteration of Ukrainian names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Ukrainian that can then be linked to forensic information in ways that will help identify the referent of the name.

ICS-630-01 Romanization of Hindi and Urdu Personal Names (2015)

This system is the Intelligence Community (IC) standard for the transliteration of names from Hindi and Urdu that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from standard Hindi and Urdu that can then be linked to forensic information in ways that will help identify the referent of the name. There are typically a number of ways that names can be Romanized from either Devanagari (Hindi) or modified Arabic (Urdu) scripts. Ambiguities can result from the Romanization of Hindi and Urdu names for several reasons, including the fact that some sounds in South Asian languages (e.g., retroflex consonants, voiced aspirates) have no equivalent in English or other European languages. In the case of Urdu, as in the original Arabic source of many Islamic names, short vowel markings, double consonant marks and other diacritics that would clearly distinguish the name are almost always omitted from standard written texts. And many Islamic names of Arabic or Persian origin reflect spelling distinctions from those languages that are lost in modern Urdu pronunciation (e.g., three distinct Arabic letters all represent the identical sound [s] for Urdu speakers); transliterations might either maintain those spelling distinctions or ignore them entirely. And, as in the Arabic source, names containing the Arabic definite article ‘al’ (‘ul’) show anticipatory assimilation in pronunciation (e.g., Shams al Din > Shamsuddin); transliterations may either reflect spelling or pronunciation in such cases. Because Hindi and Urdu overlap so extensively, it is desirable to correlate Hindi and Urdu transliterations as much as possible. In the area of names, this can become problematic when the Urdu spelling accurately reflects original Arabic spelling while the Hindi spelling was phonetically-based, in essence, already a transliteration. This would argue for ignoring Arabic/Urdu spelling distinctions not reflected in pronunciation in either Urdu or Hindi (e.g., letter sin versus letter sad) while maintaining Arabic/Urdu spelling distinctions like Hindi also maintains (e.g., qaf as in Qutubbin versus kaf)). However, this is not always possible (see Hindi va versus Urdu wau). In cases where an individual’s name has already been transliterated, that is to be indicated – as found – in parentheses immediately following its rendition in the transliteration standard (e.g., Muhammad Khulud (Mohamed Khulood)). In addition, if the original Devanagari or Arabic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Hindi- or Urdu-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Mikhail, Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the on-line directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal of this system is to produce a consistent Romanized transcription of the name that is readable to the non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. Additionally, this system will be used in conjunction with on-line tools, name dictionaries and lists containing conventional spellings of names of well-known individuals

ICS-630-01 Romanization of Uzbek Personal Names (2015)

This system is the Intelligence Community standard for the transliteration of Uzbek person names that will be applied to all final written reports and products for IC consumers. It is not intended to eliminate variations of a name that can contribute forensic information. Rather, it is to provide an IC standard Romanized (English) transliteration from Uzbek that can then be linked to forensic information in ways that will help identify the referent of the name. In cases where an individual’s name has already been transliterated in a variant spelling, the IC Standard spelling should appear first, followed by the variant spelling(s) in parentheses at the first usage. In addition, if the original Cyrillic-script spelling is known, that spelling should also appear in parentheses following the name, if possible, following best practices of the issuing organization and taking into consideration information system capabilities. For example: Farkhod Tojiev (also seen as Farhod Tadjiyev, Фарход Тожиев). This convention is designed to ensure that vital forensic information is not lost. For names of persons who are known to not be part of the Uzbek-speaking community, use the relevant IC transliteration standard for names from that language (e.g., Yitzhak). A translator’s note may be used to clarify the known origin of the person. Spell names of individuals from languages that are written in Roman letters as they are spelled in those languages (e.g., George Clooney, Jorge Garcia, Georges Pompidou). In the case of active senior government officials in the on-line CIA World Factbook and the online directory of Chiefs of State and Cabinet Members of Foreign Governments, the spellings given in these on-line reference works should be used in place of the IC Standard. For any individual who has at one time been listed in the Factbook or Chiefs of State directory but who no longer appears in those resources (i.e. is no longer a government official), the IC Standard spelling should appear first, with the spelling, if known, as it previously appeared in those resources listed within parentheses at the first usage. The primary goal is to produce a consistent Romanized transcription of names that is specifically readable to the English-speaking non-specialist. The system uses the 26 letters of the standard (English) Roman alphabet. Some ambiguities in the Romanized form will occur without the use of diacritics. However, within the context of a report, where additional information about the individual is provided, the referent will be clearly identified. This system will be used in conjunction with on-line tools, name dictionaries, and lists containing conventional spellings of names of well-known individuals.

ICS-630-01 Romanization of Chinese Personal Names (2015)

This system applies to personal names rendered in Modern Chinese as represented in the Hanyu Pinyin Romanization System. It does not apply to names that are represented in other systems or in Romanization schemes or practices that are used to represent personal names in Chinese dialects. The Intelligence Community (IC) standard for transliterating Chinese personal names into English is the Hanyu Pinyin Romanization System (or pinyin), officially known as the Scheme of the Chinese Phonetic Alphabet (汉语拼音方案), with several modifications as specified in this document (e.g., absence of umlauted ü, title case for surnames). In 1982 the International Organization for Standardization (ISO) codified the Hanyu Pinyin Romanization System as ISO 7098, Information and Documentation – Romanization of Chinese (Second Edition, 12-15-1991). The primary purpose for designating a singular system is to allow for a consistent transcription of names that is specifically readable to the English-speaking non-specialist. It is not intended to be fully "reversible". Disambiguation should be accomplished by providing additional information following best practices of the issuing organization: the Unicode-encoded form of the original Chinese characters, the original encoding scheme if other than Unicode (e.g., Big5 or GB), whether traditional or simplified characters were used, and Standard Telegraphic Code (标准电码) representations (The Standard Telegraph Codebook, revised edition, PRC Ministry of Post and Telecommunications) — e.g., Ma Yingjiu (STC: 7456/5391/0036). Use simplified (or short form) characters as the default; traditional (or long form) characters may be used for non-Mainland persons. Personal names in Chinese should be transliterated into the IC Standard in accordance with the following criteria: a. the surname (family name) should appear first, followed by the given name b. the surname should be separated from the given name and be followed by the given name. The initial letter of each name should be capitalized, with the rest in lower case letters c. commas should not be placed between the surname and given name d. syllables should not be separated in the given name e. hyphens should not be used between any syllables (except as noted in paragraph 12) f. apostrophes should not be used between any syllables (see paragraph 14 for details) g. compound surnames should be capitalized with no space between the characters Examples include Zhang Wei, Hu Jintao, Ouyang Xiu, Zhou Youguang, and Ouyang Qianqing. If an official spelling of a name differs from the IC Standard, it may be used throughout the document, with the IC Standard spelling included where capabilities allow. When a married woman uses both her surname and her husband's surname, both surnames are capitalized, but a hyphen should be used to separate the surnames (e.g., Chen-Li Meiling; the first surname is the husband's, the second the wife's maiden name). The umlaut (ü), as in Lü and Nü, should not be used. The standard uses u for the ü character: Lu, Nu. No apostrophe (’) should be used between syllables; other forensic information (e.g. original Chinese characters, STC codes) should be used where necessary to disambiguate syllable combinations. Any additional ambiguity should be addressed in a Translator's Comment.

Royal Thai General System of Transcription (1999) — phoneme-to-RTGS stage

Pinyin

This table contains the data on how Unicode Hanzi characters are pronounced in P.R.China.

Transliteration of Place Names in Minority Languages in Chinese Pinyin (Mongolian, general)

Article 1 The main purpose of the transliteration method of Chinese pinyin letter transliteration of place names in minority languages: (1) As a standard for spelling place names in minority languages ​​ with Chinese phonetic alphabet; (2) As a phonetic tool for surveying and recording ethnic place names in map surveying and mapping work; (3) As the main basis for the pronunciation and selection of place names in ethnic minority languages ​​in Chinese character transliteration; (4) Provide convenient conditions for the unified compilation of my country's place-name information and index in alphabetical order. Article 2 The transliteration method is limited to the 26 letters in the "Hanyu Pinyin Plan", two letters with additional symbols and a sound-proof symbol. In order to make the transcription and phonetic more accurate, the syllable structure can not be restricted by the syllable form of Mandarin Chinese. Soundproof symbols can be used in various occasions that are easy to be confused. When recording, additional symbols can be added to specific letters to represent special sounds. The transliteration and transliteration of ethnic minority scripts in Latin script shall be based on the script. Letters with the same or similar pronunciation and usage as in the "Hanyu Pinyin Plan" shall be written according to them; different or dissimilar letters shall be transcribed separately. If the text does not use Latin letters, the corresponding Chinese phonetic letters shall be used according to the pronunciation of the text. If there is no text, according to the general voice mark. Article 3 Special place names are handled with reference to the following methods: (1) If the commonly used Chinese name is partly transliterated and partly translated, the transliteration part is spelled according to the transliteration method, and the free translation part is spelled according to the pronunciation of the Chinese character. (2) If the commonly used Chinese character translation is a section translation, the actual situation may be considered. Some are transliterated according to the full name of the original name, and some are spelled according to the Hanyu pronunciation of the section translation. (3) If the translated name of a Chinese character originally came from a minority language, but later became a Chinese form and has been commonly used, it can be spelled according to the pronunciation of the Chinese character, including the original name transliterated if necessary. (4) Other special circumstances shall be dealt with according to specific discretion.

Transliteration of Place Names in Minority Languages in Chinese Pinyin (Mongolian, phonetic)

Article 1 The main purpose of the transliteration method of Chinese pinyin letter transliteration of place names in minority languages: (1) As a standard for spelling place names in minority languages ​​ with Chinese phonetic alphabet; (2) As a phonetic tool for surveying and recording ethnic place names in map surveying and mapping work; (3) As the main basis for the pronunciation and selection of place names in ethnic minority languages ​​in Chinese character transliteration; (4) Provide convenient conditions for the unified compilation of my country's place-name information and index in alphabetical order. Article 2 The transliteration method is limited to the 26 letters in the "Hanyu Pinyin Plan", two letters with additional symbols and a sound-proof symbol. In order to make the transcription and phonetic more accurate, the syllable structure can not be restricted by the syllable form of Mandarin Chinese. Soundproof symbols can be used in various occasions that are easy to be confused. When recording, additional symbols can be added to specific letters to represent special sounds. The transliteration and transliteration of ethnic minority scripts in Latin script shall be based on the script. Letters with the same or similar pronunciation and usage as in the "Hanyu Pinyin Plan" shall be written according to them; different or dissimilar letters shall be transcribed separately. If the text does not use Latin letters, the corresponding Chinese phonetic letters shall be used according to the pronunciation of the text. If there is no text, according to the general voice mark. Article 3 Special place names are handled with reference to the following methods: (1) If the commonly used Chinese name is partly transliterated and partly translated, the transliteration part is spelled according to the transliteration method, and the free translation part is spelled according to the pronunciation of the Chinese character. (2) If the commonly used Chinese character translation is a section translation, the actual situation may be considered. Some are transliterated according to the full name of the original name, and some are spelled according to the Hanyu pronunciation of the section translation. (3) If the translated name of a Chinese character originally came from a minority language, but later became a Chinese form and has been commonly used, it can be spelled according to the pronunciation of the Chinese character, including the original name transliterated if necessary. (4) Other special circumstances shall be dealt with according to specific discretion.

Survey of Egypt Romanization

The Survey of Egypt System (SES) of Romanization.

PROVISIONAL RULES OF REPRODUCING LETTERS OF THE UKRAINIAN ALPHABET WITH LATIN (ENGLISH) CHARACTERS

These Rules are intended for Romanized transliteration of Ukrainian geographic names in international cartographic editions. Geographic names of Russia, Byelorussia, Bulgaria and other states using the Cyrillic alphabet are transliterated according to rules accepted in those states. These Rules come into effect from the moment of their approval by the Main Administration of Geodesy, Cartography and Cadastre and will be effective until the introduction of a State standard of Ukraine regulating the Romanized transliteration of the Ukrainian alphabet.

Government of Ukraine Ukrainian System (1996)

Romanization table for Ukrainian. The current national system of romanization.

The Cabinet of Ministers of Ukraine adopted Resolution No 858 "About the statement of the technical description and a sample passport form of a citizen of Ukraine to go abroad and make changes to some acts of the Cabinet of Ministers of Ukraine"

The Cabinet of Ministers of Ukraine adopted Resolution No 55 "On Normalization of Transliteration of the Ukrainian Alphabet by Means of the Latin Alphabet"

The Cabinet of Ministers of Ukraine adopted Resolution No 55 "On Normalization of Transliteration of the Ukrainian Alphabet by Means of the Latin Alphabet" on January 27, 2010. The Resolution approved The Table of transliteration of the Ukrainian Alphabet by Means of the Latin Alphabet. As a result of the adoption of this Resolution Ukrainian proper names (geographical names, names and surnames,) are rendered by means of the Latin alphabet in accordance with unified rules of transliteration in official documents, in cartographic editions, on signs of populated places, streets, metro stations, stops, etc.

Romanization of Amharic -- UNGEGN (2016)

The United Nations recommended romanization system was approved in 1967 (resolution I/17), based on the Amharic to English Transliteration System (2nd revised edition, August 1962) by the Imperial Ethiopian Mapping and Geography Institute. The table has been published in volume II of the conference report (see Ref. in Notes section). The UN-approved system is not being used in Ethiopia, instead a simple version without diacritical marks is used. In international cartographic products mostly the BGN/PCGN 1967 system is used which differs from the former mainly by using diacritical marks differently. Often the same spellings are used without any diacritical marks. Amharic uses the Ethiopic syllabic script whereby each syllable denotes a combination of a consonant and a vowel. It has 34 basic characters, each character having several different forms, usually called orders, according to the vowel with which the basic character is combined. The system is mainly reversible with the exception of some syllables of the 1st order which are pronounced in the same manner as the syllables of the 4th order, and some consonants.

Romanization of Arabic -- Beirut system (1971)

The current United Nations recommended romanization system was approved in 2017 (resolution XI/3), based on the system adopted by Arabic experts at the conference held in Beirut in 2007, the Unified Arabic Transliteration System, taking into account the practical amendments and corrections carried out and agreed upon by the representatives of the Arabic- speaking countries at the Fourth Arab Conference on Geographical Names, held in Beirut in 2008, and some clarifications and amendments agreed in Riyadh in 20171. Previously, the United Nations had approved a romanization system in 1972 (resolution II/8), based on the system adopted by Arabic experts at the conference held at Beirut in 1971 with the practical amendments carried out and agreed upon by the representatives of the Arabic-speaking countries at their conference. The table was published in volume II of the conference report. In UN resolution XI/3 it is specifically stated that the system was recommended for the “romanization of the geographical names within those Arabic-speaking countries where this system is officially adopted”. There is evidence of its partial implementation in Jordan, Oman and Saudi Arabia. The UNGEGN Working Group on Romanization Systems intends to continue monitoring the UN system’s implementation across Arabic-speaking countries. In some countries there exist local romanization schemes or practices. The geographical names of Algeria, Djibouti, Mauritania, Morocco and Tunisia are generally rendered in the traditional manner which conforms to the principles of the French orthography. The previous UN-approved system is still found in considerable international usage. Arabic is written from right to left. The Arabic script usually omits vowel points and diacritical marks from writing which makes it difficult to obtain uniform results in the romanization of Arabic. It is essential to identify correctly the words which appear in any particular name and to know the standard Arabic-script spelling including the relevant vowels. One must also take into account dialectal and idiosyncratic deviations. The romanization is generally reversible though there may be some ambiguous letter sequences (dh, kh, sh, th) which may also point to combinations of Arabic characters in addition to the respective single characters.

Romanization of Arabic -- UNGEGN (1972)

The United Nations recommended romanization system was approved in 1972 (resolution II/8), based on the system adopted by Arabic experts at the conference held at Beirut in 1971 with the practical amendments carried out and agreed upon by the representatives of the Arabic-speaking countries at their conference. The table was published in volume II of the conference report1 . In the UN resolution it was specifically pointed out that the system was recommended "for the romanization of the geographical names within those Arabic-speaking countries where this system is officially acknowledged". It cannot be definitely ascertained which of the Arabicspeaking countries have adopted this system officially, especially since 2007 when there are efforts by the Arabic Division to promote a modification of the UN system (ADEGN romanization, see the section on other romanization systems below), with varying success2 . Judging by the use of names in international cartographic products which rely mostly on national sources it appears that the UN system or its modification is more or less current in Iraq, Kuwait, Libya, Saudi Arabia3 , United Arab Emirates and Yemen, there and in some other countries the system is often used without diacritical marks. For the geographical names of the Syrian Arab Republic international maps favour the UN system while the local usage seems to prefer a French-oriented romanization. Also in Egypt and Sudan there exist local romanization schemes or practices side by side with the UN system. The geographical names of Algeria, Djibouti, Mauritania, Morocco and Tunisia are generally rendered in the traditional manner which conforms to the principles of the French orthography. Resolution 7 of the Seventh UN Conference on the Standardization of Geographical Names (1998) recommended that "the League of Arab States should, through its specialized structures, continue its efforts to organize a conference with a view to considering the difficulties encountered in applying the amended Beirut system of 1972 for the romanization of Arabic script, and submit, as soon as possible, a solution to the United Nations Group of Experts on Geographical Names". At the Eighth UN Conference on the Standardization of Geographical Names (2002), the Arabic Division of the UN Group of Experts announced that it had finalised proposed modifications to the UN recommended romanization system. These proposals would be submitted to the League of Arab States for approval. Arabic is written from right to left. The Arabic script usually omits vowel points and diacritical marks from writing which makes it difficult to obtain uniform results in the romanization of Arabic. It is essential to identify correctly the words which appear in any particular name and to know the standard Arabic- script spelling including proper pointing. One must also take into account dialectal and idiosyncratic deviations. The romanization is generally reversible though there are some ambiguous letter sequences (dh, kh, sh, th) which may also point to combinations of Arabic characters in addition to the respective single characters.

Romanization of Arabic -- Unified Arabic Transliteration System (2017)

The current United Nations recommended romanization system was approved in 2017 (resolution XI/3), based on the system adopted by Arabic experts at the conference held in Beirut in 2007, the Unified Arabic Transliteration System, taking into account the practical amendments and corrections carried out and agreed upon by the representatives of the Arabic- speaking countries at the Fourth Arab Conference on Geographical Names, held in Beirut in 2008, and some clarifications and amendments agreed in Riyadh in 20171. Previously, the United Nations had approved a romanization system in 1972 (resolution II/8), based on the system adopted by Arabic experts at the conference held at Beirut in 1971 with the practical amendments carried out and agreed upon by the representatives of the Arabic-speaking countries at their conference. The table was published in volume II of the conference report. In UN resolution XI/3 it is specifically stated that the system was recommended for the “romanization of the geographical names within those Arabic-speaking countries where this system is officially adopted”. There is evidence of its partial implementation in Jordan, Oman and Saudi Arabia. The UNGEGN Working Group on Romanization Systems intends to continue monitoring the UN system’s implementation across Arabic-speaking countries. In some countries there exist local romanization schemes or practices. The geographical names of Algeria, Djibouti, Mauritania, Morocco and Tunisia are generally rendered in the traditional manner which conforms to the principles of the French orthography. The previous UN-approved system is still found in considerable international usage. Arabic is written from right to left. The Arabic script usually omits vowel points and diacritical marks from writing which makes it difficult to obtain uniform results in the romanization of Arabic. It is essential to identify correctly the words which appear in any particular name and to know the standard Arabic-script spelling including the relevant vowels. One must also take into account dialectal and idiosyncratic deviations. The romanization is generally reversible though there may be some ambiguous letter sequences (dh, kh, sh, th) which may also point to combinations of Arabic characters in addition to the respective single characters.

Romanization of Assamese -- UNGEGN 4.0

The United Nations recommended system was approved in 1972 (II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports. There is no evidence of the use of the system either in India or in international cartographic products. Assamese (Asamīyā) uses an alphasyllabic script whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants. The romanization table is unambiguous but the user would have to recognize many ligatures not given in the original table. The system is mostly reversible but there exist some ambiguities in the romanization of vowels (independent vs. abbreviated characters) and consonants (ligatures vs. character sequences). References Second United Nations Conference on the Standardization of Geographical Names. London, 10–31 May 1972. Vol. II. Technical papers. United Nations. New York 1974, pp. 141–142. Third United Nations Conference on the Standardization of Geographical Names. Athens, 17 August – 7 September 1977. Vol. II, Technical papers, pp. 393 etc.

Romanization of Belarusian geographic names (2007)

RESOLUTION OF THE STATE COMMITTEE ON PROPERTY OF THE REPUBLIC OF BELARUS June 11, 2007 No. 38 8/16668 (06/18/2007) On amendments and additions to the Instructions for the transliteration of geographical names of the Republic of Belarus in letters of the Latin alphabet Based on the Regulation on the State Property Committee of the Republic of Belarus, approved by the Decree of the Council of Ministers of the Republic of Belarus dated July 29, 2006 No. 958 "Issues of the State Committee on Property of the Republic of Belarus"

Romanization of Bengali -- UNGEGN 4.0

The United Nations recommended system was approved in 1972 (II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports1,2. There is no evidence of the use of the system either in Bangladesh, in India or in international cartographic products. The resolution IV/17 (1982) recommended association, inter alia, with Bangladesh, in carrying out further studies on the system. Bengali (Bānglā) uses an alphasyllabic script whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants. The romanization table is unambiguous but the user would have to recognize many ligatures not given in the original table. The system is mostly reversible but there exist some ambiguities in the romanization of vowels (independent vs. abbreviated characters) and consonants (ligatures vs. character sequences). Other systems of romanization For differences between the UN system and the ISO transliteration standard ISO 15919: 2001 see the section on the romanization of Hindi. References Second United Nations Conference on the Standardization of Geographical Names. London, 10–31 May 1972. Vol. II. Technical papers. United Nations. New York 1974, pp. 139–140. Third United Nations Conference on the Standardization of Geographical Names. Athens, 17 August – 7 September 1977. Vol. II, Technical papers, pp. 393 etc.

Romanization of Bulgarian geographical names (1977)

The System of Transliteration and Transcription of Bulgarian Geographical Names into Roman letters, as shown in the annex below, be adopted as the international system for the romanization of Bulgarian geographical names.

Romanization of Greek 1.0 (Phonetic transcription)

UNGEGN Romanization table for Greek: Phonetic transcription UNGEGN Greek v1.0, Fifth United Nations Conference on the Standardization of Geographical Names. Writing Systems and Guides to Pronunciation Romanization > Conversion of the Greek alphabet into Latin characters. Paper submitted by Greece and Cyprus.

Romanization of Greek -- UNGEGN 4.0 (transliteration)

UNGEGN Romanization table for Greek

Romanization of Greek -- UNGEGN 4.0 (transcription)

UNGEGN Romanization table for Greek

Romanization of Gujarati -- UNGEGN 4.0

The United Nations recommended system was approved in 1972 (II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports. There is no evidence of the use of the system either in India or in international cartographic products. Gujarati (Gujarātī) uses an alphasyllabic script whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants. The romanization table is unambiguous but the user would have to recognize many ligatures not given in the original table. For two vowel letters (e/ĕ, o/ŏ) there is uncertainty as to the conditions in which either of the two variants is to be used. The system is mostly reversible but there exist some ambiguities in the romanization of vowels (independent vs. abbreviated characters) and consonants (ligatures vs. character sequences). References Second United Nations Conference on the Standardization of Geographical Names. London, 10–31 May 1972. Vol. II. Technical papers. United Nations. New York 1974, pp. 134–135. Third United Nations Conference on the Standardization of Geographical Names. Athens, 17 August – 7 September 1977. Vol. II, Technical papers, pp. 393 etc.

Romanization of Hindi -- UNGEGN 4.0

The United Nations recommended system was approved in 1972 (II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports. There is no evidence of the use of the system either in India or in international cartographic products. It was stated in 1987 that the appropriate resolution had not been implemented in India and the Hunterian system was still in use in large-scale mapping Hindi uses the alphasyllabic script Devanāgarī whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants. The romanization table is unambiguous but the user would have to recognize many ligatures not given in the original table (only three are given). The system is mostly reversible but there may exist some ambiguities in the romanization of vowels (independent vs. abbreviated characters) and consonants

Romanization of Kannada -- UNGEGN 4.0

The United Nations recommended system was approved in 1972 (II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports There is no evidence of the use of the system either in India or in international cartographic products. Kannada uses an alphasyllabic script whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants. The romanization table is unambiguous. The system is mostly reversible but there may exist some ambiguities in the romanization of vowels (independent vs. abbreviated characters) and consonants (combinations with subscript consonants vs. character sequences).

Romanization of Malayalam -- UNGEGN 4.0

The United Nations recommended system was approved in 1972 (II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports. There is no evidence of the use of the system either in India or in international cartographic products. Malayalam (Malayāḷam) uses an alphasyllabic script whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants. The romanization table is unambiguous but now outdated because since the 1970's a new orthography has been introduced and the use of many character combinations and ligatures has been simplified. Nevertheless the user of the romanization table would have to recognize many ligatures not given in the original table. The system is mostly reversible but there exist some ambiguities in the romanization of vowels (independent vs. abbreviated characters) and consonants (ligatures vs. character sequences), particularly in the case of older orthography.

Romanization of Marathi -- UNGEGN 4.0

The United Nations recommended system was approved in 1972 (II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports There is no evidence of the use of the system either in India or in international cartographic products. Marathi (Marāṭhī) uses the alphasyllabic script Devanāgarī.

Romanization of Macedonian geographical names (1977)

The United Nations recommended system was approved in 1977 (III/11), based on the romanization of the Serbo-Croatian and Macedonian Cyrillic alphabets that had long been employed in official gazetteers and maps of Yugoslavia. The table was published as an annex to the resolution (Third United Nations Conference on the Standardization of Geographical Names. Athens, 17 August - 7 September 1977. Vol. I. Report of the Conference, pp. 29, 31). The system is used in The former Yugoslav Republic of Macedonia (see e.g. Report of The former Yugoslav Republic of Macedonia. Seventh United Nations Conference on the Standardization of Geographical Names. New York, 13-22 January 1998. Document E/CONF.91/CRP.23) and in international cartographic products. The Cyrillic alphabet is used. The romanization table is unambiguous and can be applied automatically. The system is on the whole reversible with the exception of the characters ѓ and ќ. These are romanized as g and k, respectively, before е and и. But also г and к are occasionally used before е and и, so, for example, the name Makedonija is reconstituted as Македонија, not Маќедонија in the Cyrillic source script.

Romanization of Mongolian in China -- UNGEGN 4.0

The United Nations resolution III/8 in 1977 recognized the Scheme for a Chinese Phonetic Alphabet (Pinyin) as China’s official Roman alphabet scheme and recommended the alphabet as the international system for the romanization of Chinese geographical names. In China Mongolian geographical names are transcribed directly from the Mongolian script into Pinyin. The scheme was published in Toponymic Guidelines for Map and Other Editors: China, 1982. The system is used in China and in international cartographic products. Mongolian uses a vertical script. Transcription of Mongolian names is made from their proper pronunciation based on the written form of the Mongolian language and Qahar vernacular, with Zhenglan as its representative pronunciation. Due to the complex nature of the script the romanization scheme is not reversible, e.g. the name of the city Hohhot is written ᠬᠥᠬᠡᠬᠣᠲᠠ but may be transliterated as kökeqota.

Romanization of Mongolian in China -- UNGEGN 4.0 (phonetic)

The United Nations resolution III/8 in 1977 recognized the Scheme for a Chinese Phonetic Alphabet (Pinyin) as China’s official Roman alphabet scheme and recommended the alphabet as the international system for the romanization of Chinese geographical names. In China Mongolian geographical names are transcribed directly from the Mongolian script into Pinyin. The scheme was published in Toponymic Guidelines for Map and Other Editors: China, 1982. The system is used in China and in international cartographic products. Mongolian uses a vertical script. Transcription of Mongolian names is made from their proper pronunciation based on the written form of the Mongolian language and Qahar vernacular, with Zhenglan as its representative pronunciation. Due to the complex nature of the script the romanization scheme is not reversible, e.g. the name of the city Hohhot is written ᠬᠥᠬᠡᠬᠣᠲᠠ but may be transliterated as kökeqota.

Romanization of Nepali (1972)

The United Nations recommended system was approved in 1972 (II/11), based on a report prepared by D. N. Sharma. The note on the system was published in volume II of the conference report. There is no evidence of the use of the system either in Nepal or in international cartographic products. The resolution IV/17 (1982) recommended association, inter alia, with Nepal in carrying out further studies on the system. In Nepal a system of romanization is employed by the Nepal Survey Department (NSD). This system has been applied to names appearing on national mapping, and it is also used in the Geographic Information Infrastructure Programme (NGIIP). Nepali (Nepālī) uses the alphasyllabic script Devanāgarī.

Romanization of Nepali (2013)

The United Nations recommended system was approved in 1972 (II/11), based on a report prepared by D. N. Sharma. The note on the system was published in volume II of the conference report. There is no evidence of the use of the system either in Nepal or in international cartographic products. The resolution IV/17 (1982) recommended association, inter alia, with Nepal in carrying out further studies on the system. In Nepal a system of romanization is employed by the Nepal Survey Department (NSD). This system has been applied to names appearing on national mapping, and it is also used in the Geographic Information Infrastructure Programme (NGIIP). Nepali (Nepālī) uses the alphasyllabic script Devanāgarī.

Romanization of Oriya (1972)

The United Nations recommended system was approved in 1972 (II/11), based on a report prepared by D. N. Sharma. The note on the system was published in volume II of the conference reports. There is no evidence of the use of the system either in India or in international cartographic products. Oriya uses an alphasyllabic script whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants. The romanization table is unambiguous. The system is mostly reversible but there may exist some ambiguities in the romanization of vowels (independent vs. abbreviated characters) and consonants (combinations with subscript consonants vs. character sequences).

Romanization of Panjabi -- UNGEGN 4.0 (1972)

The United Nations recommended system was approved in 1972 (II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports1,2. There is no evidence of the use of the system either in India or in international cartographic products. Punjabi (Panjābī) in India uses an alphasyllabic script (Gurmukhi) whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants. The romanization table is unambiguous. The system is mostly reversible but there exist some ambiguities in the romanization of vowels (independent vs. abbreviated characters) and consonants (combinations with subscript consonants vs. character sequences). References Second United Nations Conference on the Standardization of Geographical Names. London, 10–31 May 1972. Vol. II. Technical papers. United Nations. New York 1974, pp. 136–138. Third United Nations Conference on the Standardization of Geographical Names. Athens, 17 August – 7 September 1977. Vol. II, Technical papers, pp. 393 etc.

Romanization of Persian (1967)

The United Nations recommended system was approved in 1967 ( I/13), based on the official system adopted by Iran and published in its English version as Transliteration of Farsi Geographic Names to Latin Alphabet (September 1966). The romanization table was also published as an annex to the Toponymic Guidelines for the Islamic Republic of Iran in 2000 (Toponymic Guidelines for map and other editors – Revised edition 1998. Submitted by the Islamic Republic of Iran. UNGEGN, 20th session. New York, 17-28 January 2000, Working Paper No. 41.). The system is used in the Islamic Republic of Iran and in international cartographic products. Persian (Farsi) uses the Perso-Arabic script that is written from right to left. The Persian script usually omits vowel points and diacritical marks from writing which makes it difficult to obtain uniform results in the romanization of Persian. The romanization is generally reversible though there are some ambiguous letter sequences (kh, sh, th, zh) which also may represent the romanized values of two Persian characters in addition to the respective single ones.

Romanization of Russian (1987)

The United Nations recommended system was approved in 1987 (V/18), based on the official system of the Main Administration of Geodesy and Cartography of the former Soviet Union, also known as the GOST 1983 system (GOST 16876-71). The table was published as an annex to the resolution. The system is used in the Russian Federation and increasingly in international cartographic products. Russian uses the Cyrillic script which is alphabetic. The romanization table is unambiguous and can be applied automatically. The system is reversible, although rarely there can be ambiguities.

Romanization of Sinhalese -- UNGEGN 4.0 (1972)

There does not seem to exist any national systems of romanization for Sinhalese (Sinhala) in Sri Lanka. In 1972, D. N. Sharma prepared a romanization table for Sinhalese (Sinhala) which was published in vol. II of the conference report together with the other languages of the Indian group1. Sinhalese uses an alphasyllabic script whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants.

Romanization of Serbian (1977)

The United Nations recommended system was approved in 1977 (III/11), based on the Roman equivalent of the Serbo-Croatian Cyrillic alphabet that had long been employed in official gazetteers and maps of Yugoslavia. The table was published as an annex to the resolution1. The term relating to the language (Serbian instead of Serbo-Croatian) was modified in 2002 (resolution VIII/14). The system is used in Serbia, Montenegro, and Bosnia and Herzegovina. It is also used in international cartographic products. Serbian uses the Cyrillic script that is alphabetic. The romanization table is unambiguous and can be applied automatically. The system is reversible.

Romanization of Tamil -- UNGEGN 4.0 (1972)

The United Nations recommended system was approved in 1972 (II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports. There is no evidence of the use of the system either in India, Sri Lanka or in international cartographic products. Tamil uses an alphasyllabic script whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants. The romanization table is unambiguous. The system is on the whole reversible.

Romanization of Telugu -- UNGEGN 4.0 (1972)

The United Nations recommended system was approved in 1972 (II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports. There is no evidence of the use of the system either in India or in international cartographic products. Telugu uses an alphasyllabic script whereby each character represents a syllable rather than one sound. Vowels and diphthongs are marked in two ways: as independent characters (used syllable-initially) and in an abbreviated form, to denote vowels after consonants. The romanization table is unambiguous. The system is mostly reversible but there may exist some ambiguities in the romanization of vowels (independent vs. abbreviated characters) and consonants (combinations with subscript consonants vs. character sequences).

Romanization of Belarusian, Russian And Ukrainian Cyrillic (1998)

Romanization of Ukrainian (2012)

Romanization of Urdu (1972)

The United Nations recommended system was approved in 1972 ( II/11) and amended in 1977 (III/12), based on a report prepared by D. N. Sharma. The tables and their corrections were published in volume II of the conference reports1,2. There is no evidence of the use of the system either in Pakistan, India or in international cartographic products. Instead, in Pakistan the Hunterian system is officially used3. The resolutions III/12 (1977) and IV/17 (1982) recommended association, inter alia, with Pakistan, in carrying out further studies on the system. Urdu (Urdū) uses the Perso-Arabic script which is written from right to left. In the script vowel points are usually omitted which makes it difficult to obtain uniform romanizations. Some of the Arabic consonants are undifferentiated in romanization which means that the system is not fully reversible.

Encyclopaedia Aethiopica Amharic transliteration system (2003)

The Encyclopaedia Aethiopica (EAe) is a basic encyclopedia for Ethiopian and Eritrean studies. It employs an in-house form of romanization of Geez, Amharic, and other languages, which varies greatly from standard formats, such as BGN/PCGN: the emperor Menelek II's name, for example, is written as "Mənilək II".

RABABA the Arabic Diacritization Library

Arabic diacritization is useful for several practical business cases like text to speech or Romanization of Arabic texts or scripts. This map in particular uses the RABABA library to automatically detect and add diacritics using machine learning.

Encyclopaedia Aethiopica Amharic transliteration system (2003)

The Encyclopaedia Aethiopica (EAe) is a basic encyclopedia for Ethiopian and Eritrean studies. It employs an in-house form of romanization of Geez, Amharic, and other languages, which varies greatly from standard formats, such as BGN/PCGN: the emperor Menelek II's name, for example, is written as "Mənilək II".

Hindi Hunterian system

The Hunterian system is the national system of romanization in India.

Traditional Hepburn System

This is a traditional version of Hepburn romanization.

Modified Hepburn System

This is a modified version of Hepburn romanization, which was adopted by Kenkyusha's New Japanese-English Dictionary (3rd edition) One crucial difference between Modified and Tranditional Hepburn is that the ん/ン sound is always transliterated as n, even before the letters b,m,p.

Hangul to Jamo decomposition

McCune-Reischauer System (Hangul-Latin)

E. O. Reischauer and G. M. McCune The Romanization of the Korean Language Based on Its Phonetic Structure. XXIX:1-55. Korea Branch of the Royal Asiatic Society. Volume XXIX (PDF)

Hanja Hangul Converter 0.0.7

This is a Hanja-Hangul map available in the public domain.

McCune-Reischauer System (Korean-Latin)

E. O. Reischauer and G. M. McCune The Romanization of the Korean Language Based on Its Phonetic Structure. XXIX:1-55. Korea Branch of the Royal Asiatic Society. Volume XXIX (PDF)

Marathi Hunterian system

The Hunterian system is the national system of romanization in India.

Mongolian Latin alphabet

Latin alphabet was using "y" as feminine "u", with additional feminine "o" ("ө") and with additional consonants "ç" for "ch", "ş" for "sh" and "ƶ" for "j", it successfully served in printing books and newspapers. A few of the letters (f, k, p, v) were rarely used, being found only in borrowings, while q, w and x were excluded altogether. Since k transcribed [h] in loans, it is unclear how loans in [kʰ] were written. "j" is used for vowel combinations of the [ja] type. Letter "c" is used for the sound [ts] and "k" is used for the ound [h]. The first version was inspired by the Yanalif script used for the Soviet Union's Turkic languages. The orthography of the Mongolian Latin is based on the orthography of the Classical Mongolian script. It preserves short final vowels. It does not drop unstressed vowels in the closing syllables when the word is conjugated. The suffixes and inflections without long or i-coupled vowels are made open syllables ending with a vowel, which is harmonized with the stressed vowel. The rule for the vowel harmony for unstressed vowels is similar to that of the Mongolian Cyrillic. It does not use consonant combinations to denote new consonant sounds. For both of the version, letter "b" is used both in the beginning and in the middle of the word. Because it phonetically assimilates into sound [w], no ambiguity is caused.

Lessing transliteration system for Uyghur-Mongolian script

The only system for the Mongolian vertical script which is used commonly throughout Mongolian studies worldwide is the Vladimirtsov-Mostaert system (V-M). The only dictionary using this system is in an appendix to Antoine Mostaert’s Dictionnaire ordos. Thus the Harvard Journal of Asiatic Studies specifies, “please use the written Mongolian appendix to Antoine Mostaert’s Dictionnaire ordos. However, the V-M system has many difficult diacriticals and non-Latin characters that constitute a significant problem for editors and thus is difficult to recommend.

VPMC transliteration system for Uyghur-Mongolian script

The only system for the Mongolian vertical script which is used commonly throughout Mongolian studies worldwide is the Vladimirtsov-Mostaert system (V-M). The only dictionary using this system is in an appendix to Antoine Mostaert’s Dictionnaire ordos. Thus the Harvard Journal of Asiatic Studies specifies, “please use the written Mongolian appendix to Antoine Mostaert’s Dictionnaire ordos. However, the V-M system has many difficult diacriticals and non-Latin characters that constitute a significant problem for editors and thus is difficult to recommend.

IAST Sanskrit Devanagari System (Prakrit)

The International Alphabet of Sanskrit Transliteration (IAST) is the academic standard for the romanisation of Sanskrit. IAST is the de facto standard used in printed publications, like books, magazines, and electronic texts with Unicode fonts. It is based on a standard established by the Congress of Orientalists at Athens in 1912. The International Alphabet of Sanskrit Transliteration (IAST) is a transliteration scheme that allows the lossless romanisation of Indic scripts[citation needed] as employed by Sanskrit and related Indic languages. It is based on a scheme that emerged during the nineteenth century from suggestions by Charles Trevelyan, William Jones, Monier Monier-Williams and other scholars, and formalised by the Transliteration Committee of the Geneva Oriental Congress, in September 1894.IAST makes it possible for the reader to read the Indic text unambiguously, exactly as if it were in the original Indic script. It is this faithfulness to the original scripts that accounts for its continuing popularity amongst scholars.

IAST Sanskrit Devanagari System (Sanskrit)

The International Alphabet of Sanskrit Transliteration (IAST) is the academic standard for the romanisation of Sanskrit. IAST is the de facto standard used in printed publications, like books, magazines, and electronic texts with Unicode fonts. It is based on a standard established by the Congress of Orientalists at Athens in 1912. The International Alphabet of Sanskrit Transliteration (IAST) is a transliteration scheme that allows the lossless romanisation of Indic scripts[citation needed] as employed by Sanskrit and related Indic languages. It is based on a scheme that emerged during the nineteenth century from suggestions by Charles Trevelyan, William Jones, Monier Monier-Williams and other scholars, and formalised by the Transliteration Committee of the Geneva Oriental Congress, in September 1894.IAST makes it possible for the reader to read the Indic text unambiguously, exactly as if it were in the original Indic script. It is this faithfulness to the original scripts that accounts for its continuing popularity amongst scholars.

Wade-Giles

Chinese Wade-Giles 1979 System