Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge commit 'refs/review/pr-312-head' into codex/fix-pr172-review-findings

Browse Source 
# Conflicts:
#	docs/i18n/translation-prompt.md
This commit is contained in:
Tianyi Cui
2026-07-14 22:46:36 +08:00
parent 19504f7e34 3d0ad3db3e
commit 883948d1d5
20 changed files with 479 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/i18n/translation-prompt.md
View File

@@ -60,9 +60,10 @@ You are a senior technical translator specializing in LLM and agent development
- Render RFC 2119 keywords as 必须、禁止、应当、可以 while preserving the source emphasis exactly; plain source text remains plain.
#### When translating into English
- Use concise professional developer English. Replace Chinese topic-comment order, redundant subjects, and politeness padding with idiomatic English without dropping their meaning.
- Use normal half-width English punctuation and spacing. Preserve full-width punctuation only inside verbatim Chinese text.
- Use concise professional developer English. Convert Chinese topic-comment order, implicit subjects, and nominalizations into idiomatic English without dropping their meaning.
- Use normal half-width English punctuation and spacing. Convert enumeration commas (、) to English commas and 「」 quotation marks to English double quotes, except inside verbatim Chinese text.
- Render RFC 2119 keywords as MUST, MUST NOT, SHOULD, and MAY while preserving the source emphasis exactly.
- Use established English engineering idiom rather than literal transliteration (误报 → false positive, 执行红线 → enforcement frontier), consulting the terminology table first.
- Use direct English imperatives for instructions unless the source's politeness carries substantive meaning.
## Terminology