Wikipedia:WikiProject Korea/Romanization of Korean on Wikipedia

Essay on editing Wikipedia From Wikipedia, the free encyclopedia

This essay serves as a companion to Wikipedia:Manual of Style/Korea-related articles and Wikipedia:Naming conventions (Korean). It provides detailed explanations of the choices related to romanization made in those guidelines (namely for when the explanations would be too lengthy), and also serves as an FAQ page.

The arguments in this page should not be interpreted as authoritative; this page just explains the current community consensus. When the MOS:KO or WP:NCKO change, this page should be updated to reflect the new consensus. This article should also ideally contain references for claims made, be discussed, and be challenged in order to improve robustness and usefulness.

Purpose

Our main goal is to make editing and reading Wikipedia easier for the average person.

Our guidelines and explanations are complicated and boring to most. You don't need to know all of it to be a good editor. These resources exist just to solve repetitive debates in advance and to standardize things.

Background

Note: For abbreviations such as "RR" and "MR", see § Romanization systems in use on Wikipedia.

The romanization of Korean is unfortunately really complicated.

  • Korean does not have a widespread standard romanization system.
    • Currently, North Korea, South Korea, South Korean English-language academia, international academia, linguists, South Korean English-language media, and the international media all promote different standards. Many organizations also have individual style guides that modify standard romanization practices. Many of these groups have also changed their preferred systems and guidelines over time.
      • Some have intense opinions on the merits of each romanization system, and refuse to use (or even acknowledge the legitimacy of) systems they dislike.[a]
      • Academics and book authors sometimes pick and choose which romanization system to use based on personal preference (and many, even after nominally picking a system to use, romanize incorrectly, either by mistake[1] or in order to reflect a perceived common practice).
    • Many Koreans still regularly use ad hoc romanizations.
    • Many dated or ad hoc spellings have become widespread and persistent.
      • Some Korean words with unusual romanizations have been adopted into the English language, like "chaebol".[2]
    • On Wikipedia, extremely few people understand how any of the Korean romanization systems work in detail. A large portion of Korea-related Wikipedia articles still have romanization mistakes in them, especially in {{Infobox Korean name}}.
    • Outside of Wikipedia, a significant proportion of published works (even those by academics) have romanization mistakes in them.
      • Native Korean speakers often find RR and MR unintuitive, as the systems reflect pronunciation rules that many Korean speakers are not consciously aware of.[3][4][b]
      • This popular romanization converter from Pusan National University even outputs incorrect romanizations.[c]
    • By contrast, pinyin for Chinese and revised Hepburn for Japanese have become nearly universally accepted and there are far fewer mistakes in their application.
  • The phonology of Korean, particularly because of its additional vowels and consonants, is not easily expressible using Latin letters.
    • Many systems have used diacritics to represent these other sounds. Notably, the breve (◌̆) is used for MR and is difficult to access on computers and phones. It is thus regularly omitted, which leads to ambiguity and confusion.[5]
    • Other systems have used digraphs. Like this RR example: the "eo" in "Incheon" represents the single Korean vowel ([ʌ]). Some argue these are unintuitive or unsightly.
  • Both MR and RR have ambiguities.
    • For example, hyphenation in MR and in RR are flexible.
    • To fill these gaps and recommend standardized practice, we researched and weighed the following:
      1. Supplementary explanations and essays from relevant people that created the systems
      2. Common romanization practices in academia and public
      3. Wikipedia guidelines and policies

Romanization of Korean on Wikipedia

Since the first version of the MOS in 2004, there has been regular confusion and debate over how to handle all of these issues on Wikipedia. These discussions have often been repetitive and wasteful.

In 2024, WikiProject Korea wrote a complete rewrite of the MOS. This effort and its relevant research and argumentation is documented in this essay.

Basic principles

Our guidelines should abide by Wikipedia's standards, especially the Wikipedia:Manual of Style and Wikipedia:Article titles. Per those guidelines, we prioritize the reflection of current (not past or predicted future) romanization practices used in the majority of recent Wikipedia:Reliable sources, particularly sources that deal specifically with Korea and have significant impact (WP:COMMONNAME, WP:DIVIDEDUSE, WP:CRYSTALBALL).

As such, we try to avoid promoting romanization choices that we think are "better". That is not the job of Wikipedia: we do not lead, we follow. At the same time, we try to minimize how complicated our rules are. Unfortunately, the situation is fundamentally complicated.

