Translate, then localize (two passes)
Goal: EN→ZH in two passes: faithful translate first, localize second—pass B must not sneak in new facts.
Best for: EN↔ZH product copy, emails, help text, HK vs mainland tone shifts.
One-shot “translate and make it marketing-ready” creates muddy mix and sneaky meaning changes. Approve fidelity first. Then localize for audience and market—keeping product/legal names stable.
Translate gets words across; localize fits place, tone, and reader habits. Do them as two passes—especially for HK/TW/CN phrasing and English mix.
Name the two passes in the chat (“PASS1 translate”, “PASS2 localize”) so you can diff them without guessing which edit did what.
Why beginners skip this
Doing translate and localize in one pass feels efficient—tone and wording miss both sides. Faithful first, then local.
Step 1 — Pass A: faithful translate
Pass A: on a paragraph you must send, keep meaning and numbers; ban new soft claims.
Translate faithfully to [target language].
Keep meaning. Mark idioms you are unsure about with [?].
Do not rewrite for marketing yet.
Keep unchanged: [product names, button labels if UI stays EN, legal entity names]
Step 2 — Pass B: localize
Pass B: local tone only; keep brand names; delete claims that appear only in Pass B.
Localize the approved translation for [audience in market: e.g. zh-HK office workers / zh-CN mainland app users].
Natural phrasing; keep legal/product names stable.
List 5 changes you made and why.
Do not add offers or claims absent from the source.
Example
Filled prompt
Pass 1: translate this EN paragraph to ZH-CN literally. Pass 2: localize for HK bilingual professionals (may keep brand names in EN, soft tone). Source: [paste]. Do not add facts.
What good output looks like
- Matches outline/voice freeze for “Avoid awkward bilingual output by separating faith”
- No AI-slop openers; one concrete proof from your notes
- Numbers/names frozen — polish does not invent
- Pass/fail: phone-skim 20s still clear
Step 3 — HK vs mainland check
If both markets matter, run Pass B twice with different reader lines—or follow the HK bilingual mail guide.
Example
Filled prompt
EN→ZH for Harbor client note. Freeze names/numbers first.
Pass 1 meaning-true. Pass 2 HK register. No invented company facts. Human skim before send.
What good output looks like
- No AI-slop openers; one concrete proof from your notes
- Numbers/names frozen — polish does not invent
- Pass/fail: phone-skim 20s still clear
- Matches outline/voice freeze for “Avoid awkward bilingual output by separating faith”
Save this card
Card: Faithful translate first, localize second—pass B must not sneak in new facts. Keep this beside the tool; read before you start.
Before you start
Name the reader and freeze facts on paper for “Avoid awkward bilingual output by separating.” If outline bullets do not exist yet, stop before prose. Guide: writing-translate-then-localize. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.
How to use this week
This week faithful-translate a real draft once, then run localize separately; store the two artifacts apart.
Keep it real
Run this guide’s Practice now on work you will actually ship this week—not a fictional scenario. Dated notes beat perfect theory.
Do not bookmark-only
Finish Practice now, then tick this guide on your path. Titles unread are not skills.
Close the loop
Write one line: next time I merge translate and localize into one pass, I refuse send.
One more pass
Re-read your Save-this-card line. If it is vague, rewrite it until a stranger could apply it.
Example
Filled prompt
EN→ZH-HK help paragraph. Freeze product names.
Meaning then register. Human skim before publish.
Context: real workstream this week (Asia/Shanghai). Name actual files/people.
Constraints: no invented metrics/owners/prices; label Unknowns; stop before send/delete/pay.
Done check: I can mark pass/fail in one minute on the output.
What good output looks like
- Numbers/names frozen — polish does not invent
- Matches outline/voice freeze for “Avoid awkward bilingual output by separating faith”
- Pass/fail: phone-skim 20s still clear
- No AI-slop openers; one concrete proof from your notes
Red flag
Localize pass sneaking new facts; skip faithful translate—diff facts after pass B.
Pitfalls
| Pitfall | Fix |
|---|---|
| One-shot marketing translate | A then B |
| Translating UI strings that must stay EN | Keep-unchanged list |
| Softening legal meaning | Pass A fidelity gate |
| Mixing EN/ZH in one sentence | Language contract |
Example
Filled prompt
Temptation: skip the habit for writing-translate-then-localize to save five minutes.
Job still: Avoid awkward bilingual output by
Smallest correct pass: Done visible · checkable artifact · Unknowns [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: artifact + refuse-line said aloud.
What good output looks like
- Names the shortcut refused (specific to writing-translate-then-localize)
- Still delivers checkable output for “Avoid awkward bilingual output by”
- Unknowns labeled; draft-only
- Pass/fail: refuse-line dated (writing-translate-then-localize #4)
Practice now
Humor check: jokes localized or cut—never literal (Asia/Shanghai).
Currency/date: localize formats, not just words (Asia/Shanghai).
Register match: match formality to the target locale norm (Asia/Shanghai).
Name keep: proper nouns stay; tone localizes (Asia/Shanghai).
Untranslatable: list one phrase you localize instead of translate (Asia/Shanghai).
Audience swap: localize for the real reader locale, not dictionary defaults (Asia/Shanghai).
Localize drill: translate one paragraph then localize one idiom; keep meaning, drop calques (Asia/Shanghai).
Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.
Tonight faithful-translate a real draft once, then run localize separately; store the two artifacts apart.
Ship gate: localize one paragraph today or mark incomplete.
One sentence takeaway
Faithful translate first, then localize alone; store the two artifacts apart.
Word-floor practice
Run the Today card once on a real artifact. Write pass/fail + never-do with date Asia/Shanghai. If you only skimmed, do not mark this guide done.
Next
Multilingual prompts · Bilingual HK workflow · Voice pass · Outline before prose
先翻译,再本地化(两遍)
目标: 英译中分两遍:先忠实直译,再按读者本地化,并且不添加事实。
适合: 一键翻译就想发,或本地化时偷偷加料的人。
直译保住意思;本地化让它像当地人会说的话。两遍绑在一起,才不会「通但不像人」,或「像人却不忠」。
为什么新手跳过
翻译和本地化一次做完像省事;语气与用词会两边都不对。先忠实,再本地。
步骤 1——A 遍:忠实翻译
A 遍:对着真要发的段落保意思与数字;禁止新软性主张。
忠实翻译成 [目标语言]。
保持意思。不确定的习语标 [?]。
先不要按营销改写。
保持原文: [产品名、如果界面仍是英文则按钮文案、法律实体名]
步骤 2——B 遍:本地化
B 遍:只调本地语气;品牌名不动;删掉只在 B 遍冒出的主张。
把已批准译文本地化给 [市场读者:如 zh-HK 上班族 / zh-CN 内地应用用户]。
措辞自然;法律/产品名稳定。
列出 5 处改动及原因。
不要添加原文没有的优惠或主张。
实例
填好的提示词
第 1 遍:把这段英文译成简体直译。第 2 遍:本地化为香港双语职场(品牌名可留英文、语气柔和)。原文:【粘贴】。不要添加事实。
边界:不编造;未知标 [?];发送前停下。
完成检查:一分钟内能判过/不过。
像样的输出大概长这样
- 流程拆成两遍:先直译求准确,再本地化求像当地人,中间不混做
- 本地化时不添加原文没有的事实、折扣或承诺
- 第二遍明确点出港式职场语气,品牌名可保留英文
- 两遍对比后,能看出「语句通」和「读起来像当地人」的差别
- 步骤短到下一封产品信还能按同一流程复用
步骤 3——港/内地检查
如果两个市场都要,B 遍跑两次、换读者行;或去看港 / 双语实务指南里的邮件场景。
实例
填好的提示词
请列出 5 条面向香港读者的产品邮件本地化检查(日期格式、语气、CTA 清晰、双语主题、无仅内地黑话)。
B 遍禁止偷偷加新主张;品牌名与数字不动。
边界:不编造;未知标 [?];发送前停下。
完成检查:一分钟内能判过/不过。
像样的输出大概长这样
- 本地化检查正好五条,条条可打勾
- 覆盖日期格式、语气、CTA、双语主题行、以及有无仅内地黑话
- 面向香港读者写得务实,不装腔
- 场景贴住产品更新邮件,不漂到无关文案
- 短到能钉在邮件模板最上方
- 未知标出;不编造负责人、日期或指标
保存这张卡
记下:编辑轮或译→本地化里管用的一句改法。标上日期。
开始前
先写清读者是谁,再备一张冻结事实清单。不知道谁会读就先停,润色补不出读者。
本周怎么用
本周对一篇真稿先忠实翻译一版,再单独跑本地化;两遍产物分开存。
保持真实
用本周真要交付的工作做「现在就练一次」,别编假场景。带日期的实操笔记,比完美理论有用。
不要只收藏
先做完「现在就练一次」,再在学习路径上打勾。只收藏不练,标题变不成技能。
闭环
写下一行:下次翻译本地化一次做完,我拒绝发出。
再过一遍
重读「保存这张卡」那一行。如果含糊,改到陌生人也能执行。
红旗
翻译和本地化一次做完,语气与用词两边都不对;先忠实,再本地。
常见坑
| 坑 | 改法 |
|---|---|
| 一键译完就发 | 两遍:直译→本地化 |
| 本地化偷偷加事实 | 第二遍不添加原文没有的内容 |
| 忽略读者地区 | 港式检查:日期/语气/CTA/黑话 |
现在就练一次
今晚就练:对一篇真稿先忠实翻译一版,再单独跑本地化;两遍产物分开存。
一句话带走
先忠实翻译,再单独本地化;两遍产物分开存。
下一步
← Back to home · Learn · Tools · Compare · Start