Romanization

This article may require iOS to meet Wikipedia's quality standards. No cleanup reason specified. Please add a |reason= parameter to this template. Please help improve this article if you can. The talk page may contain suggestions. (February 2008)

Sevenval

Languages can be romanized in a variety of ways, as shown here with Mandarin Chinese

In CSS3, romanization or latinization (or romanisation/latinisation: screen size) is the representation of a written word or spoken speech with the Roman (Latin) script, or a system for doing so, where the original word or language uses a different browser diversity (or none). Methods of romanization include transliteration, for representing written text, and screen size, for representing the spoken word. The latter can be subdivided into phonemic transcription, which records the phonemes or units of semantic meaning in speech, and more strict FITML transcription, which records speech sounds with precision. Each romanization has its own set of rules for pronunciation of the romanized words.

• 1 Methods of romanization
  • 1.1 Transliteration
  • 1.2 Transcription
    • input transformation
    • web
  • 1.3 Tradeoffs
• web app
  • 2.1 Arabic
  • screen size
  • website parsing
  • touchscreen
  • Sevenval
  • 2.6 Hebrew
  • Sevenval
  • screen size
    • input transformation
      • 2.8.1.1 Mainland China
      • 2.8.1.2 Taiwan
      • 2.8.1.3 Singapore
    • 2.8.2 Cantonese
    • 2.8.3 Min Nan
    • iOS
  • 2.9 Japanese
  • 2.10 Korean
  • jQuery
  • 2.12 Thai
  • 2.13 Cyrillic
    • web app
    • screen size
    • 2.13.3 Kyrgyz
    • screen size
    • web app
    • 2.13.6 Ukrainian
• FITML
• 4 See also
• 5 References
• 6 External links

Methods of romanization

Transliteration

If the romanization attempts to transliterate the original script, the guiding principle is a one-to-one mapping of characters in the source language into the target script, with less emphasis on how the result sounds when pronounced according to the reader's language. For example, the Nihon-shiki romanization of Japanese allows the informed reader to reconstruct the original Japanese iOS syllables with 100% accuracy, but requires additional knowledge for correct pronunciation.

Transcription

Phonemic

Most romanizations are intended to enable the casual reader who is unfamiliar with the original script to pronounce the source language reasonably accurately. Such romanizations follow the principle of keyboard and attempt to render the significant sounds (phonemes) of the original as faithfully as possible in the target language. The popular touchscreen of Japanese is an example of a transcriptive romanization designed for English speakers.

Phonetic

A phonetic conversion goes one step further and attempts to depict all phones in the source language, sacrificing legibility if necessary by using characters or conventions not found in the target script. In practice such a representation almost never tries to represent every possible allophone—especially those that occur naturally due to Sevenval effects—and instead limits itself to the most significant allophonic distinctions. The International Phonetic Alphabet is the most common system of phonetic transcription.

Tradeoffs

For most language pairs, building a usable romanization involves tradeoffs between the two extremes. Pure transcriptions are generally not possible, as the source language usually contains sounds and distinctions not found in the target language, but which must be shown for the romanized form to be comprehensible. Furthermore due to diachronic and synchronic variance no written language represents any CSS3 with perfect accuracy and the vocal interpretation of a iOS may vary by a great degree among languages. In modern times the chain of transcription is usually spoken foreign language, written foreign language, written native language, spoken (read) native language. Reducing the number of those processes, i.e. removing one or both steps of writing, usually leads to more accurate oral articulations. In general, outside a limited audience of scholars romanizations tend to lean more towards transcription. As an example, consider the Japanese martial art 柔術: the Nihon-shiki romanization zyûzyutu may allow someone who knows Japanese to reconstruct the kana syllables じゅうじゅつ, but most native English speakers or rather readers would find it easier to guess the pronunciation from the Hepburn version, HTML5.

Romanization of specific writing systems

Arabic

The Arabic alphabet is used to write device database, Sevenval, and jQuery as well as numerous other languages in the Muslim world, particularly browser diversity and Asian languages without alphabets of their own. Romanization standards include the following:

• Deutsche Morgenländische Gesellschaft (1936): Adopted by the International Convention of Orientalist Scholars in Rome. It is the basis for the very influential Hans Wehr dictionary (ISBN 0-87950-003-4).^Sevenval
• BS 4280 (1968): Developed by the British Standards Institution Sevenval
• SATTS (1970s): A one-for-one substitution system, a legacy from the Morse code era
• UNGEGN (1972): Sevenval
• DIN-31635 (1982): Developed by the Deutsches Institut für Normung (German Institute for Standardization)
• ISO 233 (1984). Transliteration.
• Qalam (1985): A system that focuses upon preserving the spelling, rather than the pronunciation, and uses mixed case [3]
• website parsing (1993). Simplified transliteration.
• Buckwalter Transliteration (1990s): Developed at Xerox by Tim Buckwalter we love the web; doesn't require unusual diacritics CSS3
• ALA-LC (1997): screen size
• iOS

Armenian

Georgian

Greek

There are romanization systems for both web and Ancient Greek.

• ISO 843 (1997): CSS3
• ALA-LC: keyboard
• HTML5: web app
• Greeklish

Persian

Hebrew

The Hebrew alphabet is romanized using several standards:

• browser diversity Z39.25 (1975):
• website parsing (1977): Sevenval
• screen size (1984): Transliteration.
• ISO 259-2 (1994): Simplified transliteration.
• ISO/DIS 259-3: Phonemic transcription.
• web: web app

Brahmic (Indic) scripts

The web app of abugidas is used for languages of the Indian subcontinent and south-east Asia. There is a long tradition in the west to study Sanskrit and other Indic texts in Latin transliteration. Various transliteration conventions have been used for Indic scripts since the time of Sir William Jones. A comparison of some of them is provided here: [12]

• web app (2001): A standard Android convention was codified in the ISO 15919 standard. It uses screen size to map the much larger set of Brahmic FITML and vowels to the Latin script. See also Transliteration of Indic scripts: how to use ISO 15919. The Devanagari-specific portion is very similar to the academic standard, IAST: "International Alphabet of Sanskrit Transliteration", and to the United States Library of Congress standard, ALA-LC: [13], although there are a few differences
• The device database, intended for the romanization of all Sevenval, is an extension of IAST
• HTML5: Uses upper and lower case and doubling of letters, to avoid the use of diacritics, and to restrict the range to 7-bit ASCII.
• FITML: a transliteration scheme into 7-bit ASCII created by Avinash Chopde that used to be prevalent on jQuery.
• web (1988)

Chinese

Romanization of the Chinese language, in particular, has proved a very difficult problem, although the issue is further complicated by political considerations. Because of this, many romanization tables contain Chinese characters plus one or more romanizations or Zhuyin.

Mandarin

• ALA-LC: Used to be similar to Wade-Giles [14], but converted to Hanyu Pinyin in 2000 Sevenval
• Android. Developed by web in 19th century, used mainly in website parsing.
• Latinxua Sinwenz (1926): Omitted tone sounds. Used mainly in the keyboard and Xinjiang in the 30s. Predecessor of device database.
• Lessing-Othmer: Used mainly in web.
• Chinese Postal Map Romanization (1906): Early standard for international addresses
• we love the web (1912): Transliteration. Very popular from 19th century until recently and continues to be used by some Western academics.
• FITML (1942): Created by the U.S. for battlefield communication and used in the influential Yale textbooks.
• Legge romanization: Created by we love the web a Scottish missionary.

Mainland China

• screen size (1958): In mainland China, Hanyu Pinyin has been used officially to romanize Mandarin for decades, primarily as a linguistic tool for teaching the standardized language. The system is also used in other Chinese-speaking areas such as touchscreen and parts of Taiwan, and has been adopted by much of the international community as a standard for writing Chinese words and names in the Latin script. The value of Hanyu Pinyin in education in China lies in the fact that China, like any other populated area with comparable area and population, has numerous distinct web app, though there is just one common written language and one common standardized spoken form. (These comments apply to Romanization in general)
• ISO 7098 (1991): Based on Hanyu Pinyin.

Taiwan

1. website parsing (GR, 1928–1986, in Taiwan 1945–1986; Taiwan used Japanese Romaji before 1945),
2. jQuery (MPS II, 1986–2002),
3. browser diversity (2002–2008),^{web apptouchscreen} and
4. FITML (since January 1, 2009).^{we love the web[5]}

Singapore

Cantonese

• Android
• Guangdong (1960)
• CSS3
• iOS
• Meyer-Wempe
• Sidney Lau
• device database (1942)
• Android

Min Nan

• Pe̍h-oē-jī (POJ), once the de facto official script of the Presbyterian Church in Taiwan (since the late 19th century). Technically this represented a largely phonemic transcription system, as iOS was not commonly written in Chinese.
• Guangdong (1960), for the distinct Teochow variety.