Romanization systems in use on Wikipedia

We use the following romanization systems on Wikipedia:

Why not use one romanization system for everything?

While tempting and this would be easier, this would go too far against our § Basic principles.

Why not use other systems?

We try to balance reflecting common practice and reducing complication. The systems we currently recommend are more than sufficient for most cases; asking users to learn more systems adds significant complication without adding much understanding.

Why use MR for pre-1945 topics?

International academic journals almost universally use MR when writing about Korean history.[6][7] Practice in books seems to be more divided but still leaning MR, per § Romanizations used in books.

Why use 1945 as a dividing line for using RR?

Mid/late August 1945 was when the division of Korea occurred.

Other possible lines:

  • 1948 (the establishment of North/South Korea)
    • Arguably less significant than the 1945 division. Little changed between 1947 and 1949, but 1944 to 1946 was a seismic change.
    • Similarly, dividing spellings for terms relating to the United States Army Military Government in Korea (1945–1948) and South Korea (1948–) seems relatively arbitrary. There was relatively clear continuity between both these entities.
  • 2000 (the enactment of RR)
    • Without a doubt, less significant than the division of Korea. Notability is unlikely to change from 1999 to 2001.
    • Some recent writings use MR when talking about post-division South Korea.

Why use RR for South Korea?

RR is now widely used by the international and domestic English-language press for coverage of South Korea. South Korea's popular culture and soft power have boosted the use of the system. Books on contemporary South Korea also often employ the system.[d]

Why use Yale romanization?

The international linguistics community still seems to widely use Yale.[8] Restricting its use would mean asking our editors to convert Yale text in sources to either MR or RR; this is difficult to enforce, leaves room for errors, would be misrepresenting current practice, and adds complication.

How extensively or firmly Yale should be recommended is currently uncertain.

Why not use North Korea's romanization for North Korean articles?

North Korean romanization ("NKR") is used by the NK government and state media. It is also recommended by the AP Stylebook for people names and by NK News for general cases (see § Other style guidelines).

Arguments against using NKR:

  • The international academic community widely uses standard MR when writing on North Korea.[verification needed]
  • AP and NK News aren't consistent in their usage of NKR.
  • It is based on MR,[7] which it is also reasonably similar to.
  • Minimizing the number of systems in use on Wikipedia.
    • This is currently weighted highly.
  • Using standard MR has been the status quo since the first version of the MOS in 2004, and seemingly nobody has disputed it until 2024.

McCune–Reischauer

Why use the 1961 version of MR?

This version appears to be the most widely used.[verification needed] The 1961 paper is effectively a summary of the 1939 version, with minor updates to reflect more recent Korean phonology and spelling. It is missing some details that the original had (as it is a summary). We assume those details still apply; they have not been affected by the development of the Korean language.

How strictly the specifications of MR are followed seems to vary; some authors claim to use the system but romanize in ways that are either incorrect or recommended against in the original 1939 and 1961 papers.

Why not use the ALA-LC (Library of Congress) version?

This version appears to not have widespread adoption in academic works. It's also extremely complicated, with countless instructions for edgecases.

The ALA-LC version heavily focuses on word division in phrases and sentences. While that may be important when romanizing book titles in libraries (and for easier word-based searching in library databases), that is much less important on Wikipedia, where phrases and sentences are usually translated into English (though romanizations can also be given).

In addition, the ALA-LC version has strange rules about two-syllable given names: non-Sino-Korean names have joined syllables, and Sino-Korean names have a hyphen between the two syllables. This is needlessly complicated and not really possible to follow. It is not really possible to determine which names are Sino-Korean and which are not. Even ALA-LC admitted this.[9] The original MR does not do this – it treats given names just like any other words.

Hyphenation

The 1939 paper that introduced MR says the following about hyphenation:

in Korean, a given syllable may vary widely in pronunciation according to the nature of the other syllables in the word [...]. A simple example, the word Silla, will help to clarify the point. In Chinese, hsin 新 plus lo 羅 are pronounced Hsin-lo but in Korea, sin 新 plus na (la) 羅 are pronounced Silla. To hyphenate this name as Sil-la would imply that it is composed of two parts which individually are sil and la, which is obviously misleading.[10]

