Romanization

From Infogalactic: the planetary knowledge core
(Redirected from Romanize)
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

For other uses, see Romanization (disambiguation).

Lua error in package.lua at line 80: module 'strict' not found.

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

Romanization or Latinization (or romanisation, latinisation: see spelling differences), in linguistics, is the conversion of writing from a different writing system to the Roman (Latin) script, or a system for doing so. Methods of romanization include transliteration, for representing written text, and transcription, for representing the spoken word, and combinations of both. Transcription methods can be subdivided into phonemic transcription, which records the phonemes or units of semantic meaning in speech, and more strict phonetic transcription, which records speech sounds with precision.

Methods

There are many consistent or standardized romanization systems. They can be classified by their characteristics. A particular system’s characteristics may make it better-suited for various, sometimes contradictory applications, including document retrieval, linguistic analysis, easy readability, faithful representation of pronunciation.

  • Source, or donor language – A system may be tailored to romanize text from a particular language, or a series of languages, or for any language in a particular writing system. A language-specific system typically preserves language features like pronunciation, while the general one may be better for cataloguing international texts.
  • Target, or receiver language – Most systems are intended for an audience that speaks or reads a particular language. (So-called international romanization systems for Cyrillic text are based on central-European alphabets like the Czech and Croatian alphabet.)
  • Simplicity – Since the basic Latin alphabet has a smaller number of letters than many other writing systems, digraphs, diacritics, or special characters must be used to represent them all in Latin script. This affects the ease of creation, digital storage and transmission, reproduction, and reading of the romanized text.
  • Reversibility – Whether or not the original can be restored from the converted text. Some reversible systems allow for an irreversible simplified version.

Transliteration

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: 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 kana syllables with 100% accuracy, but requires additional knowledge for correct pronunciation.

Transcription

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Transcription (linguistics)

Phonemic

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

See also: Phonemic orthography

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 phonemic transcription and attempt to render the significant sounds (phonemes) of the original as faithfully as possible in the target language. The popular Hepburn romanization of Japanese is an example of a transcriptive romanization designed for English speakers.

Phonetic

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

See also: Phonetic transcription

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 coarticulation 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 spoken language with perfect accuracy and the vocal interpretation of a script 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, jūjutsu.

Romanization of specific writing systems

The below listing may be incomplete, see also Category:Romanization

Arabic

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Arabic

The Arabic alphabet is used to write Arabic, Persian, Urdu and Pashto as well as numerous other languages in the Muslim world, particularly African and Asian languages without alphabets of their own. Romanization standards include the following:

Persian

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Persian

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

See also: Category:Persian orthography

Armenian

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Armenian

Lua error in package.lua at line 80: module 'strict' not found.

Georgian

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Georgian

Lua error in package.lua at line 80: module 'strict' not found.

Greek

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Greek

There are romanization systems for both Modern and Ancient Greek.

Hebrew

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Hebrew

The Hebrew alphabet is romanized using several standards:

Indic (Brahmic) scripts

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

See also: Devanagari transliteration, Romanization of Bengali, and Romanization of Malayalam

The Brahmic family 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.[13]

  • ISO 15919 (2001): A standard transliteration convention was codified in the ISO 15919 standard. It uses diacritics to map the much larger set of Brahmic consonants and vowels to the Latin script. See also Transliteration of Indic scripts: how to use ISO 15919.[14] 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,[15] although there are a few differences
  • The National Library at Kolkata romanization, intended for the romanization of all Indic scripts, is an extension of IAST
  • Harvard-Kyoto: Uses upper and lower case and doubling of letters, to avoid the use of diacritics, and to restrict the range to 7-bit ASCII.
  • ITRANS: a transliteration scheme into 7-bit ASCII created by Avinash Chopde that used to be prevalent on Usenet.
  • ISCII (1988)

Devanagari–nastaʿlīq (Hindustani)

Hindustani is an Indo-Aryan language with extreme digraphia and diglossia resulting from the Hindi–Urdu controversy starting in the 1800s. Technically, Hindustani itself is recognized by neither the language community nor any governments. Two standardized registers, Standard Hindi and Standard Urdu, are recognized as official languages in India and Pakistan. However, in practice the situation is,

  • In Pakistan: Standard (Saaf) Urdu is the "high" variety, whereas Hindustani is the "low" variety used by the masses (called Urdu, written in nastaʿlīq script).
  • In India, both Standard (Shuddh) Hindi and Standard (Saaf) Urdu are the "H" varieties (written in devanagari and nastaʿlīq respectively), whereas Hindustani is the "L" variety used by the masses and written in either devanagari or nastaʿlīq (and called 'Hindi' or 'Urdu' respectively).

