To handle names in translation, first identify the kind of name, its established usage and the preference of the person or organization it refers to. Names are not all treated alike: a personal name, a place, an institution, a product and a fictional character can follow different conventions. Transliteration, translation and retaining the original spelling are distinct choices.
Identify the name’s role
Ask whether the name identifies a person, place, organization, product or fictional entity. Check whether the target audience already uses an established form. For example, an institution may have an official translated name, while a small company may ask that its registered name remain unchanged.
Context matters. A phrase that looks like a name can also describe a role or feature. In an invented app, “Morning Light” might be a product name, a heading or a literal description of a color setting. Decide what it is before deciding whether to translate it.
Distinguish translation from transliteration
Translation carries meaning into another language. Transliteration represents a name’s sounds or letters using another writing system, with conventions that may not preserve pronunciation perfectly. Transcription can refer more broadly to representing spoken sounds in writing. Keeping the original spelling is another option when the script and context support it.
For an invented name such as “Mira Vale,” a publication might retain the spelling in a Latin-script context, use an established form if one exists, or render it in another script according to relevant conventions and the person’s preference. Do not assume that one spelling can be reverse-engineered perfectly into every writing system.
Ask about personal preference
For personal names, use the form the person uses when that information is available and appropriate. Do not silently reorder, shorten, translate or “correct” a name because it seems unfamiliar. Name order and family-name conventions vary, and databases designed around a single first-name/last-name pattern can impose assumptions.
The W3C includes handling of personal names and forms of address among locale-related preferences that internationalized systems may need to support [1]. That is a design concern as well as an editorial one: forms should allow the name structure required by the people using them, instead of forcing every entry into one template.
Keep names consistent without flattening them
Create a short project note for recurring names: preferred spelling, whether to translate or retain, capitalization, diacritics, script rendering and any established alternatives. Record the source of the decision and revisit it if the person or organization updates its preferred form. Consistency means following the documented choice, not making every name obey one universal rule.
For an invented newsletter, suppose the editor prefers “Mira Vale” in Latin script, while a translated profile also needs a local-script rendering. The team can retain the preferred spelling in a byline and use a reviewed rendering in body text where readers need it. Note the distinction so later pages do not invent competing forms.
Handle fictional and branded names carefully
A fictional name may carry a meaning, joke or sound pattern that matters to the story. Translating it can help readers perceive that function, while retaining it may preserve identity or continuity. Discuss the author’s intent and the audience’s reading context; there is no universal answer. For brands, check official naming guidance rather than assuming the name is translatable.
A useful next step is to build a name list for one project. For each entry, record its type, preferred form, target-language treatment, pronunciation or script note where relevant, and the person responsible for confirming it. Review the list before publication and check names in page layouts, forms and captions.