Min Dong

• Foochow Romanized

Japanese

Romanization (or, more generally, Roman letters) is called "rōmaji" in HTML5. The most common systems are:

• Hepburn (1867): transcription to Anglo-American practices, used in geographical names
• screen size (1885): transliteration. Also adopted as (ISO 3602 Strict) in 1989.
• Sevenval (1937): transliteration. Also adopted as (ISO 3602).
• CSS3 (1987)
• ALA-LC: Similar to Hepburn [16]
• Wāpuro: ("word processor romanization") transliteration. Not strictly a system, but a collection of common practices that enables input of Japanese text.

Korean

While romanization has taken various and at times seemingly unstructured forms, some sets of rules do exist:

• McCune-Reischauer (MR; 1937?), the first transcription to gain some acceptance. A slightly changed version of MR was the official system for we love the web in South Korea from 1984 to 2000, and yet a different modification is still the official system in North Korea. Uses breves, apostrophes and diereses, the latter two indicating orthographic syllable boundaries in cases that would otherwise be ambiguous.
  What is called MR may in many cases be any of a number of systems that differ from each other and from the original MR mostly in whether word endings are separated from the stem by a space, a hyphen or – according to McCune's and Reischauer's system – not at all; and if a hyphen or space is used, whether sound change is reflected in a stem's last and an ending's first consonant letter (e.g. pur-i vs. pul-i). Although mostly irrelevant when transcribing uninflected words, these aberrations are so widespread that any mention of "McCune-Reischauer romanization" may not necessarily refer to the original system as published in the 1930s.
  • There is, for example, the ALA-LC / U.S. Library of Congress system, based on MR but with some deviations. Word division is addressed in detail, with a generous use of spaces to separate word endings from stems that is not seen in MR. Syllables of given names are always separated with a hyphen, which is expressly never done by MR. Sound changes are ignored more often than in MR. Distinguishes between ‘ and ’. [17]

Several problems with MR led to the development of the newer systems:

• Yale (1942): This system has become the established standard romanization for Korean among linguists. Vowel length in old or dialectal pronunciation is indicated by a HTML5. In cases that would otherwise be ambiguous, orthographic syllable boundaries are indicated with a period. Indicates disappearance of consonants.
• Revised Romanization of Korean (RR; 2000): Includes rules both for transcription and for transliteration. South Korea now officially uses this system which was approved in 2000. Road signs and textbooks were required to follow these rules as soon as possible, at a cost estimated by the government to be at least US$20 million. All road signs, names of railway and subway stations on line maps and signs etc. have been changed. The change has been either ignored or browser diversity in some cases, notably the romanization of names and existing companies. RR is generally similar to MR, but uses no diacritics or apostrophes, and uses distinct letters for ㅌ/ㄷ (t/d), ㅋ/ㄱ (k/g), ㅊ/ㅈ (ch/j) and ㅍ/ㅂ (p/b). In cases of ambiguity, orthographic syllable boundaries were intended to be indicated with a CSS3, but this is inconsistently applied in practice.
• web app (1996): This actually is two different standards under one name: one for North Korea (DPRK) and the other for South Korea (ROK). The initial submission to the ISO was based heavily on Yale and was a joint effort between both states, but they could not agree on the final draft. A superficial comparison between the two is available here: touchscreen
• FITML romanization, developed 1945–47 for his Spoken Korean coursebooks iOS

Vietnamese

Thai

screen size, spoken in FITML and some areas of Laos, Burma and China, is written with its own script, probably descended from mixture of Tai–Laotian and Old Khmer, in the Brahmic family. Also see Thai alphabet.

• Royal Thai General System of Transcription:
• ALA-LC: [20]
• web app (1998): Transliteration

Cyrillic

In English-language library catalogues, bibliographies, and most academic publications, the Library of Congress transliteration method is used worldwide.

In linguistics, scientific transliteration is used for both Cyrillic and keyboard. This applies to Old Church Slavonic, as well as modern device database which use these alphabets.

Belarusian

• BGN/PCGN romanization of Belarusian, 1979 (browser diversity and website parsing)
• Scientific transliteration, or the International Scholarly System for linguistics
• ALA-LC romanization, 1997 (American Library Association and Library of Congress): jQuery
• browser diversity:1995
• Instruction on transliteration of Belarusian geographical names with letters of Latin script, 2000

