Translate or Transliterate Names and Place Names? A Practical Decision Guide

Do not apply one universal rule to names. First identify the entity, target audience, script, genre, and authoritative target-language usage. Then choose deliberately among retaining the original form, transliterating its script, using an established target-language name, translating its meaning, or showing two forms on first mention.

Transliteration is not translation. It changes script while aiming to represent the source form; translation changes linguistic content. Microsoft makes that distinction in its globalization glossary. For geographical names, the United Nations Group of Experts on Geographical Names (UNGEGN) also treats standardization and romanization as systems, not improvised spellings.

Start by identifying the entity, not the string

The same written form can refer to different things, and different forms can refer to the same entity. Before changing a name, record:

• entity type: person, place, organization, title, product, fictional character, or invented location;
• source-language and source-script form;
• target language, target locale, and target script;
• established target-language or official form, if one exists;
• who uses the name and in what context;
• whether the name's literal meaning matters; and
• whether readers need to search, cite, pronounce, or navigate with it.

UNGEGN's data guidance distinguishes the named place from its names and spellings. It uses Athens as an example: the Greek endonym Athína and English exonym Athens are different names for the same place, while the Greek-script form and its standardized romanization are different spellings of one name. That distinction prevents “translate or transliterate?” from becoming a false two-option question. See the UNGEGN geographical-name data model.

Choose among five treatments

1. Retain the original form

Keep the source spelling when the target script can display it, the form itself is authoritative or important, and the audience can use it.

Typical cases include brand names without an official localized form, bibliographic evidence, usernames, codes, and a source-script name shown for scholarly identification.

Retention does not guarantee usability. A target reader may be unable to pronounce, type, or search the form, so consider a transliteration on first mention.

2. Transliterate into the target script

Represent the name in another script according to an established system or accepted convention. For example, a Cyrillic, Arabic, or Greek name may need a Latin-script form for an English edition.

Do not transliterate by ear without checking the relevant authority. UNGEGN says a romanization system should be scientifically based, implemented by the proposing country, and sufficiently reversible before adoption as a UN standard. Its romanization systems directory lists recommended systems by language or script.

Transliteration still requires editorial decisions about hyphens, spacing, diacritics, name order, and established exceptions.

3. Use the established target-language name

Some people, places, institutions, historical figures, and works already have a conventional target-language form. English readers expect Athens, not a fresh transliteration chosen for one manuscript.

Prefer an authoritative current source appropriate to the entity:

• national naming authority or official gazetteer for places;
• the person's own target-language publication or official profile for personal names;
• the organization's official target-language site for institutions;
• library catalogues, publishers, or cited editions for works; and
• relevant domain style guides for historical or scientific names.

Popularity in a web search is evidence to investigate, not authority by itself.

4. Translate the meaning

Translate a name when its semantic content performs a function the target reader needs and the genre permits it. This can apply to descriptive institutions, fictional place names, nicknames, titles, allegorical characters, and names that carry a plot clue or joke.

Before translating, ask:

• Is this a proper name or an ordinary description that became name-like?
• Does the meaning matter to characterization, world-building, humor, or navigation?
• Would translation make the entity sound generic or change its cultural setting?
• Is an official translated name already in use?
• Will later wordplay still work?

A fictional “North Gate” may need a translated form if its direction and symbolism matter. A real business named North Gate may require its registered name unchanged.

5. Show two forms

Use source plus target, or target plus transliteration, when the reader needs both immediate readability and reliable identification.

Common patterns include:

• established English name followed by the local form on first mention;
• transliteration followed by source script in parentheses;
• translated institutional name followed by the official original; and
• native-script name in a glossary, index, map, or authority list rather than every occurrence.

Do not repeat both forms so often that the prose becomes mechanical. Define the first-mention rule and the short form for later uses.

Use a source hierarchy for real names

Build evidence before selecting a spelling.

