Transliteration is the process of converting the sounds of a word or name from one writing system into another, keeping pronunciation close to the source rather than translating its meaning. It appears in translation and localization style guides, terminology databases, and language-specific briefs as a rule for proper nouns, personal names, place names, and brand names where consistent sound representation is more important than semantic equivalence.
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
In translation and localization workflows, transliteration rules commonly appear in client style guides, termbases, language-variant instructions, and query sheets. Translators apply them when rendering actor names in subtitles, user names in legal or financial documents, or product names in UI strings, especially when target scripts such as Cyrillic, Arabic, or CJK require a consistent sound-based spelling.
A frequent error is mixing transliteration with translation or with a previously established local name, producing inconsistent spellings across a product or campaign. This matters because users may fail to recognize the same person or brand, search and voice commands break, and reviewers or clients reject deliverables for violating a termbase or style guide.
Creative and consumer content needs accurate meaning as well as tone and context. Subtitles, interfaces and voice scripts also require checks for timing, character limits and pronunciation.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Employee-training video transcription and dubbing.
Read the published project →Brand documentation.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Content Globalization solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.