saberongo/public-domain-books-translation/translation-quality-defect-families

译文质量问题族 / Translation Quality Defect Families

Boundary / 边界

Use this skill to turn recurring translation-quality problems into reusable correction knowledge. 使用本 skill，把反复出现或可能系统性复现的译文质量问题，沉淀成可复用的修正规则。

This skill focuses on the translation as a readable book: fidelity, literary force, target-language fluency, terminology, narrative rhythm, reader engagement, and source-supported expression. 本 skill 关注“译文作为一本书”的质量：忠实度、文学性、目标语顺读、术语、叙事节奏、读者吸引力，以及所有有原文依据的表达转换。

Do not use this skill for format-only issues such as EPUB manifest errors, cover policy, release metadata, local-path leaks, or CI failures unless they also expose a translation-quality pattern. 不要把本 skill 用于纯格式问题，例如 EPUB manifest、封面 policy、release metadata、本机路径泄漏或 CI 失败；除非这些问题同时暴露了译文质量模式。

Required Workflow / 必须流程

When a review finds a defect that may recur, do the following before declaring the work closed. 评审发现可能复现的问题后，必须先完成以下步骤，才能宣布关闭。

1. Classify the defect family.

先归纳问题族。

1. Record how it was found: chapter control, random sample, human note, rg scan, glossary scan, source comparison, generated XHTML inspection, or reader feedback.

记录发现方式：章节控制、随机样本、人工意见、rg 扫描、术语扫描、原文对照、生成 XHTML 检查或读者反馈。

1. Define the risk: what reader misunderstanding, fidelity loss, rhythm damage, terminology drift, or unauthorized invention it causes.

定义风险：它会造成什么误读、失真、节奏损伤、术语漂移或擅自加戏。

1. Audit similar cases with the cheapest reliable method first: glossary fields, rg, title maps, source-to-target term lists, chapter controls, or targeted small-context agent review.

先用最低 token 且可靠的方法查同类：术语表字段、rg、标题映射、源语-目标语词表、章节控制，或小上下文 agent 专项复核。

1. Fix confirmed matches and record justified exceptions.

修复确认命中，并记录合理例外。

1. Add or merge a reusable lesson in the register below.

在下方注册表追加或合并可复用经验。 This is mandatory in the same round as the fix: do not postpone skill backfill to a final summary, because later agents will otherwise rediscover the same family. 必须在同一轮修复中完成 skill 回填：不要拖到最终总结，否则后续 agent 会反复重新发现同一问题族。

1. Recheck with the appropriate gate: full-chapter recheck for chapter-stage defects, new-seed stratified random sample for post-EPUB defects, or a targeted family audit for book-wide risks.

用合适门禁复查：章节阶段问题做整章复查，EPUB 后抽检问题用新 seed 复抽，全书风险做问题族专项审计。

Update Discipline / 更新纪律

Do not append repetitive notes blindly. 不要盲目重复追加。

Before adding a new entry, search this file for the family, source-language mechanism, and target-language symptom. If an entry already exists, update that entry with a sharper detection method, better fix pattern, or a concrete example. 新增条目前，先搜索本文件中的问题族、源语机制和目标语症状。已有同族条目时，应合并更新：补更准的发现方法、更好的修复模式或具体例子。

Every entry should stay reusable across books. Book-specific names may appear as examples, but the rule must be phrased as a general lesson. 每个条目都应能跨书复用。可以用具体书名或人名做例子，但规则必须写成通用经验。

Use bilingual Chinese-English wording for new major sections. Chinese may lead when the expected contributor is Chinese. 新增主要段落使用中英文双语。面向中文贡献者时，中文可置前。

Validator Fields / 校验字段

For random spot-check rounds, book-local evidence belongs in reviews/random_spotcheck/round_XXX/fixes/fix_log.md and verification/closure_check.md, but reusable translation-quality lessons must be merged here in the same round. The pass validator checks this through machine-readable fields. 随机抽检轮次中，书内证据写入 reviews/random_spotcheck/round_XXX/fixes/fix_log.md 和 verification/closure_check.md，但可复用译文质量经验必须在同一轮合并回填到本 skill。强校验会通过机器可读字段检查这件事。

When a round found translation-quality defect families, set: 发现译文质量问题族时，必须填写：

defect_family_count: {total_family_count}
translation_quality_defect_family_count: {quality_family_count}
translation_quality_skill_backfill: "UPDATED" # or "MERGED"
translation_quality_skill_backfill_path: "skills/translation-quality-defect-families/SKILL.md"
translation_quality_skill_backfill_summary: "{what was added or merged: finding method, classification, low-token audit, fix pattern, recheck}"

And in closure_check.md: 并在 closure_check.md 写入：

translation_quality_skill_backfill_verified: true