Record the source URL or edition, retrieval date, selected form, rejected forms, and owner. If authorities disagree, preserve the disagreement and apply the project's declared policy instead of pretending one form is universally correct.

Separate script conversion from name adaptation

Use this decision sequence:

1. Resolve identity. Confirm which entity the source refers to.
2. Find authoritative forms. Search current official and target-language sources.
3. Check for an established target exonym or translated name. Use it when it fits the edition's audience and policy.
4. If no established form exists, select a recognized transliteration system. Do not mix systems inside one work.
5. Ask whether the name's meaning performs a literary or practical function. If yes, consider translation, a dual form, or an explanatory note.
6. Test the complete context. Check grammar, inflection, sorting, searchability, maps, citations, links, and later callbacks.
7. Record and enforce the decision. Add variants to the QA search list.

This sequence avoids a frequent error: translating a meaningful-looking proper name before confirming that it is a real entity with an established form.

Change the method by genre

Fiction

Track character names, aliases, titles, forms of address, invented places, meaningful names, and pronunciation. Preserve deliberate opacity: not every name whose etymology can be explained should be translated for the reader.

If a name powers a pun or later reveal, connect the decision to the humor register. The humor and wordplay workflow provides the mechanism test.

Academic and historical writing

Optimize for identification and citation. Preserve source-script forms where they help verification, follow the relevant disciplinary style, and match titles to the editions actually cited. A new translation of a quotation does not silently rename the cited work.

The research-paper translation guide adds citation, equation, figure, and terminology controls.

General nonfiction and manuals

Prioritize consistent recognition and user action. A place in an address, a manufacturer's legal name, and a descriptive department name can require three different treatments in one paragraph.

Maps, indexes, and metadata

Treat sorting and discovery as acceptance criteria. Test diacritics, alternate names, cross-references, search strings, and whether maps and body text point to the same entity.

Build a name authority record

Use one row per entity, not one row per spelling.

The book terminology consistency workflow explains how to search approved and rejected forms across a complete manuscript.

Do not strip diacritics or collapse variants silently

UNGEGN's model says original and correct spellings should be retained without removing or transforming diacritical characters. A project may also need an ASCII fallback for a legacy system, URL, or search index, but that is a separate technical representation—not evidence that the displayed name should lose its marks.

Likewise, do not assume two spellings are errors. They may be:

• original script and romanization;
• endonym and exonym;
• full and short forms;
• historical and current names;
• two language forms in a multilingual region; or
• intentional aliases in a narrative.

Classify the relationship before deduplicating it.

Full-book QA for names and places

Before release:

1. Search every approved form and rejected variant.
2. Check zero-count approved forms against the source for omissions or unexpected paraphrases.
3. Compare first mention with later short forms.
4. Review chapter boundaries where different translators or model runs meet.
5. Check maps, captions, tables, footnotes, bibliography, index, metadata, and cover copy.
6. Test target-script fonts and directionality in the exported file.
7. Verify that links, addresses, and citations still identify the intended entity.
8. Rerun the search after final layout or EPUB conversion.

For Arabic, Hebrew, and mixed-direction files, add the RTL book checks because correct spelling can still render in the wrong visual order.

Release checklist

Confirm that:

• each consequential string is attached to a resolved entity;
• the target language, locale, and script are specified;
• authoritative existing target forms were checked;
• transliteration follows a named system or explicit project convention;
• meaningful fictional names were evaluated for narrative function;
• source-script, dual-form, first-mention, and short-form rules are explicit;
• diacritics, name order, spacing, hyphens, and inflections are controlled;
• maps, indexes, metadata, citations, and links use compatible forms;
• rejected variants were searched in the final export; and
• unresolved naming disputes remain visible to the editor.

BookTranslator's Auto glossary can help keep names, places, and key terms consistent across eligible non-PDF book and document translations. Keep the external name authority record anyway: it stores the authoritative source, transliteration system, rejected variants, and editorial reasoning that an automatic glossary cannot infer safely.