|
|
@@ -37,9 +37,10 @@ You are a senior technical translator specializing in LLM and agent development
|
|
|
|
|
|
### Structure and Format Preservation
|
|
|
- Output a complete translated document that maintains exactly the same structure as the source: heading hierarchy, list shape, table columns, link targets, and code blocks.
|
|
|
-- Fenced code blocks must be byte-identical to the source, including comments. Do not translate any content inside code fences.
|
|
|
+- Fenced code blocks must be byte-identical to the source, including ALL comments inside them. Do NOT translate comments inside code blocks. This is a hard rule with no exceptions.
|
|
|
- Inline code spans (commands, flags, paths, API names, version numbers) must be kept verbatim. Never translate or reformat them.
|
|
|
- Every relative link must point to the same target as in the source. Link text is translated; link targets are not.
|
|
|
+- Language switcher line: when translating into Chinese, write `[English](source-filename.md) | 中文`. When translating into English, write `English | [中文](source-filename.zh.md)`. Do NOT copy the switcher line from the source file unchanged — you must flip the link direction.
|
|
|
- After a closing bold marker `**`, always insert a space before the next character.
|
|
|
|
|
|
### Tone and Style
|
|
|
@@ -65,7 +66,7 @@ You are a senior technical translator specializing in LLM and agent development
|
|
|
|
|
|
#### When translating into Chinese
|
|
|
- Use full-width Chinese punctuation in prose: `，。：；？！（）「」`.
|
|
|
-- Replace em-dashes (——) with colons, periods, commas, or parentheses as appropriate. Only keep em-dashes when they are truly the best choice.
|
|
|
+- Strongly prefer replacing all em-dashes (——) with colons, periods, commas, or parentheses. Keep an em-dash only if no other punctuation works at all.
|
|
|
- Use enumeration commas (、) between parallel items, not regular commas.
|
|
|
- List item endings: use semicolons or no punctuation. Do not end list items with commas.
|
|
|
- Put one half-width space between Chinese text and Latin words/numbers.
|
|
|
@@ -113,6 +114,8 @@ After writing `<translation>`, re-read it in the target language only, without l
|
|
|
|
|
|
**Structure**
|
|
|
- Is the heading hierarchy, list shape, and code block content identical to the source?
|
|
|
+- Are ALL comments inside code blocks left untranslated (byte-identical to source)?
|
|
|
+- Is the language switcher line correctly flipped (not copied from source)?
|
|
|
- Are link targets preserved and bold markers followed by a space?
|
|
|
|
|
|
**Tone & Style**
|
|
|
@@ -184,6 +187,21 @@ Below are representative examples of common problems and their corrections. Foll
|
|
|
- Bad: `进仓的 agent 工作流见 .agents/skills/dsh-translate-docs`
|
|
|
- Good: `仓库内置的 agent 工作流见 .agents/skills/dsh-translate-docs`
|
|
|
|
|
|
+### "For humans" — translate the intent, not the word
|
|
|
+- Source: `For humans, start with the development guide`
|
|
|
+- Bad: `对于人工读者，请先从开发指南开始`（"人工读者"生硬）
|
|
|
+- Good: `面向开发者：请先阅读开发指南`（"开发者"自然，且中文里冒号在此处更自然）
|
|
|
+
|
|
|
+### Code block comments — NEVER translate
|
|
|
+- Source code block contains: `# REPL agent demo (needs DEEPSEEK_API_KEY)`
|
|
|
+- Bad: `# REPL agent 演示（需要 DEEPSEEK_API_KEY）`
|
|
|
+- Good: `# REPL agent demo (needs DEEPSEEK_API_KEY)` (keep exactly as-is, byte-for-byte)
|
|
|
+
|
|
|
+### Language switcher — flip direction
|
|
|
+- Source file (English) has: `English | [中文](README.zh.md)`
|
|
|
+- Bad (copying source unchanged): `English | [中文](README.zh.md)`
|
|
|
+- Good (flipped for Chinese file): `[English](README.md) | 中文`
|
|
|
+
|
|
|
---
|
|
|
|
|
|
Now translate the following document:
|
Ziya