top of page

What Actually Goes Into a Content Translation

Writer: Tamim Balkhi
Tamim Balkhi
Sep 3
2 min read

Most people picture translation as swapping words from one language into another. In practice, a lot more happens before a piece of content is ready to publish — especially with something factual, like health or public-information content, where precision and tone both matter.


I recently worked through a short public-health fact sheet from English into Turkish as a hands-on example of my Content Translation process, and wanted to walk through what that actually looks like from start to finish.


Screenshot of an English-language public health fact sheet titled "Dengue," showing sections including Key Facts and Overview with text about dengue virus transmission, symptoms, and prevention.
The source document — a public-health fact sheet in English, before translation.

Step 1: Reading before translating


Before touching a single sentence, I read the whole piece — structure, tone, and any terms that repeat throughout. A document like this has a clear pattern: short factual statements, a consistent register, and specific terminology that needs to stay exactly the same every time it appears.


Step 2: Translating with consistency in mind


The translation itself is only the first layer. The real work is making sure that:


  • The same term is translated the same way every single time it shows up (a health term rendered five different ways across one document reads as unfinished, not natural)

  • Numbers, dates, and measurements follow the correct local formatting

  • The tone matches the source — factual and clear stays factual and clear, it doesn't become stiffer or looser in translation


Screenshot of memoQ translation software showing English source text and Turkish target text in parallel columns, with a translation results panel and project details visible on the right.
The translation in progress in memoQ — English source and Turkish target side by side.


Step 3: A dedicated quality check


Once a first draft was done, I went through it again specifically looking for consistency issues: places where one English term had drifted into two or three different Turkish renderings, formatting slips, and spots where a word had accidentally been left untranslated. This is a separate pass from the translation itself — different mindset, different focus.


  • Before — "severe" translated as "Ağır," inconsistent with the term used elsewhere in the document.
  • After — corrected to "Şiddetli" to match terminology used throughout.


Step 4: Building a reference for next time


For any topic I expect to come back to, I keep a running glossary of the terms I've settled on and why — so the next document in that subject area starts from a consistent baseline instead of relitigating the same word choices from scratch.


Screenshot of a glossary table with columns for English, Turkish, and Note, including entries for "dengue," "severe dengue" (standardized to "şiddetli dang humması" after inconsistent use of ağır/ciddi), "WHO," and "viremic."
A snippet from the glossary I keep for recurring topics — settled terms and the reasoning behind them.


Why this matters for content translation specifically


Content Translation covers things like web copy, articles, and informational material — content meant to be read naturally by a general audience, not filed or certified. That makes internal consistency and natural phrasing the whole job: nobody sees the process, they just notice if something reads a little off.


Screenshot of the completed Turkish translation of the dengue fact sheet, showing sections including Önemli bilgiler and Genel Bakış with fully translated body text.
The finished Turkish document — formatted and ready to publish.

If you're weighing whether your own English content is ready to be translated — or already have a Turkish or Arabic version you're not fully sure about — I help businesses in Türkiye and beyond with exactly this kind of work. Feel free to reach out and tell me what you're working on, or see my services for more on how I can help.

 
 
 

Comments


bottom of page