If the round found only format, asset, path, EPUB structure, or other non-translation-quality issues, set translation_quality_defect_family_count: 0, translation_quality_skill_backfill: "NOT_APPLICABLE", and write a concrete translation_quality_skill_backfill_not_applicable_reason. 如果该轮只有格式、资产、路径、EPUB 结构或其他非译文质量问题，应写 translation_quality_defect_family_count: 0、translation_quality_skill_backfill: "NOT_APPLICABLE"，并填写具体的 translation_quality_skill_backfill_not_applicable_reason。

Low-Token Audit Pattern / 低 token 审计模式

• Start with machine-readable evidence: glossary/terms.csv, forbidden renderings, title maps, chapter controls, sample manifests, and review tables.

先用机器可读证据：glossary/terms.csv、禁用正文写法、标题映射、章节控制、抽样 manifest 和评审表。

• Use rg to collect candidates before asking an agent to read prose.

先用 rg 收集候选，再让 agent 阅读片段。

• Give the agent only the candidate passage, nearby source text, relevant glossary rows, and the current family rule.

只给 agent 候选段、邻近原文、相关术语行和当前问题族规则。

• Treat random sampling as discovery, not as the main polishing engine.

随机抽检用于发现盲点，不是主要润色引擎。

• Treat full-chapter review as the main place to catch fidelity, fluency, rhythm, and terminology issues.

忠实度、顺读、节奏和术语问题，主要应在每章全量复检阶段解决。

Defect Family Register / 问题族注册表

High-Impact Literal and Explanatory Opening Prose / 高影响开篇直译腔与解释腔

• Symptom: Author/source prefaces, introductions, openings, first chapters, or other reader-entry passages are accurate but sound stiff, flat, awkward, overly literal, or explanatory in the target language. The prose may use causal bridges such as 原因在于, conditional chains such as 要是只能...就必然, abstract noun stacks, or target-only analytical wording that explains the source instead of becoming a natural book sentence.

症状：原作者/原书序言、导言、开篇、首章或其他读者入口段落意思准确，但目标语读起来不顺口、怪、平、硬、直译感重或解释腔明显。常见表现包括 原因在于 一类因果桥、要是只能...就必然 一类条件链、抽象名词堆叠，或把原意说明出来而不是转成自然书面句。

• Find by: Treat opening files and headings matching preface|introduction|序言|前言|导言|开篇|首章|第一章 as high impact before random sampling. Use scripts/check_literary_style_gate.py --write-report plus targeted scans such as 原因在于|也就不能|就必然|换言之|也就是说|这说明|进行|具有|予以|加以|表达 意思是|原文意思是. These are candidates, not automatic defects; inspect small source-target contexts and prioritize the first pages of the book.

发现方式：在随机抽检前即把文件名/标题匹配 preface|introduction|序言|前言|导言|开篇|首章|第一章 的章节视为高影响区域。运行 scripts/check_literary_style_gate.py --write-report，并用 原因在于|也就不能|就必然|换言之|也就是说|这说明|进行|具有|予以|加以|表达 意思是|原文意思是 等扫描候选。这些只是候选，不是自动错误；必须小上下文对照源文，优先检查全书最前几页。

• Risk: Readers judge the translation before they reach the middle of the book. A weak opening can lose trust even when later chapters are accurate. Treat repeated opening style debt as P2/blocking for final release, not as a harmless P3 comment.

风险：读者会在进入正文前判断译本是否可信。开篇弱，即使后文准确，也会让读者流失。反复出现的开篇文学债务在最终发布前应按 P2/阻塞处理，不应作为无害 P3 建议。

• Fix by: First perform target-language-only rewriting: remove explanatory scaffolding, break source syntax, rebuild cadence, and choose idiomatic target-language verbs and clauses. Then compare against the source to ensure the polish did not add argument, motivation, or tone. For Gibbon-like argumentative prose, preserve balance and antithesis without turning the sentence into modern analysis; for biography or dialogue, preserve voice and character pressure instead of smoothing everything into commentary.

修复方式：先只看目标语重写，删去解释脚手架，打散源语句法，重建节奏，选择自然目标语动词和分句；再回到源文校准，确认润色没有新增论点、动机或语气。吉本式论辩散文要保留均衡和对照，不要改成现代分析说明；传记或对话要保留人物声口和叙述压力，不要全部抹成评论腔。

• Recheck: Final release requires qa/literary_style/literary_style_review.md PASS with target_only_reading_score: 5, read_aloud_awkward_sentence_count: 0, literal_explanatory_style_debt_count: 0, and high-impact sections reviewed. Random review agents must set high_impact_style_debt_count: 0 and style_debt_count: 0 for excellence PASS.

复查：最终发布必须有 qa/literary_style/literary_style_review.md PASS，并记录 target_only_reading_score: 5、read_aloud_awkward_sentence_count: 0、literal_explanatory_style_debt_count: 0，且高影响开篇已复审。随机评审 Agent 若要给优秀 PASS，必须写明 high_impact_style_debt_count: 0 和 style_debt_count: 0。