Free to read · no account needed

10 min · prompt

Multilingual prompts without muddy mix

Goal: Lock instruction vs draft languages; keep proper nouns intact—no Chinese–English salad in one sentence.

Best for: Teams that research in one language and ship in another; HK/bilingual workers switching mid-day.

Models will happily mix languages mid-sentence if you do not declare the rules. Product names, error codes, and UI strings often must stay in the original form. Say that out loud in the prompt.

Why beginners skip this

Mashing ZH/EN in one sentence feels tidy—the model follows the muddle and both readers tire. Pick a primary language, then mark exceptions.

Step 1 — Declare languages like a contract

Declare the output language at the top like a contract; one language for the whole thread.

Input language: [en / zh / mixed notes]
Output language: [en / zh] — one language only
Do not mix languages inside one sentence.
Keep unchanged (original form): [product names, SKUs, error codes]
If a term has no natural translation, keep English and add a short gloss in parentheses once.
Audience locale: [US / HK / mainland / …]

Step 2 — Chinese notes → English sales bullets

Example

Filled prompt

Input language: Chinese meeting notes
Output language: English bullets for US sales
Keep unchanged: “iswarp”, “Claude Projects”, error code E-204
Do not mix languages in one sentence.
Audience locale: US
Task: Turn notes into 6 bullets: problem → what we ship → proof point → CTA.
Notes:
- 新手不知道 ChatGPT/Claude/Grok 怎么选
- 我们按场景写指南,不堆参数表
- 免费阅读,不用注册

What good output looks like

  • Clean English only in the bullets
  • Product names untouched
  • No “我们 ship 一个 seamless 体验” mashups
  • CTA matches what you can actually offer

Step 3 — Two-pass when you need both languages

Do not ask for “both languages in one block” first—sequence it: full language A, then translate the whole block to language B.

Pass A: Output English only (rules above).
Pass B: After I approve, localize to [zh-HK / zh-CN] for [audience]. Keep product names. Prefer natural phrasing over literal calques.

If you need both in one doc, request a labeled section structure: ## EN then ## ZH—never interleaved sentences.


Example

Filled prompt

Live task this week (not a toy): apply this guide's Goal — Control input and output language clearly when you work across English and Chinese—so drafts stay pu
Fill with your real artifact names/files. Constraints: no invented facts; label Unknowns; stop before send/delete/pay.
Return the working prompt + one pass/fail check I can mark in a minute.

What good output looks like

  • Goal/Format/Boundaries all present for “Control input and output language clearly when you”
  • One example beats stacked IMPORTANT words
  • Version/date kept when template changes
  • Pass/fail: zero clarifying turns on live task

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Reality check

Open this guide beside a live task. If you cannot name the task, pick one before reading further.

Close the loop

Write one line: next time I mash ZH/EN in one sentence with no exception list, I refuse send.

Example

Filled prompt

EN bullets → ZH-HK email. Freeze names/numbers.
Pass1 meaning · Pass2 HK register. No mixed EN leftovers in body except product names.

What good output looks like

  • One example beats stacked IMPORTANT words
  • Version/date kept when template changes
  • Pass/fail: zero clarifying turns on live task
  • Goal/Format/Boundaries all present for “Control input and output language clearly when you”

Red flag

Output language unlocked; half-translated salad shipping—lock input/output languages.

Save this card

Card: When switching languages, lock input/output language so drafts ship—not a half-translated salad. Keep this beside the tool; read before you start.

Before you start

Keep the last failing output visible. You will repair the prompt for “Control input and output language clearly when” against that failure—not a fresh toy ask. Guide: prompt-multilingual-without-muddy-mix. 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 set a primary language on a real bilingual draft, list exception terms aside; rewrite every mashed sentence.

Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).

Pitfalls

PitfallFix
“Translate and improve” with no output languageName input + output every time
Letting UI strings get “helpfully” translatedList keep-unchanged tokens
One-shot “make it bilingual”Two passes; approve EN before ZH
Mainland tone for HK readers (or reverse)State locale; see bilingual HK workflow

Example

Filled prompt

Temptation: skip the habit for prompt-multilingual-without-muddy-mix to save five minutes.
Job still: Control input and output language clearly
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 prompt-multilingual-without-muddy-mix)
  • Still delivers checkable output for “Control input and output language clearly”
  • Unknowns labeled; draft-only
  • Pass/fail: refuse-line dated (prompt-multilingual-without-muddy-mix #4)

Practice now

Glossary three: three locked bilingual terms on Save (Asia/Shanghai).

Output lang tag: first line states output language (Asia/Shanghai).

Lang lock: one system language; mark output language explicitly (Asia/Shanghai).

Multilingual drill: one language for instructions, one for output—label both (Asia/Shanghai).

Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.

Tonight set a primary language on a real bilingual draft, list exception terms aside; rewrite every mashed sentence.

Buffer line: name the artifact path you used (Asia/Shanghai).

One sentence takeaway

Primary language first; exception terms listed aside; rewrite mashed sentences.

Next

Translate then localize · Bilingual HK workflow · GFB pattern

← Back to home · Learn · Tools · Compare · Start