There are many cases where there is a partial division does not seem great enough to justify writing them as separate words. It is for such cases that we have reserved the use of the hyphen; but we believe that on the whole it should be used as sparingly as possible. [Example: 연산군 → Yŏnsan-gun][11]

The 1961 summary paper on MR says the following about hyphenation:

The hyphen is reserved for subsidiary divisions within words, such as Tŏksu-gung (덕수궁), Haein-sa (해인사).

Reischauer, one of the namesakes of MR, expressed general distaste for the use hyphens for pronunciation-related matters. When the Japanese government introduced a Japanese romanization rule (1937) that employs a hyphen when the moraic n () is followed by a vowel (including y), he wrote the following (excerpt from Rōmaji or Rōmazi (1940)):

Another change for the worse in Kokutei is the substitution of the hyphen for ' between the final n of one syllable and an initial vowel in the next syllable within a single word. The hyphen is best reserved for use in words which should be hyphenated on other than phonetic grounds.

It could be argued that the above is part of the reason why MR uses n'g (not n-g) when n and g are pronounced separately (e.g. 한글 Han'gŭl), despite the apostrophe also being used for strongly aspirated consonants. "Mun'gyŏng-si" is much easier to parse than "Mun-gyŏng-si"; the hyphen is more suitable for semantic division.

Spacing

In MR, there are mandatory and optional spaces.

Mandatory spaces are just those between the family names and given names of people.[12]

Optional spaces are more subjective. The 1939 paper that introduced MR says the following:

In Romanizing sentences, book titles and the like, the problem of a correct division into words is important. It is difficult to define what is a word in any language, and the problem is particularly complicated in Korean where divisions have been traditionally made by syllables and by clauses. Therefore in Romanizing groups of words a division into units roughly comparable to those in European sentences should be made if the Romanization is to be intelligible to the average Occidental.

One can not lay down hard and fast rules for word divisions, and much depends on the special considerations and needs of each individual problem of Romanization.[13]