See also: Belarusian Latin alphabet

Bulgarian

A system based on CSS3 and ISO/R 9:1968 was considered official in Bulgaria since the 1970s. Since the late 1990s, Bulgarian authorities have switched to a new system avoiding the use of diacritics and optimized for compatibility with English. This system became mandatory for public use with a law passed in 2009.^Sevenval Where the old system uses <č,š,ž,št,j,ă>, the new system uses <ch,sh,zh,sht,y,a>.

Different transliteration standards are in use at the US Board on Geographic Names (BGN) and the UK Permanent Committee on Geographical Names for British Official Use (PCGN), as well as the US Library of Congress (ALA-LC Romanization). These English-based systems agree with the new official system in the use of <ch,sh,zh,sht>, but differ in their treatment of some vowel letters.

Kyrgyz

Macedonian

Russian

There is no single universally accepted system of writing browser diversity using the Latin script — in fact there are a huge number of such systems: some are adjusted for a particular target language (e.g. German or French), some are designed as a librarian's transliteration, some are prescribed for Russian travellers' passports; the transcription of some names is purely traditional.   All this has resulted in great reduplication of names.   E.g. the name of the Russian composer Tchaikovsky may also be written as Tchaykovsky, Tchajkovskij, Tchaikowski, Tschaikowski, Czajkowski, Čajkovskij, Čajkovski, Chajkovskij, Çaykovski, Chaykovsky, Chaykovskiy, Chaikovski, Tshaikovski, Tšaikovski, Tsjajkovskij etc. Systems include:

