Files
deepseek-harness/docs/user/develop/framework/service.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

41 lines
1.5 KiB
YAML

# Bilingual-pair consistency record for service.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/user/develop/framework/service.md
/services-and-dependencies:
en: 03fe9a674163a484
zh: 45374665fa3bb8e3
/services-and-dependencies/what-is-a-service:
en: fb06be7799d75fc0
zh: a59fdde61e557b24
/services-and-dependencies/consume-a-service:
en: 6655ebf5abce2a59
zh: 0c91cac86768d63e
/services-and-dependencies/provide-a-service:
en: ed1d04f41f64b6ce
zh: e0ddcb48bf3207c1
/services-and-dependencies/provide-a-service/extend-service:
en: 3de1c24498e2c62f
zh: 57836dc4fa8d5c9a
/services-and-dependencies/provide-a-service/declare-its-type:
en: fc1a29f46715ade5
zh: b1edb281077df180
/services-and-dependencies/dependency-behavior:
en: 6678917fe40eea55
zh: 6227580b94a50855
/services-and-dependencies/dependency-behavior/required-and-optional-dependencies:
en: 8a98845896146946
zh: 2383ad4ba5d2943d
/services-and-dependencies/dependency-behavior/when-a-service-disappears:
en: 689e4b95dd320122
zh: 674ffba2733ec745
/services-and-dependencies/service-isolation:
en: cc4be89f19cb7615
zh: e00e86a615f59003
/services-and-dependencies/built-in-harness-services:
en: 07eb5bcc03955284
zh: 5eec0f3c6e01c0f9
/services-and-dependencies/next-steps:
en: 1537e6955eb02c62
zh: 6430f34e63cfa533