Writing for Translation: How to Make Your Text Travel Well
The quality of a translation, whether made by a person or a machine, depends heavily on the source text. Writers who anticipate translation can save time, money and confusion. The guidelines below overlap with plain-language principles, which is no accident: clear writing is easier for everyone to interpret.
Keep sentences short and complete
Long sentences with several clauses leave room for ambiguity about what refers to what. Aim for one idea per sentence. Avoid leaving out words that are grammatically optional in English, such as “that” in “the file you sent”, when omission could cause misreading. Use the active voice where possible, since it makes the actor explicit.
Be consistent with terms
If you call something a “dashboard” in one paragraph and a “control panel” in the next, a translator may assume two different things. Choose one term for each concept and keep it throughout. Maintain a short glossary and share it with the translation team.
Avoid idioms and cultural shortcuts
- Phrases like “ballpark figure”, “touch base” or “hit the ground running” rarely have equivalents.
- Sports and local references may confuse readers elsewhere.
- Jokes and wordplay seldom survive; if humour is important, flag it and ask for adaptation rather than direct rendering.
Watch ambiguous words
Many English words serve as both nouns and verbs, such as “file”, “set” and “light”. Pronouns like “it” and “they” can point to unclear antecedents. Where confusion is possible, repeat the noun. Avoid stacking nouns, as in “customer service response time report”, which hides relationships between the words.
Handle formats and variables carefully
- Do not build sentences from separate fragments, because word order differs between languages.
- Avoid placeholders that depend on grammar, such as inserting a name into the middle of a sentence where the language might require different endings.
- Write dates in an unambiguous way, for example with the month spelled out.
- Specify units and provide conversions only if needed.
Leave room for expansion
Some languages need noticeably more space than English, which matters for buttons, menus and tables. Brief labels in the source may become cramped. Discuss limits with designers and give translators character limits where they apply.
Provide context
- Describe the purpose, audience and tone of the text.
- Share screenshots or layouts so that translators see where text appears.
- Explain any brand names or product names that should remain unchanged.
- Indicate what the target readers already know.
Do not embed text in images
Words baked into graphics require redesign for every language. Keep text as live text on top of images, or supply editable source files.
Mark text that should not be translated
Product codes, commands and certain legal names may need to remain as they are. Use clear notation or notes so that this is respected.
Use review and feedback loops
Ask translators what puzzled them. Their questions reveal ambiguity in the original. Update the source accordingly so future work becomes easier. If you rely on machine translation, test a sample paragraph and see where it stumbles; the errors tell you which phrases to simplify.
Writing for translation is basically writing for a global reader. Clarity, consistency and context are the three habits that repay the effort again and again.
Create a reusable checklist
Turn these points into a short checklist that writers consult before handing text over: terms consistent, idioms removed, context supplied, placeholders checked, notes added. A page of reminders, used every time, quietly improves every language version that follows.