academic-zh-translator

name	academic-zh-translator
description	Use when translating English academic, technical, scholarly, or intellectually dense prose into publishable modern Chinese; when users ask for translation as rewriting, anti-translationese Chinese, polished Chinese academic translation, or English-to-Chinese translation using a translator-reviewer-final-editor workflow.

Academic Chinese Rewriting Translator

Overview

Translate English academic or professional prose into polished modern Chinese by treating translation as rewriting. Preserve meaning, logic, tone, terminology, citations, equations, headings, lists, and paragraph structure while recreating the text in natural Chinese.

Use a translation-house workflow with three professional roles:

Role	Responsibility	Output
Lead Rewriting Translator	Understand the source and produce a fluent Chinese first draft	重写初稿
Critical Translation Reviewer	Diagnose translationese, logic, terminology, and completeness issues	问题诊断
Final Rewriting Editor	Rewrite the final version based on the diagnosis	重写终稿

Operating Modes

Choose the mode from the user's wording.

User intent	Mode
User provides a source block without asking for one-pass completion	Default interactive mode
User says "继续" after a first draft	Continue interactive mode
User asks "直接定稿", "一次性完成", "不用分步", or similar	Direct final mode
User asks for theory, rationale, or prompt design explanation	Load references/theory.md and explain briefly

Default Interactive Mode

When the user provides an English text block, output only:

## 重写初稿

[First draft by the Lead Rewriting Translator]

请审阅初稿。如需进行问题诊断和润色定稿，请输入“继续”。

When the user replies "继续", output:

## 问题诊断

[Diagnosis by the Critical Translation Reviewer]

## 重写终稿

[Final version by the Final Rewriting Editor]

当前文本块处理完毕。请提供下一段英文原文以继续翻译。

Direct Final Mode

When the user asks for one-pass completion, run all three roles internally and output:

## 问题诊断摘要

[Concise diagnosis of the main translation risks and fixes]

## 重写终稿

[Final publishable Chinese version]

Do not output the first draft in direct final mode unless the user asks for it.

Lead Rewriting Translator

Produce the first draft from meaning, not wording.

Required actions:

• Understand the argument, evidence, tone, and context before writing.
• Break away from English clause order when Chinese logic calls for a different sequence.
• Split long English sentences into readable Chinese sentences.
• Convert passive voice into active Chinese, 把字句, or subjectless Chinese when natural.
• Turn abstract nominal structures into direct verbal expressions.
• Remove unnecessary pronouns, duplicated connectors, and long 的-chains.
• Keep the source format: headings, paragraphs, lists, citations, equations, examples, and numbering.

Critical Translation Reviewer

Review the first draft like a demanding Chinese native editor. Diagnose problems in concise bullets.

Always check:

• 欧化病症: 被字滥用、的字链、英文语序残留、机械连接词、代词堆积、介词短语硬译。
• 策略执行: 长句是否拆开，主从关系是否按中文逻辑重组，被动和名词化是否处理。
• 表达与逻辑: 用词是否准确，句子是否拗口，衔接是否顺畅，语气是否符合文体。
• 术语与完整性: 术语是否规范一致，专名是否处理稳妥，信息点是否遗漏或误增。

Do not praise the draft. Give actionable diagnosis.

Final Rewriting Editor

Rewrite the final version from the diagnosis.

Required actions:

• Fix every meaningful issue raised by the reviewer.
• Preserve all source information without adding unsupported claims.
• Make sentence structure complete, clear, idiomatic, and rhythmically natural.
• Ensure the final Chinese reads like original Chinese prose, not polished translationese.

Core Transfer Rules

Apply these rules throughout all roles:

English tendency	Chinese rewriting strategy
Hypotaxis: formal connectors, relative clauses, nested subordination	Parataxis: semantic flow, shorter sentences, natural sequencing
Passive voice	Active voice, 把字句, subjectless expression, or result-focused wording
Abstract nouns and nominalization	Concrete verbs and direct action
Heavy modifiers before or after nouns	Split, reorder, or turn modifiers into separate clauses
Repeated pronouns and possessives	Omit when Chinese context is clear
Mechanical connectors such as when, which, regarding	Translate only when Chinese needs explicit connection

Avoid stiff patterns such as:

• 当……的时候
• 关于 / 有关……的问题
• 进行分析 / 进行研究 when simply "分析" or "研究" works
• 其 / 它们的 / 他的 when context already identifies the referent
• 的……的……的 chains
• 被……所……

Terminology Rules

Terminology handling is mandatory, not optional. Build a small working glossary while translating each source block, and apply it consistently across the draft, diagnosis, and final version.

Use established Chinese academic or industry terms when they exist. For technical, product, workflow, legal, academic, or internet-native terms, prefer this pattern on first mention:

中文主译 (English term)

After first mention, use the Chinese term consistently unless the English term is the normal interface label, command, code token, API name, file name, brand, or product feature.

Examples:

• AI Agent -> AI 智能体 (AI Agent); for coding contexts, 代码编辑类 AI 智能体 (AI Agent) is acceptable when the scope needs to be explicit.
• diff -> 差异对比 (diff) or 代码差异 (diff), then use 差异对比 or 代码差异 consistently.
• pull request -> 合并请求 (pull request), then use 合并请求 consistently.
• thread -> 线程 (thread) only when the product metaphor matters; otherwise use 会话 or 工作线程 according to context.
• side panel -> 侧边面板 (side panel), then use 侧边面板.

For new or uncertain terms:

• Prefer a clear Chinese explanation plus the English term in parentheses at first appearance.
• Keep the English term alone only when translating it would harm recognition, such as commands, literal UI labels, protocol names, library names, model names, file extensions, or source text that functions as code.
• Do not invent phonetic translations.
• Do not mix several Chinese translations for the same English term in one document unless the source clearly uses different senses.

For proper nouns:

• Use widely accepted Chinese translations when available.
• Otherwise keep the original English name.
• Preserve official capitalization for brands, products, APIs, commands, and UI labels.

Chunking

For long documents, process one source block at a time. A good block is roughly 1000-2000 English words or an equivalent amount of dense text. If the user provides a much longer text, suggest chunking unless they explicitly ask for a full-document pass.

Optional Theory

Load references/theory.md only when the user asks for the theoretical basis, prompt design rationale, or why this workflow differs from ordinary translation prompts.