A do-not-translate list is a project-specific reference that identifies terms and strings which must remain in their original form, including brand names, legal entity names, code identifiers, trademarked product names, and some UI element IDs. It is usually delivered as part of the localization kit or style guide so that translators and reviewers consistently leave these items untouched in every file, screen, and campaign asset.
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.
Translators encounter this list when preparing files in CAT tools, especially for software strings, marketing copy, legal content, or product documentation. The list is often enforced through a termbase, a QA check, or a locked glossary that flags any translated instance of a protected term so it can be reverted before delivery.
A frequent mistake is assuming that partial translation is allowed, such as translating a product name's generic noun while keeping the brand portion; this can break trademark usage and create legal exposure. Another issue is forgetting to apply the list to screenshots or metadata, where a protected term may be overlooked because it does not appear as a standard segment.
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.