Do-Not-Translate Terms, Reset, and Removal

Protect exact terms, reset a damaged list, or remove terminology without losing evidence unexpectedly.

Written By 4ALL.LIVE

Last updated 12 days ago

Protect exact terms, reset a damaged list, or remove terminology without losing evidence unexpectedly.

Best for: Multilingual producers, caption operators, accessibility leads, event administrators, and authorized language reviewers.

Before you start

Translation, target-language count, glossaries, and text-to-speech depend on event permissions, provider/model/language support, plan entitlements, usage allowances or wallet, and eligible BYOK configuration.

  • Confirm source language and provider quality first.
  • List approved target locales, terminology, voice requirements, and human review responsibilities.
  • Test with representative content before distributing viewer links.

Step by step

  1. Identify exact-match intent. Use DNT for names, brands, codes, acronyms, or wording that must remain unchanged where the provider supports it.
  2. Add and test DNT. Check punctuation, inflection, case, surrounding language, and each target locale.
  3. Review conflicts. A glossary replacement and DNT rule for the same term can conflict.
  4. Prepare reset. Export/record the approved current list when retention allows.
  5. Use Reset deliberately. The reset clears saved terms and do-not-translate words for the event; confirm exact event.
  6. Verify after reset. Run source and target test phrases.
  7. Remove obsolete entries. Delete terms no longer approved and test nearby words.
  8. Audit/document. Record owner, reason, provider, and time.

What success looks like: The configured language service produces the intended accessible output with known quality, latency, usage, and recovery behavior.

Check your setup

  • Protected terms behave as intended, or a reset/removal returns the event to a known clean terminology state.

Troubleshooting

Term still translated

Check provider/DNT support, exact locale, punctuation, casing, and cache.

Reset was accidental

Restore only from an approved export/version if available and document the incident.

Old behavior persists

Clear/refresh allowed cache, verify saved event/provider scope, and generate a new segment.

Security and operational notes

  • Reset may be destructive.
  • Do not use DNT for content that requires grammatical localization without review.
  • Protect exported lists.