Files
deepseek-harness/docs/subsystems/feedback.i18n.yaml
T
Turtle e7def469e1 feat(i18n): key translation pairing records by heading section (#5036)
* feat(i18n): key translation pairing records by heading section

Replace the whole-file blob hashes in *.i18n.yaml with one entry per
heading section that still holds language-specific content, keyed by the
English heading-slug path. Blocks identical across the pair (generated
table rows, code blocks, shared regions) stay out of the hash, so edits to
different sections and identical regenerations merge with Git's default
text merge, including on GitHub.

Remove the dsh-translation-pairing merge driver, its resolver command and
installer wiring; gen-translation-brief recovers last-confirmed text from
commit history. Migrate all active records, archive the superseded Agent
Note, and record the replayed conflict reduction in the new one.

* test(i18n): refresh translation prompt snapshot for the terminology note

* feat(i18n): exclude only code blocks and generated regions from pairing records

Replace byte-equality masking with an explicit rule: a record hash skips
fenced code blocks and BEGIN/END GENERATED regions, the two kinds of
content the pairing gate already requires to be identical on both sides.

Move generated data into regions written into both pages:
gen-config-catalog renders both languages and the record with per-package
regions labelled by code identifiers; gen-module-graph keeps its table in a
region; gen-doc-graphs splices the event matrix regions into the Chinese
page. Add a generic region splice beside the region grammar.
2026-09-23 22:32:06 +08:00

29 lines
1008 B
YAML

# Bilingual-pair consistency record for feedback.md (docs/i18n/README.md): per heading
# section, a hash of its English and Chinese blocks outside code blocks and generated regions.
# After editing either side, bring the other along and re-record with:
# pnpm run verify-translation-pairing --write docs/subsystems/feedback.md
/message-feedback:
en: 707e1e2e0183cf62
zh: f47848008069df70
/message-feedback/public-types:
en: 514e3a869e355a86
zh: 4b6f416f8ff3847f
/message-feedback/session-feedback-types:
en: dacd5384864a040f
zh: 1912000a5d76c277
/message-feedback/data-and-concurrency:
en: 12231161d9001f8b
zh: 2f1aa0cf78f67643
/message-feedback/target-and-lifecycle-authority:
en: 5f27c79e933bec0a
zh: e9211a24f97e730f
/message-feedback/persistence-and-remote-contract:
en: d30ec3f187959494
zh: 3a32859637c492ce
/message-feedback/web-surface:
en: 6f60352749185e55
zh: c654a17ec1e17393
/message-feedback/boundaries-and-limitations:
en: 6e258de40224234e
zh: 05a7e181d357d038