Plan H: AI Translation / Multilingual Export

Preprocess source → build glossary → AI first pass → human review → localization adaption → QA & ship

Time
1-3 hours / language
Cost
Low-Medium
Difficulty
Beginner

Best for

Best for going abroad: product copy, website/app multilingual, marketing content and documentation — machine translation for the base, human review for quality.

Steps

Preprocess the source

10 min

Formatting tools + you

Clean layout noise (extra line breaks, markup, placeholders) and flag what must be preserved. Clean input means clean output.

💡Tag placeholders like %s, {name} and {{variable}} separately so translators never touch them.

Build a glossary

15-30 min

ChatGPT / Claude

Collect brand names, product names, jargon and slogans into a source↔target glossary, ruling which stay untranslated and which get fixed translations. Consistency starts here.

💡Brand names usually stay as-is; feature words (e.g. 'save') get one canonical translation site-wide.

AI first pass

30-60 min

DeepSeek / ChatGPT / translation API

Feed 'glossary + style requirements + source' together, translating segment by segment. For bulk, use an API or script, giving each line context to avoid mis-splitting.

💡Give the model 1-2 polished reference sentences (few-shot) for much steadier style.

Human review

1-2 hours

Native speaker / professional translator

Review cultural context, tone and marketing hooks line by line; reflow long sentences to target-language habits. Brand-voice consistency is won at this gate.

💡Give reviewers a scope ('tone / length / culture only') so style doesn't drift while editing.

Localization adaption

30 min

Localization platform / dev handoff

Localize dates, currency, units and time zones; adapt truncation and wrapping caused by different text lengths, and restore placeholders to the right slots.

💡EN→ZH often grows ~30%, ZH→EN can shrink ~30%; leave flex in your layout.

QA and ship

30 min

Back-translation spot checks + UI screenshots

Back-translate samples to compare semantics; screenshot key pages for truncation, overlap and untranslated leftovers before launch.

💡Run an automated 'untranslated residue scan' before release — more reliable than eyeballing screens.

Tools involved

Pitfalls to avoid

Inconsistent terminology

The same feature translated differently across pages is a going-abroad killer; build a glossary and enforce it globally.

Awkward cultural context

Literal translation trips over memes, puns and taboos; native review is the safety net.

Lost format / truncation

Placeholders shift and text overflows after translation; use a localization platform plus screenshot QA.

Machine-translation smell

Pure MT reads stiff; the AI-pass + human-polish combo beats either alone.

Related Workflows