Translate Like a Pro | Build a Do-Not-Translate List

Professional translation includes knowing what not to translate. Product names, trademarks, legal entity names, standards references, identifiers, SKUs, URLs, code, placeholders, command names and approved global terminology may need to remain unchanged even when every sentence around them is localized. A translator who changes protected content can create a more serious error than a translator who leaves ordinary prose imperfect.

Searches for do not translate list, non-translatable terms, what should not be translated, translation exclusion list, protected terms localization, do not translate brand names, translate attribute, XLIFF translate no and localization protected strings all point to the same operational requirement: translatability should be specified, not improvised.

This guide shows how to build a do-not-translate system that is precise enough for translators and safe enough for software. It separates global protections from locale-specific exceptions, distinguishes identity from ordinary meaning, explains how to protect variables and code, covers trademark and institutional naming, and shows how to test protected content after extraction, translation and reconstruction.

This article is part of eduKateSG’s Master Art of Translation architecture. It extends the professional workflow layer rather than replacing the broader owners for meaning, terminology, quality or language learning.

Quick route through the problem

Classify: determine why an item might be non-translatable.
Scope: decide whether protection is global, language-specific or locale-specific.
Represent: mark protected content in source systems or exchange formats where possible.
Explain: provide context so translators can integrate the protected item naturally.
Test: verify that extraction, tools and reconstruction actually preserve the item.
Govern: review protected status when branding, law, products or locales change.

A do-not-translate list is not a miscellaneous glossary of words that somebody prefers in English. It is a governed set of content whose identity, function, interoperability or legal status would be damaged by ordinary translation. Strong systems also record the reason for protection, the locales to which the rule applies, allowed grammatical treatment around the protected token and the authority that approved the rule.

1. Define non-translatable by reason

The strongest do-not-translate rules explain why the content is protected. Different reasons create different handling: machine identity, legal identity, brand identity, industry convention, code syntax and temporary project policy are not the same.

Professional method. Add a reason field to each protected entry and link to the authority or system requirement when possible. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. A flat list invites overprotection because nobody knows whether an item is truly immutable or merely preferred. A database key is protected because the system requires exact identity; a brand slogan may be protected only in markets where the global campaign mandates it.

Verification. Ask whether changing the string would alter identity, function, legal reference or approved brand policy. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

2. Separate brand names from descriptive product language

A product can contain a protected name inside a sentence that should otherwise be translated naturally. Brand identity is not an excuse to freeze surrounding grammar.

Professional method. Protect the brand token and give translators examples of how it inflects or combines with local grammar, articles and punctuation. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. Teams either translate the brand accidentally or leave entire product phrases in the source language. The product name may stay unchanged while category words, feature descriptions and instructions are localized.

Verification. Read the full target phrase as a native expression while confirming the protected token is byte-for-byte or policy-correct. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

3. Research official names before protecting them

Institutional and legal names may already have authoritative target-language forms. Protecting the source-language form blindly can be as wrong as inventing a new translation.

Professional method. Check official websites, legislation, registries or organisation publications for established forms and record the authoritative target name when one exists. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. A do-not-translate list can fossilise an unofficial name because the team never researched it. A university or ministry may publish an official English name that differs from a literal translation of its local-language title.

Verification. Store the source of the approved name and review it when institutions rebrand or merge. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

4. Protect identifiers as data, not language

SKUs, model numbers, error codes, account IDs and reference numbers usually belong to a data system. Their internal characters may have no linguistic meaning even when they resemble words.

Professional method. Tag or lock identifiers during extraction and present them as variables or protected spans when possible. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. Spellcheck, case normalization or well-meaning translators can silently alter a valid identifier. ERR-1042 should remain ERR-1042 even if the surrounding error message is completely rewritten in the target language.

Verification. Compare identifiers automatically between source and target outputs. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

5. Protect variables and placeholders

Placeholders are interfaces between language and software. Changing braces, names, order requirements or format specifiers can break runtime substitution.

Professional method. Use named variables, provide examples of inserted values and configure localization tools to protect placeholder syntax. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. Translators may translate a variable name or delete punctuation required by the parser. {account_name} remains unchanged while the target sentence moves the placeholder to the grammatically natural position.

Verification. Run automated placeholder parity checks and render strings with realistic values. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

6. Separate code from translatable strings

Source code contains both machine syntax and human-facing language. Translators need the user-visible content without gaining accidental control over syntax.

Professional method. Extract translatable resources from code and protect tags, keys, function names and commands unless the product specification explicitly localizes them. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. Sending raw source files encourages accidental edits and creates unnecessary cognitive load. A menu label may be translated while its JSON key remains stable.

Verification. Rebuild and run the product after translation; successful parsing is part of language QA. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

7. Treat URLs and domains as structured identifiers

