The Complete Guide to Romanizing Names for English Usage

This comprehensive guide explains the principles and practices of romanizing personal names from various languages into English. It covers name order, official systems, passport considerations, and common variants, providing essential knowledge for linguists, travelers, and data specialists.

Short Answer

This comprehensive guide explains the principles and practices of romanizing personal names from various languages into English. It covers name order, official systems, passport considerations, and common variants, providing essential knowledge for linguists, travelers, and data specialists.

Native Name Order

In many cultures, the order of given name and family name differs from the English convention. For example, in East Asian languages such as Chinese, Japanese, and Korean, the family name precedes the given name (e.g., Kim Jong-un where Kim is the family name). In Western contexts, the given name typically comes first. When romanizing names for English usage, it is crucial to preserve the native order unless a specific context (e.g., a passport or database) requires inversion. The UNGEGN (United Nations Group of Experts on Geographical Names) recommends retaining the original name order in romanized forms to avoid confusion.

Official or Common System

There is no single official romanization system for all languages. Instead, various standards exist depending on the source language and the target audience. For example:

  • Hanyu Pinyin for Mandarin Chinese (ISO 7098)
  • Revised Romanization of Korean (South Korean official system)
  • Hepburn for Japanese (de facto standard)
  • BGN/PCGN for many languages (used by U.S. and U.K. mapping agencies)
  • ISO 9 for Cyrillic scripts

For English names themselves, romanization is not needed, but when English names appear in non-Latin scripts (e.g., on foreign documents), the reverse process (transcription into the local script) follows local conventions. This guide focuses on converting non-English names into Latin script for English-language contexts.

Family Name Placement

In English-language documents, the family name is often placed last (e.g., John Smith). However, when romanizing names from cultures where the family name comes first, it is common to either keep the native order or invert it for English readability. Official passports from many countries now follow the ICAO standard, which places the family name in a separate field or uses all caps for the surname. For example, a Chinese name Wang Xiaoming may appear as Xiaoming Wang in an English context, but the passport will show WANG Xiaoming. Consistency is key: always check the target document’s requirements.

Spacing and Hyphens

Spacing and hyphenation in romanized names can vary widely. Some languages, like Vietnamese, use spaces between syllables (e.g., Nguyễn Văn A). Others, like Japanese, may use no spaces in the original script but insert spaces in romanization for clarity (e.g., Tanaka Taro). Hyphens are sometimes used to link compound given names (e.g., Jean-Pierre) or to indicate syllable boundaries in transliteration (e.g., Chou En-lai). The ALA-LC romanization tables provide specific rules for hyphenation. In general, follow the conventions of the source language’s official romanization system.

Passport Considerations

Passport authorities have strict rules for romanizing names to ensure machine readability and international consistency. The ICAO 9303 standard mandates that names be written in Latin capital letters without diacritics (e.g., Müller becomes MUELLER). Many countries allow only the 26 basic letters of the English alphabet, forcing the omission of accents and special characters. This can lead to multiple acceptable variants (e.g., José becomes JOSE). When applying for a passport, the name must match the birth certificate or other official documents. For dual citizens, the romanization used in the issuing country’s passport may differ from the native script.

Common Variants

Due to different romanization systems and personal preferences, many names have multiple accepted romanized forms. For example:

  • Arabic: Muhammad can also be Mohammed, Mohamed, Muhammed.
  • Russian: Yeltsin vs. Eltsin (BGN/PCGN vs. ISO 9).
  • Chinese: Beijing (Pinyin) vs. Peking (Wade-Giles).
  • Korean: Park vs. Bak (Revised vs. McCune-Reischauer).

These variants can cause confusion in databases and search engines. It is advisable to use the most widely accepted system for the target audience, or to include multiple variants as aliases.

Historical Spellings

Historical romanizations often reflect older systems or colonial influences. For instance, Canton (now Guangzhou) and Peking (now Beijing) are remnants of earlier romanizations. In personal names, historical spellings may be retained by families for generations (e.g., Lee instead of Li for Chinese surnames). Understanding these historical layers is important for genealogical research and for matching records across time periods. The Library of Congress and BGN/PCGN provide historical tables that document changes.

Examples

Native Script Romanized Form
王小明 (Chinese) Wang Xiaoming
김영희 (Korean) Kim Yeonghui
田中太郎 (Japanese) Tanaka Taro
محمد (Arabic) Muhammad
Иван Петров (Russian) Ivan Petrov

Variations for the above examples:

  • Wang Xiaoming can also be romanized as Wang Hsiao-ming (Wade-Giles) or Wang Siaoming (Gwoyeu Romatzyh).
  • Kim Yeonghui may appear as Kim Young-hee (McCune-Reischauer) or Gim Yeonghui (Revised Romanization).
  • Tanaka Taro is sometimes written as Tanaka Tarō with macron, or Tanaka Taro without.
  • Muhammad has dozens of variants: Mohammed, Mohamed, Muhammed, etc.
  • Ivan Petrov may be transliterated as Ivan Petrov (BGN/PCGN) or Ivan Petrov (ISO 9, same for this name).

What the Converter Cannot Determine

Automated romanization converters have limitations. They cannot:

  • Distinguish between homographs (e.g., the Chinese surname 李 Li vs. the given name 丽 Li).
  • Choose the correct system for a given context (e.g., Pinyin vs. Wade-Giles).
  • Handle names that are not in the converter’s language database (e.g., mixed-language names).
  • Apply cultural name order rules (e.g., when to invert family and given names).
  • Account for personal preferences or legal spellings that deviate from standard systems.

Therefore, human oversight is essential, especially for official documents like passports, visas, and academic records.

FAQ

Why are there so many different romanizations for the same name?

Different romanization systems were developed for different purposes (e.g., linguistic accuracy, ease of pronunciation, political reasons). Historical systems like Wade-Giles for Chinese have been replaced by Pinyin, but older spellings persist in personal names and place names. Additionally, personal preferences and regional variations contribute to multiple forms.

Should I use the native name order or invert it for English documents?

It depends on the context. For formal documents like passports, follow the issuing country's rules (often family name last in English contexts). For academic or informal use, you may keep the native order to respect cultural norms. Always check the specific guidelines of the institution or database you are using.

How do I handle diacritics (accents) when romanizing for a passport?

Most passports require names in Latin capital letters without diacritics. Accents are typically replaced by the base letter (e.g., é becomes E) or by adding an 'e' (e.g., ü becomes UE). Check the passport authority's specific rules, as some allow diacritics if the issuing country's alphabet supports them.

Further reading

References

  1. United Nations Group of Experts on Geographical Names (UNGEGN). 'Romanization Systems and Policies.'
  2. International Civil Aviation Organization (ICAO). 'Doc 9303, Machine Readable Travel Documents.'
  3. Library of Congress. 'ALA-LC Romanization Tables.'
  4. BGN/PCGN. 'Romanization Systems for Geographic Names.'
  5. ISO 9:1995. 'Information and documentation — Transliteration of Cyrillic characters into Latin characters.'

Leave a Reply

Your email address will not be published. Required fields are marked *