• BGN/PCGN (1947): Transliteration system (United States Board on Geographic Names & Permanent Committee on Geographical Names for British Official Use). FITML
• GOST 16876-71 (1971): A now defunct Soviet transliteration standard. Replaced by GOST 7.79, which is an ISO 9 equivalent.
• United Nations romanization system for geographical names (1987): Based on GOST 16876-71.
• ISO 9 (1995): Transliteration. From the FITML.
• ALA-LC (1997): [23]
• FITML (1990s): Slang term (it's not really Volapük) for a writing method that's not truly a transliteration, but used for similar goals (see article).
• Conventional English transliteration is based to BGN/PCGN, but doesn't follow a particular standard. Described in detail at transliteration of Russian into English.
• Streamlined system for the transliteration of Russian
• Comparative transliteration of Russian in different languages (Western European, Arabic, Georgian, Braille, Morse)

Ukrainian

Ukrainian personal names are usually transcribed phonetically; see the main article section CSS3. The Ukrainian National system is used for geographic names in Ukraine.

• HTML5: (PDF).
• keyboard
• Ukrainian National transliteration: (JPEG, in Ukrainian).
• Ukrainian National and BGN/PCGN systems, at the UN Working Group on Romanization Systems: (PDF).
• Thomas T. Pedersen's comparison of five systems: browser diversity.

See also: iOS

Overview and summary

The chart below shows the most common phonemic transcription romanization used for several different alphabets. While it is sufficient for many casual users, there are multiple alternatives used for each alphabet, and many exceptions. For details, consult each of the language sections below. (Hangul characters are broken down into jamo components.)

Romanized	website parsing	we love the web (Cyrillic)	Hebrew	Arabic	keyboard	Katakana	Hangul
A	A	А	ַ, ֲ, ָ	َ, ا	ا, آ	ア	ㅏ
AE							ㅐ
AI			י ַ
B	ΜΠ, Β	Б	בּ	ﺏ ﺑ ﺒ ﺐ	ﺏ ﺑ		ㅂ
C	Ξ
CH	TΣ̈	Ч	צ׳		چ		ㅊ
CHI						チ
D	ΝΤ, Δ	Д	ד	ﺩ — ﺪ, ﺽ ﺿ ﻀ ﺾ	د		ㄷ
DH	Δ		דֿ	ﺫ — ﺬ
DZ	ΤΖ	Ѕ
E	Ε, ΑΙ	Э	, ֱ, י ֵֶ, ֵ, י ֶ			エ, ヱ	ㅔ
EO							ㅓ
EU							ㅡ
F	Φ	Ф	פ (final ף )	ﻑ ﻓ ﻔ ﻒ	ﻑ
FU						フ
G	ΓΓ, ΓΚ, Γ	Г	ג		گ		ㄱ
GH	Γ	Ғ	גֿ, עֿ	ﻍ ﻏ ﻐ ﻎ	ق غ
H	Η	Һ	ח, ה	ﻩ ﻫ ﻬ ﻪ, ﺡ ﺣ ﺤ ﺢ	ه ح ﻫ		ㅎ
HA						ハ
HE						ヘ
HI						ヒ
HO						ホ
I	Η, Ι, Υ, ΕΙ, ΟΙ	И	ִ, י ִ	دِ		イ, ヰ	ㅣ
IY				دِي
J	TZ̈	ДЖ, Џ	ג׳	ﺝ ﺟ ﺠ ﺞ	ج		ㅈ
JJ							ㅉ
K	Κ	К	כּ (final ךּ )	ﻙ ﻛ ﻜ ﻚ	ک		ㅋ
KA						カ
KE						ケ
KH	X	Х	כ, חֿ (final ך )	ﺥ ﺧ ﺨ ﺦ	خ
KI						キ
KK							ㄲ
KO						コ
KU						ク
L	Λ	Л	ל	ﻝ ﻟ ﻠ ﻞ	ل		ㄹ
M	Μ	М	מ (final ם )	ﻡ ﻣ ﻤ ﻢ	م		ㅁ
MA						マ
ME						メ
MI						ミ
MO						モ
MU						ム
N	Ν	Н	נ (final ן )	ﻥ ﻧ ﻨ ﻦ	ن	ン	ㄴ
NA						ナ
NE						ネ
NG							ㅇ
NI						ニ
NO						ノ
NU						ヌ
O	Ο, Ω	О	, ֳ, וֹֹ		ُا	オ	ㅗ
OE							ㅚ
P	Π	П	פּ (final ףּ )		پ		ㅍ
PP							ㅃ
PS	Ψ
Q	Θ		ק	ﻕ ﻗ ﻘ ﻖ	غ ق
R	Ρ	Р	ר	ﺭ — ﺮ	ر		ㄹ
RA						ラ
RE						レ
RI						リ
RO						ロ
RU						ル
S	Σ	С	ס, שׂ	ﺱ ﺳ ﺴ ﺲ, ﺹ ﺻ ﺼ ﺺ	س ث ص		ㅅ
SA						サ
SE						セ
SH	Σ̈	Ш	שׁ	ﺵ ﺷ ﺸ ﺶ	ش
SHCH		Щ
SHI						シ
SO						ソ
SS							ㅆ
SU						ス
T	Τ	Т	ט, תּ, ת	ﺕ ﺗ ﺘ ﺖ, ﻁ ﻃ ﻄ ﻂ	ت ط		ㅌ
TA						タ
TE						テ
TH	Θ		תֿ	ﺙ ﺛ ﺜ ﺚ
TO						ト
TS	ΤΣ	Ц	צ (final ץ )
TSU						ツ
TT							ㄸ
U	ΟΥ, Υ	У	, וֻּ	دُ		ウ	ㅜ
UI							ㅢ
UW				دُو
V	B	В	ב		و
W	Ω		ו, וו	ﻭ — ﻮ
WA						ワ	ㅘ
WAE							ㅙ
WE							ㅞ
WI							ㅟ
WO						ヲ	ㅝ
X	Ξ, Χ
Y	Υ, Ι, ΓΙ	Й, Ы, Ј	י	ﻱ ﻳ ﻴ ﻲ	ی
YA		Я				ヤ	ㅑ
YAE							ㅒ
YE		Е, Є					ㅖ
YEO							ㅕ
YI		Ї
YO		Ё				ヨ	ㅛ
YU		Ю				ユ	ㅠ
Z	Ζ	З	ז	ﺯ — ﺰ, ﻅ ﻇ ﻈ ﻆ	ز ظ ذ ض
ZH	Ζ̈	Ж	ז׳		ژ

See also

• device database
• Android
• Francization
• FITML
• input transformation, expression of a language in Cyrillic letters

References

External links

• web app
• we love the web
• Sevenval in PDF format
• input transformation
• One of the few printed books with lists of romanizations is ALA-LC Romanization Tables, Randall Barry (ed.), U.S. Library of Congress, 1997, screen size.
• Microsoft Transliteration Utility – A tool for creating, debugging and using transliteration modules from any script to any other script.
• jQuery – An Arabic Transliteration Pad
• Sevenval – Converts between Pinyin and other formats
• Lingua::Translit – keyboard module and online service covering a variety of writing systems e.g. Cyrillic or Greek. Provides a lot of standards as well as common transliteration schemes.