Most URLs should not be translated as ordinary prose. Changing a path or hostname can break navigation, but some systems intentionally use localized slugs.

Professional method. Define URL policy explicitly: unchanged, mapped to locale-specific URL, or generated by the CMS. Do not let translators guess. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. One translator leaves all URLs source-language; another rewrites visible slugs manually; both may be wrong under the actual routing model. The visible link text can be localized even when the destination URL is protected.

Verification. Click every representative link in the final localized build. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

8. Control filenames and file extensions

Filenames can be user-visible language, technical references or both. Renaming can break links, imports or scripts, while never localizing can expose poor user experience.

Professional method. Classify filename components: protected extension, protected machine reference, optional localized display name and mapping between them. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. A translated filename is uploaded without updating references, or a machine name is shown directly to users. guide_v3.pdf can remain the stored asset name while the download label becomes a natural target-language title.

Verification. Test downloads, links and any automation that references the original file. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

9. Protect standards, clauses and citation identifiers

Formal references often require exact numbering or recognised naming. A changed standard number or clause label points to a different authority.

Professional method. Separate the fixed identifier from the translatable title or explanation and verify current official naming. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. A translator treats ISO, RFC, article numbers or section codes as ordinary text. A standard’s identifier remains fixed while the descriptive title may have an official translated form.

Verification. Cross-check references against the authoritative publication. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

10. Define treatment of acronyms and abbreviations

Some abbreviations remain global; others have established local forms. Protection cannot be assumed solely because text is uppercase.

Professional method. Record first-use rule, full form, target abbreviation if any, and locales where the source abbreviation is retained. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. Teams preserve opaque abbreviations that target readers cannot understand or invent abbreviations nobody uses. A global product acronym may be fixed while a government programme acronym changes by official language.

Verification. Search target-language authoritative sources and document the convention. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

11. Make do-not-translate rules locale-aware

A term protected in one market may be translated in another. Brands, legal names, campaigns and product conventions can vary by jurisdiction.

Professional method. Store locale scope with each rule instead of treating protection as globally binary. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. A global exclusion list becomes overbroad and prevents correct local naming. A product family may keep its English name globally except in a market where the company has an officially registered local name.

Verification. Test the rule against the exact target locale, not just the language. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

12. Distinguish do-not-translate from do-not-edit

A string can be translatable in principle but temporarily locked for workflow reasons. Translation status and editing permission are different concepts.

Professional method. Represent permanent non-translatability separately from approved/locked/currently-not-editable status in project management and tools. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. Teams use one flag for both, making later maintenance confusing. A previously approved legal sentence may be locked for the current release yet still have a valid translated version.

Verification. Ask whether the text should never be translated, or merely should not change in this workflow stage. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

13. Mark protected spans as close to the source as possible

Source-side metadata is more reliable than instructions in an email. The farther protection rules sit from the content, the easier they are to miss during extraction and tool handoff.

Professional method. Use structured content models, HTML translate metadata, XLIFF translatability information or localization-tool locks where appropriate. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. A spreadsheet note saying ‘do not translate blue cells’ disappears when content moves to another tool. A protected brand span can carry its status into extraction instead of depending on the translator recognising it from memory.

Verification. Inspect the actual package delivered to translators and confirm protection survives. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

14. Give translators grammatical integration guidance

Protected text still lives inside target-language sentences. Articles, case markers, word order, punctuation and plural agreement may need adaptation around an unchanged token.

Professional method. Provide examples of natural integration and state whether transliteration, declension or possessive forms are allowed. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. Overly rigid protection produces awkward or ungrammatical target prose. A protected English product name may remain unchanged while surrounding grammar marks possession or case in a target-language conventional way.

Verification. Native-read the complete sentence, not just the protected token. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

15. Build an exceptions process

Protection status changes over time. Rebrands, acquisitions, terminology decisions and local registrations can create new approved forms.

Professional method. Assign an owner, effective date and change log. Require downstream updates to translation memories, termbases and existing content when protection changes. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. Old and new rules coexist silently across releases. A renamed service remains protected under its new global identity while legacy documentation must be migrated deliberately.

Verification. Search the corpus for deprecated protected forms after each policy change. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

16. Test extraction and reconstruction, not only translation

A do-not-translate rule is successful only if the delivery system preserves it. Extraction can expose protected text, reconstruction can alter it, and filters can normalize characters or case.

Professional method. Pair protection policy with file-preparation testing and automated source-target comparisons. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. The terminology sheet is perfect but the export filter still sends protected code to translators. A placeholder can be locked in the CAT tool yet damaged by a later CSV conversion.

Verification. Run round-trip tests through the actual toolchain. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

17. Audit protected content during final QA

Protected does not mean invisible to review. A token can remain untranslated yet still be wrong, obsolete or in the wrong place.

