Translation readiness · hard · v4.6.1

TRN-04

Avoid idioms, slang, and culturally specific references. These don't translate and confuse non-native speakers.

Pass example

This feature is simple to set up.

Fail example

Setting up this feature is a piece of cake.

Relevant content types

Notes by content type

All content types
Flag slang, colloquial expressions, and culturally specific phrases that have clear plain-language alternatives (e.g., 'tap into' → 'use', 'piece of cake' → 'simple', 'let's go' → descriptive CTA). Do NOT flag widely understood metaphorical language that professional translators handle routinely, such as 'peace of mind,' 'take control,' or 'journey' used to describe a process. The test: would a professional translator working in this vertical need to look this phrase up, or would they translate it idiomatically without hesitation?

Sources

Style guides that shaped this standard. Each is listed on /sources with its license and opt-out path.

  • Mailchimp

Version history

  1. v4.6.1 · 2026-04-23

    Per-standard version tracking introduced. Every standard starts at the library version current at introduction; bump per-standard when the rule text, examples, or content_type_notes change.

Related standards

Other standards in the Translation readiness category.

  • TRN-01 Avoid words with multiple meanings that confuse translators. Replace 'once' (use 'after'), 'right' (use 'correct'), and 'since' (use 'because').
  • TRN-02 Avoid unnecessary -ing words that create ambiguity in translation. Rewrite gerunds and -ing adjectives when a simpler form exists. Progressive verb forms are acceptable when they describe an ongoing action ('Uploading your file...', 'Loading results...').
  • TRN-03 Repeat subjects and verbs in compound sentences instead of relying on implied subjects. Many languages require explicit subjects.
  • TRN-05 Keep function words like 'the,' 'a,' 'that,' and 'to' even if they seem unnecessary. Removing them creates ambiguity in translation.
  • TRN-06 Use metric measurements and 3-letter ISO currency codes (USD, EUR, GBP) instead of symbols when writing for international audiences. Currency symbols are acceptable in locale-specific content that will be localized (adapted per region) rather than translated (same content in multiple languages).
  • TRN-07 Avoid using different words for the same concept within a single piece of content. If 'workspace,' 'team hub,' and 'project space' all refer to the same thing, pick one term and use it consistently. Different terms are acceptable when they refer to genuinely different concepts.

← The content model