The digraphia renders any work in either script largely inaccessible to users of the other script, though otherwise Hindustani is a perfectly mutually intelligible language, essentially meaning that any kind of text-based open source collaboration is impossible among devanagari and nastaʿlīq readers.

Initiated in 2011, the Hamari Boli Initiative[16] is a full-scale open-source language planning initiative aimed at Hindustani script, style, status & lexical reform and modernization. One of primary stated objectives of Hamari Boli is to relieve Hindustani of the crippling devanagari–nastaʿlīq digraphia by way of romanization.[17]

Chinese

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Chinese

Romanization of the Sinitic languages, particularly Mandarin, 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

Mainland China
  • Hanyu Pinyin (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 Singapore 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 dialects, 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

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Chinese language romanization in Taiwan
  1. Gwoyeu Romatzyh (GR, 1928–1986, in Taiwan 1945–1986; Taiwan used Japanese Romaji before 1945),
  2. Mandarin Phonetic Symbols II (MPS II, 1986–2002),
  3. Tongyong Pinyin (2002–2008),[20][21] and
  4. Hanyu Pinyin (since January 1, 2009).[22][23]
Singapore

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Chinese language romanisation in Singapore

Cantonese

Min Nan

  • Pe̍h-ōe-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 Min Nan was not commonly written in Chinese.
  • Guangdong (1960), for the distinct Teochow variety.

Min Dong

Japanese

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Japanese

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

  • Hepburn (1867): transcription to Anglo-American practices, used in geographical names
  • Nihon-shiki (1885): transliteration. Also adopted as (ISO 3602 Strict) in 1989.
  • Kunrei-shiki (1937): transliteration. Also adopted as (ISO 3602).
  • JSL (1987): transcription. Named after the book Japanese: The Spoken Language by Eleanor Jorden.
  • ALA-LC: Similar to Modified Hepburn[24]
  • Wāpuro: ("word processor romanization") transliteration. Not strictly a system, but a collection of common practices that enables input of Japanese text.

Korean

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of 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 Korean 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 ’.[25]

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 macron. 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 that 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 grandfathered 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 hyphen, but this is inconsistently applied in practice.
  • ISO/TR 11941 (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.[26]
  • Lukoff romanization, developed 1945–47 for his Spoken Korean coursebooks[27]

Philippine languages

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Filipino orthography

Almost all Languages of the Philippines (including Tagalog, Ilokano, the Bicol languages, Cebuano and other Visayan languages, Kapampangan, and the Spanish-based creole Chavacano) use the Modern Filipino Alphabet.

When Spain colonised the Philippines in the late 16th century, the numerous languages of the Philippines were written in various scripts, such as Baybayin. These were initially promoted by the colonists but later replaced by Spanish transcriptions, which are still evident in place names and surnames. Letters such as C, Ll, and Ñ were considered Hispanic additions and removed in the Abakada, an attempt at a more indigenous alphabet devised by Lope K. Santos in 1940. These were eventually superseded by the Pilipino Alphabet and by the 28-letter, Modern Filipino Alphabet, which adds Ñ and the native Ng to the standard, 26-letter Latin alphabet.

While the Spanish language itself uses a very phonemic spelling, the romanised spelling created for Philippine languages is even more so. For example, the Spanish caballo ([kaˈβa.ʎo], "horse"), the same word in Tagalog is kabayo (demonstrating yeismo in the pronunciation of the Spanish "Ll" digraph).

Thai

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Thai

Thai, spoken in Thailand 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.

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 Glagolitic alphabets. This applies to Old Church Slavonic, as well as modern Slavic languages that use these alphabets.

Belarusian

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Belarusian

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

See also: Belarusian Latin alphabet

Bulgarian

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Bulgarian

A system based on scientific transliteration 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.[30] Where the old system uses <č,š,ž,št,j,ă>, the new system uses <ch,sh,zh,sht,y,a>.

The new Bulgarian system was endorsed also by UN [31] in 2012 and by BGN and PCGN[32] in 2013.

Kyrgyz

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Kyrgyz

Lua error in package.lua at line 80: module 'strict' not found.

Macedonian

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Macedonian

Lua error in package.lua at line 80: module 'strict' not found.

Russian

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Russian

There is no single universally accepted system of writing Russian 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).[33]
  • 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 International Organization for Standardization.
  • ALA-LC (1997)[34]
  • "Volapuk" encoding (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 Romanization of Russian.
  • Streamlined system[35] for the transliteration of Russian
  • Comparative transliteration of Russian[36] in different languages (Western European, Arabic, Georgian, Braille, Morse)

Ukrainian

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Romanization of Ukrainian

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

  • ALA-LC[37]
  • ISO 9
  • Ukrainian National transliteration[38]
  • Ukrainian National and BGN/PCGN systems, at the UN Working Group on Romanization Systems[39]
  • Thomas T. Pedersen's comparison of five systems[40]

See also: Ukrainian Latin alphabet

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 Greek Russian (Cyrillic) Hebrew Arabic Persian Katakana Hangul
A A А ַ, ֲ, ָ َ, ا ا, آ ア ㅏ
AE ΑΙ ㅐ
AI י ַ
B ΜΠ, Β Б בּ ﺏ ﺑ ﺒ ﺐ ﺏ ﺑ ㅂ
C Ξ
CH TΣ̈ Ч צ׳ چ ㅊ
CHI チ
D ΝΤ, Δ Д ד ﺩ — ﺪ, ﺽ ﺿ ﻀ ﺾ د ㄷ
DH Δ דֿ ﺫ — ﺬ
DZ ΤΖ Ѕ
E Ε, ΑΙ Э , ֱ, י ֵֶ, ֵ, י ֶ エ, ヱ ㅔ
EO ㅓ
EU ㅡ
F Φ Ф פ (or its final form ף ) ﻑ ﻓ ﻔ ﻒ ﻑ
FU フ
G ΓΓ, ΓΚ, Γ Г ג گ ㄱ
GH Γ Ғ גֿ, עֿ ﻍ ﻏ ﻐ ﻎ ق غ
H Η Һ ח, ה ﻩ ﻫ ﻬ ﻪ, ﺡ ﺣ ﺤ ﺢ ه ح ﻫ ㅎ
HA ハ
HE ヘ
HI ヒ
HO ホ
I Η, Ι, Υ, ΕΙ, ΟΙ И ִ, י ִ دِ イ, ヰ ㅣ
IY دِي
J TZ̈ ДЖ, Џ ג׳ ﺝ ﺟ ﺠ ﺞ ج ㅈ
JJ ㅉ
K Κ К כּ (or its final form ךּ ) ﻙ ﻛ ﻜ ﻚ ک ㅋ
KA カ
KE ケ
KH X Х כ, חֿ (or its final form ך ) ﺥ ﺧ ﺨ ﺦ خ
KI キ
KK ㄲ
KO コ
KU ク
L Λ Л ל ﻝ ﻟ ﻠ ﻞ ل ㄹ
M Μ М מ (or its final form ם ) ﻡ ﻣ ﻤ ﻢ م ㅁ
MA マ
ME メ
MI ミ
MO モ
MU ム
N Ν Н נ (or its final form ן ) ﻥ ﻧ ﻨ ﻦ ن ン ㄴ
NA ナ
NE ネ
NG ㅇ
NI ニ
NO ノ
NU ヌ
O Ο, Ω О , ֳ, וֹֹ ُا オ ㅗ
OE ㅚ
P Π П פּ (or its final form ףּ ) پ ㅍ
PP ㅃ
PS Ψ
Q Θ ק ﻕ ﻗ ﻘ ﻖ غ ق
R Ρ Р ר ﺭ — ﺮ ر ㄹ
RA ラ
RE レ
RI リ
RO ロ
RU ル
S Σ С ס, שׂ ﺱ ﺳ ﺴ ﺲ, ﺹ ﺻ ﺼ ﺺ س ث ص ㅅ
SA サ
SE セ
SH Σ̈ Ш שׁ ﺵ ﺷ ﺸ ﺶ ش
SHCH Щ
SHI シ
SO ソ
SS ㅆ
SU ス
T Τ Т ט, תּ, ת ﺕ ﺗ ﺘ ﺖ, ﻁ ﻃ ﻄ ﻂ ت ط ㅌ
TA タ
TE テ
TH Θ תֿ ﺙ ﺛ ﺜ ﺚ
TO ト
TS ΤΣ Ц צ (or its final form ץ )
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

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ [1] Archived January 29, 2006 at the Wayback Machine
  10. ↑ [2] Archived December 10, 2004 at the Wayback Machine
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ The News International - Dec 29, 2011 -- "Hamari Boli (our language) is perhaps one of the very first serious undertakings to explore, develop and encourage the growth of Roman script in the use of Urdu/Hindi language"
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ [3] Archived February 14, 2006 at the Wayback Machine
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ State Gazette # 19, Sofia, 13 March 2009. (in Bulgarian)
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ [4] Archived December 19, 2007 at the Wayback Machine
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ [5] Archived March 7, 2005 at the Wayback Machine
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

About Romanization:

Romanization Online:

Retrieved from "https://infogalactic.com/w/index.php?title=Romanization&oldid=125070"