Professional method. Include protected items in final identity, placement and reference checks. Verify links, codes, brand spelling and current official names. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. Reviewers skip everything marked non-translatable and miss outdated identifiers. An unchanged product code may be correct textually but belong to the wrong product variant.

Verification. Check both preservation and contextual correctness. If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

18. Keep the list small enough to trust

Overprotection makes localization brittle. If hundreds of ordinary words are marked non-translatable, target language becomes unnatural and reviewers start ignoring the list.

Professional method. Protect only items with a clear identity, function, authority or strategic reason. Put preferred ordinary vocabulary in the termbase instead. The important discipline is to make the rule explicit enough that another translator, reviewer or developer could apply it to the next occurrence without relying on memory.

Where teams go wrong. A company freezes generic English marketing nouns as if they were trademarks. A genuine trademark belongs on the do-not-translate list; a preferred translation for ‘dashboard’ belongs in terminology governance.

Verification. Challenge each entry periodically: what breaks if this is translated correctly? If the check fails, return to the source, locale specification, interface context or governing standard before polishing the wording. A visually attractive result is not a substitute for structurally correct multilingual content.

A repeatable operating sequence

A reliable exclusion workflow begins with classification and ends with toolchain verification.

Inventory candidate protected content from product, legal, brand and engineering sources.
Classify each item by protection reason.
Research authoritative target-language names before freezing source-language forms.
Assign global or locale-specific scope.
Record allowed grammatical treatment and visible-display behaviour.
Encode protection in structured source content or localization exchange where possible.
Test extraction so protected content is locked or clearly marked.
Render translations with realistic variables and surrounding grammar.
Run automated identity checks for codes, variables and identifiers.
Review the exclusion list at every major brand, product or locale change.

The sequence is deliberately recursive. When later testing reveals a hidden assumption, return to the earlier decision that created it. Professional translation systems improve by tracing errors to their source rather than repairing only the visible symptom.

Worked scenarios

1. Global brand, local legal entity

The consumer brand stays in English, but the registered subsidiary has an official local-language corporate name. The controlling risk is treating all related names as one protected string.

Create separate entries with separate authority and locale scope; protect the brand globally while using the registered legal name where required. The point of the exercise is not to memorise one answer. It is to identify which layer—linguistic meaning, script behaviour, locale convention, file integrity, product policy or reader expectation—owns the decision.

2. Localized website slug policy

The CMS supports locale-specific slugs but the engineering team also uses stable internal route IDs. The controlling risk is translating machine routes instead of display URLs.

Protect internal identifiers, let the CMS generate approved locale URLs and localize visible link text independently. The point of the exercise is not to memorise one answer. It is to identify which layer—linguistic meaning, script behaviour, locale convention, file integrity, product policy or reader expectation—owns the decision.

3. Product command name inside documentation

A CLI command looks like ordinary English. The controlling risk is translating executable syntax.

Protect the command token, translate the explanatory sentence and verify the command still runs after documentation export. The point of the exercise is not to memorise one answer. It is to identify which layer—linguistic meaning, script behaviour, locale convention, file integrity, product policy or reader expectation—owns the decision.

4. Protected acronym nobody understands

The business wants a global acronym retained for brand recognition. The controlling risk is identity protection undermining comprehension.

Keep the acronym but allow a target-language explanation at first use when the brief and audience require it. The point of the exercise is not to memorise one answer. It is to identify which layer—linguistic meaning, script behaviour, locale convention, file integrity, product policy or reader expectation—owns the decision.

5. Variable embedded inside an inflected language

The target grammar changes according to the value inserted at runtime. The controlling risk is protecting syntax but producing ungrammatical output.

Keep the variable identifier unchanged while redesigning the sentence or using plural/gender-aware message logic. The point of the exercise is not to memorise one answer. It is to identify which layer—linguistic meaning, script behaviour, locale convention, file integrity, product policy or reader expectation—owns the decision.

6. Legacy trademark renamed mid-project

Half the corpus contains the old protected form. The controlling risk is new policy applied only to newly translated strings.

Version the exclusion list, search historical target content and migrate the deprecated form under controlled change management. The point of the exercise is not to memorise one answer. It is to identify which layer—linguistic meaning, script behaviour, locale convention, file integrity, product policy or reader expectation—owns the decision.

Do-not-translate governance: twenty professional drills

Use these drills to practise diagnosis. For each one, write the governing rule, the evidence you would request, the safest provisional action and the final verification step.

1. The source contains a product name beside a translated noun

Classify the product name as identity data and the noun as natural-language content. Protect the name, translate the noun, and test the combined phrase in the target sentence. After making the decision, explain what would cause you to reverse it. That final sentence is important: it turns a preference into a controlled professional judgment.