The paper then gives some recommendations on space insertion:[14]

  • For native Korean terms, no space between verb stems and verb endings (e.g. 자다 ("to sleep") → chada and not cha ta)
  • For native Korean terms, no space between nouns and postpositions (e.g. 꽃이 ("flower" + subject postposition) → kkoch'i and not kkot i)
  • For other remaining native Korean terms (e.g. adjectives, adverbs, etc), attempt to follow spacing practices of English.
  • For Sino-Korean words, recommendations are difficult; rely on experience, typical groupings of characters, and to maximize understanding to readers.

They provide this example:[15]

한글 운동은 연산군 조에 이르러 큰 액운을 당하였다.
Han'gŭl undongŭn Yŏnsan-gun choë irŭrŏ k'ŭn aegunŭl tanghayŏtta.
(The Han'gŭl movement was placed in an extremely critical position during the reign of the ruler Yŏnsan.)

Common MR mistakes

  • should be romanized si (not shi), per the original MR. sh only appears when romanizing (shwi).[16]
  • Syllable-final + syllable-initial is rh (not lh).
  • The apostrophe only appears in ch', k', p', t', and n'g. It does not appear elsewhere.
    • When n and g are pronounced separately, an apostrophe is added between them (i.e. n'g); ng is not followed by an apostrophe.
More information Hangul, Correct ...
HangulCorrectIncorrect
신라SillaShilla
쉽다shwiptaswipta
발해ParhaePalhae
연구yŏn'guyŏngu
영어yŏngŏyŏng'ŏ
Close

Revised Romanization of Korean

Hyphenation

In RR, hyphens can be either optional or mandatory.

  • Optional hyphens are used in two scenarios:
    1. Disambiguating pronunciation (e.g. 해운대 Hae-undae)
    2. Between syllables of a given name (e.g. 홍길동 Hong Gil-dong)
  • Mandatory hyphens are for separating an administrative unit (e.g. 평창군 Pyeongchang-gun)

In general, we recommend against the use of hyphens for disambiguating pronunciation. This seems to align with the explanations from the National Institute of Korean Language.[5][17][18]

Also, mixed use of hyphens can be confusing. For example, in Hae-undae-gu, the first hyphen is for disambiguation in pronunciation, but the second one is for separating an administrative unit. Consistently excluding optional hyphens (i.e. Haeundae-gu) makes names more immediately recognizable.

Note that hyphenation in the names of geographic features, cultural properties, and man-made structures is prohibited.[19]

For hyphenation in people names, see § RR names.

Spacing

RR requires a space between family and given names. It does not officially comment on optional spaces.

Letter-by-letter transliteration

When reversibility is desired (namely in academic articles), RR officially allows for a letter-by-letter transcription. For example, 독립 would be rendered as "doglib" in the letter-by-letter transcription, whereas by its normal pronunciation spelling it'd be "dongnip".[19]

In general, we discourage the use of such transcriptions. Arguments against using it:

  • They are an alternate form of RR and less commonly used (thus making them less useful and recognizable to the majority of people).
  • In any situation where they may have some benefit, the original Hangul could be added instead. Hangul is more recognizable than letter-by-letter RR.
  • While it is tempting to try and advocate for our consistent use of this system because of its reversibility with Hangul and ease of use for people who know Hangul, remember our § Basic principles.

Romanization of people names

Why have these steps for WP:KOREANNAME?

Over the past 20 years on Wikipedia, there has been constant costly debate and confusion over how to weigh WP:COMMONNAME, personal preference of the subject, and systematic romanization for Korean names. These debates have often reached differing conclusions, and have created a confusing mess of inconsistent practice. We established these steps to hopefully reduce these debates and improve WP:TITLECON.

Note that this process was designed to consider all five WP:CRITERIA for titles:

  • Recognizability – accounted for in all three steps. In the third step, we even chose to use a common modification of RR (hyphens in given names) to improve recognizability. WP:KOREANNAME is designed to match most common practice for various common subject matters and time periods.
  • Naturalness – accounted for in all three steps. Same explanation for above.
  • Precision – self-explanatory
  • Concision – self-explanatory
  • Consistency – accounted for mostly in the third step. First two steps yield exceptions, the third step defaults to a safe consistent practice.

Why ask for "widely used" WP:COMMONNAMEs in step 1?

Multiple reasons.

  1. For cases when there are extremely few attestations in English, there are so many conflicting romanization practices that taking a small sample will likely yield inconsistent romanization (including possibly ad-hoc romanization), which hurts WP:TITLECON and potentially WP:RECOGNIZABILITY. We'd rather people turn to a default spelling to avoid those downsides.
  2. When there is significantly divided use, while we'd love for if people really researched each concept to determine which names are 51% vs 49% more common, this is costly and people rarely want to engage in such research. So we give them an easy out by turning to a default practice.

MR names

The 1939 MR paper says this about people names:[12]

In both two character surnames and two character given names the general rules of euphonic changes should be observed, and the two syllables should be written together... [For assimilating between surnames and given names,] disregard euphonic changes between surnames and given names or titles... [For the surname ], it is pronounced in the standard dialect and should be Romanized I, but some may prefer to retain the older Romanization, Yi, because that is already the familiar form.

We recommend following the above guidance; it also appears to be commonly followed in academia. Also, "Yi" is more likely to be the WP:COMMONNAME spelling, and is also arguably more readable than "I".

For hyphenation in names, we currently do not recommend in WP:KOREANNAME that hyphens be inserted. This is subject to change; it is not yet clear to us whether hyphenation or non-hyphenation of MR names is more dominant (some research documented in #Romanizations used in books).

RR names

Assimilated sound changes are not reflected in given names.[19]

For given names, hyphens are officially discouraged by the National Institute of Korean Language[19] and the Ministry of Culture, Sports and Tourism.[20] See also Revised Romanization of Korean § Hyphenation. However, English-language press in both South Korea and abroad appear to widely use them. Per our § Basic principles, we choose to hyphenate.[e]

On the official RR documentation, it says "Transcriptions of family names will be established additionally.", implying that they are planning to eventually establish additional guidelines on how to romanize family names. However, even into 2026, this hasn't come to fruition.[19] Since it has been already 25 years, this may actually never happen.

Common English spellings for South Korean surnames

For South Korean surnames in English-language text, if there's evidence of a widespread common spelling we recommend the use of that spelling.

We choose to do this instead of the alternative: defaulting to standard RR spellings if common name or personal preference are not known. Defaulting to RR may have some benefit in recognizability and consistency. However:

  • For the surnames where almost all people use a non-RR spelling (e.g. Park for ; Bak), we'd be wrong almost all of the time.
    • Per naturalness, people expect to see these spellings for those names, even if they're ad hoc.
  • Few people seem to actually know how RR works in detail, meaning recognizability may be weak.

How widespread a surname spelling should be before we recommend it is not certain. We also only included the top N most common surnames in order to not make the table overly lengthy. Initial commonality threshold is 80%; no prejudice against lowering it or increasing N.

Surname spelling statistics

Note: if bolded, passes the 80% threshold and thus we recommend it. Many of the surnames that pass the threshold are already standard per RR; thus we don't go out of our way to recommend a modified spelling.

More information Surname (Hangul), Spelling 1 ...
2011 passport statistics, ordered by most common in 2015[21][f]
Surname
(Hangul)
Spelling 1Spelling 2Spelling 3
Kim[g]
Lee[g]
Park[g]
Jung (41.13%)Jeong (32.17%)Chung (15.38%)
Choi (88.51%)Choe (10.20%)Choy (0.24%)
Cho (69.85%)Jo (27.95%)Joe (0.89%)
Kang (95.93%)Gang (3.39%)Khang (0.17%)
Jang (74.76%)Chang (24.46%)Jhang (0.15%)
Yoon (48.66%)Yun (36.83%)Youn (13.75%)
Lim (61.84%)Im (26.44%)Yim (6.21%)
Shin (86.71%)Sin (12.43%)Sheen (0.18%)
Yoo (38.15%)Yu (28.12%)You (18.44%)
Han (98.53%)Hahn (1.34%)Hann (0.05%)
Oh (97.08%)O (2.14%)Ou (0.18%)
Seo (77.16%)Suh (16.97%)Su (1.19%)
Jeon (54.48%)Jun (25.01%)Chun (10.42%)
Kwon (74.82%)Gwon (9.30%)Kweon (7.45%)
Hwang (95.34%)Whang (2.80%)Hoang (0.69%)
An (57.77%)Ahn (39.89%)Ann (1.90%)
Song (99.28%)Soung (0.39%)Shong (0.12%)
Hong (99.53%)Houng (0.35%)Heung (0.02%)
Yang (99.06%)Ryang (0.25%)Yaung (0.22%)
Ko (59.75%)Go (18.00%)Koh (17.30%)
Moon (70.28%)Mun (29.21%)Mon (0.19%)
Son (83.93%)Sohn (9.47%)Shon (5.82%)
[h]Woo (97.58%)Wu (0.97%)U (0.31%)
Close
More information Surname (Hangul), Spelling 1 ...
2007 examination of 63,000 passports[22]
Surname
(Hangul)
Spelling 1Spelling 2Spelling 3
Kim (99.3%)Gim (0.6%)Ghim (0.01%)
Lee (98.5%)Yi (1%)Rhee (0.2%)
Park (95.9%)Bak (1.8%)Pak (1.7%)
Choi (93.1%)Choe (6.5%)Choy (0.09%)
Jung (48.6%)Jeong (37%)Chung (9.2%)
Close

This 2015 news article says that, for , a passport examination had 62.22% of people using "Jung" and 28.25% using "Jeong".[23]

North Korean romanization

At present, we do not use North Korean romanization on Wikipedia except for cases of WP:COMMONNAME. We considered applying the rules of North Korean romanization for names to MR, but it was argued that doing so was too arbitrary and inconsistent.

Regardless, below is what North Korean romanization recommends for people names. We document this here for ease of access.

Spaces are given between the first and second names of a person and the first sounds of the names are written in capital letters and in the names of Chinese character origin, spaces are given between each letter. When the first sound of the second syllable becomes vocal, it is transcribed in a relevant voiceless letter.

e.g.

  • 김꽃분이 Kim KKotpuni
  • 박동구 Pak Tong Gu
  • 안복철 An Pok Chŏl[24]

Romanization of titles of works

Per MOS:NONENGTITLE, how titles are capitalized depends on the language. Neither RR nor MR specify how to handle capitalization for titles of works. For works with Korean titles, it is widely recommended to use sentence case when romanizing. This is the common practice from The Chicago Manual of Style,[7] which itself is widely used by Korean studies journals (see § List of style guidelines for Korean studies journals). For which romanization to use, we break with the practice of journals (which widely use MR) and recommend the use of whichever romanization system is appropriate for the main topic of the article.

Other names

Partial tautological names

One point of uncertainty is whether to use terms like "Gyeongbokgung Palace" ("gung" means "palace") or "Bulguksa Temple" ("sa" means "temple"). Beginning on January 1, 2013, the South Korean government body Cultural Heritage Administration began officially preferring that style.[25] The Seoul Metropolitan Government also shares this preference. However, this practice has varying levels of adoption elsewhere and in various newspapers. For example, the Korea JoongAng Daily has explicitly rejected it.[26]

In general, our naming conventions currently discourage the practice. Various Wikipedians have expressed distaste for it, as it seems repetitive if one speaks Korean and English. However, it has also been pointed out that such repetitions are not "incorrect" in linguistics, and are actually quite common elsewhere in the world.

Context parameter in Korean templates

This is an explanation of why the |context= parameter was removed from {{Infobox Korean name/auto}} and {{Korean/auto}}.

People have fiercely argued we should use various spellings of both "Hangul" and "Hanja". Some have even argued that different spellings should be used in different contexts. These debates have often reached differing conclusions, with various people dissatisfied each time.

Rather than ourselves participate in that debate, instead we will only use the spellings used by the titles of the respective articles ("Hangul" and "Hanja"). This decision is based on WP:COMMONNAME and WP:KO-CONSISTENT. If those articles ever change titles, we will follow the change.

Spellings for especially "Hangul" are not straightforward. "Hangul" is neither preferred by North Korea (which uses "Chosŏn'gŭl") nor by South Korea ("Hangeul"). Furthermore, the script went by a variety of inconsistent names even into the mid-20th century. The spelling "Hangul" is a word in the English language[27] and the spelling/name used by default by the International Organization for Standardization.[28]

"Hanja" is the preferred spelling of South Korea, but not of North Korea, which prefers "Hancha".

If we did decide to use various spellings for Hangul/Hanja depending on the article, what spellings should be used for articles like Korean Demilitarized Zone (relevant to North and South Korea) or Sejong the Great (no single clear name for the script during his lifetime, perhaps "Hunminjeongeum" or "Hunminjŏngŭm")?

Should our templates reflect all these nuances and have options to display all these various names for scripts? Would the tens of thousands of uses of these templates need to be verified to confirm they're using the exact terminology preferred by specific groups at specific times? Seems like too much work, debate, and minute editing over too little gain to readers.

In short, our decision avoids time-consuming busywork and need to relitigate old debates. We simply leave the debates to editors of the articles Hangul and Hanja, and always use whichever spellings they decide on.

Notes

  1. • For example, to correctly convert 독립문 into "Dongnimmun" (RR) or "Tongnimmun" (MR), prior practice converting an orthographic Hangul spelling into a phonetic Hangul form (독립문 → [동님문]) is required. Without this kind of training, people are tempted to romanize the term incorrectly as "Dokripmun" or "Tokripmun".
    • MR also reflects voicing distinction, which is not a phonemic difference in Korean. For example, 제주 is "Cheju" in MR. It is very difficult for ordinary Korean speakers to understand this, as they do not sense the voicing difference.
  2. • For example, in the "personal name" function, the full name 남궁은비 (surname 남궁, given name 은비) is "Namgung Ŭnbi" in MR, but this converter incorrectly gives "Namkung Ŭnpi" (archive).
    • As another example, in the "proper nouns" function, 국립 과학 수사 연구원 is "Gungnip gwahak susa yeonguwon" in RR and "Kungnip kwahak susa yŏn'guwŏn" in MR, but this converter incorrectly gives "Gungnim gwahang susa yeonguwon" and "Kungnim kwahang susa yŏn'guwŏn" respectively (archive).
  3. Some recent authors even employ RR when writing on North Korea, although it appears unlikely this is a dominant practice.
  4. It is possible that "inserting a hyphen between syllables of a given name is allowed" in RR is actually for journalists. Journalists have been inserting hyphens to Korean given names before RR (as found in AP Stylebooks published in the 1990s) and they probably did not want to change what they had been doing when RR was being formulated, so they probably demanded that inserting hyphens to given names be allowed. After all, there is not a real reason to insert hyphens only to given names when syllables in other words (place names, common nouns, etc.) are simply joined without hyphens.
  5. Ordered by most common surnames as per List of Korean surnames.
  6. Stats not gathered, as they assumed it was a nearly universal spelling.
  7. Including this, even if not top most common, because otherwise the default RR reading is one letter and difficult to read.

References

Appendix

Related Articles

Wikiwand AI