DNT terms list 

DNT stands for “do not translate.” A DNT terms list is maintained as part of a project glossary and tells translators, CAT tools, and machine translation engines which content to pass through untouched. When a term on the list appears in a source string, it gets highlighted or locked in the translation interface, signaling that no change should be made regardless of the target language.

The need for a DNT list goes beyond brand consistency. In software and documentation, strings often mix translatable text with variables, placeholders, code snippets, and proprietary terminology that must remain intact for the product to function. Without a clearly maintained list, a translator working under time pressure may not know whether “Accu-Chek,” font-size, or “Just Do It” should be translated or left alone.

What belongs on a DNT list #️⃣

Some terms are obvious candidates. Others require deliberate decisions by the localization manager or product team before translation starts. Common categories include:

• Brand and company names — names that are intentionally language-neutral or legally protected as trademarks
• Product and feature names — globally marketed names that should not be adapted per market
• Trademarks and registered marks — any term with legal protection in the source language
• Code and technical strings — variable names, file paths, HTML tags, CSS properties, API parameters, and placeholders
• Proper nouns — names of people, specific locations, or organizations without a standard translated form
• Legal terminology — terms required by regulation to remain in the source language

🚫 Key points about DNT terms lists #️⃣

• Best practice is to mark DNT terms directly in the source content where possible, with the glossary as a backup. This double protection reduces the chance of accidental translation even when instructions are overlooked.
• DNT status can be applied globally across all languages or selectively, with per-language overrides. A product name that stays untranslated in most markets may require a local equivalent in others due to legal or cultural requirements.
• MT engines will attempt to translate or transliterate unprotected terms. A brand name like “Pink Floyd” can come back transliterated in certain scripts if no DNT rule is configured.
• A missing or outdated DNT list is one of the most common sources of translation inconsistency in large projects, especially when multiple translators or vendors work in parallel.
• DNT terms should be reviewed with each release. Product names change, features get renamed, and new technical terms are introduced regularly.

🤖 DNT lists and machine translation #️⃣

MT presents a specific challenge that human translators do not. A human reading context can usually recognize a brand name. An MT engine cannot without explicit rules. Most TMS platforms support wrapping protected terms in tags or passing DNT configuration directly to the MT engine before translation. Without this, even well-maintained DNT lists may not protect terms in automated pipelines.

How Localazy handles DNT terms #️⃣

In Localazy, DNT terms are managed through the project glossary. Terms flagged as do-not-translate are surfaced in the translation editor, giving translators a clear signal to leave them unchanged. Per-language overrides are supported for cases where a term needs a local equivalent in a specific market. This works for both human translation workflows and MT pipelines.

Learn more about managing glossaries and QA checks in the Localazy docs.