mirror of
https://github.com/langgenius/dify-docs.git
synced 2026-07-22 20:36:31 -04:00
Riskey
d95f83ca4d
* feat: retire the auto-translation pipeline
* fix: drop the Dify-API translator and align the navigation guideline
* fix: remove unused pipeline-era config and the translation A/B test framework
* fix: retire remaining pipeline references in glossary, env-vars skill, termbase tool
(cherry picked from commit 267089b359)
Translation Rules and Utilities
Chinese and Japanese documentation is translated alongside each English change — by the docs team and contributors alike, typically with AI-agent assistance following the rules in this directory.
What lives here
| File | Purpose |
|---|---|
formatting-zh.md |
Chinese formatting and localization rules — read before writing any zh content |
formatting-ja.md |
Japanese formatting and localization rules — read before writing any ja content |
termbase_i18n.md |
Terminology database (en/zh/ja) — derived from writing-guides/glossary.md |
derive-termbase.py |
Regenerates the termbase from the glossary; --check verifies sync (used by CI) |
json_formatter.py |
Format-preserving JSON writer for docs.json edits (keeps diffs clean) |
openapi/ |
OpenAPI spec translation utilities: extract translatable fields to markdown, rehydrate translated values back into the JSON |
Translation workflow
- Make the English change.
- Update the zh and ja counterparts in the same pass: read
formatting-zh.md/formatting-ja.mdandwriting-guides/glossary.mdfirst; check codebase i18n strings for UI labels; keep the translation Note at the top of zh/ja pages. - If
docs.jsonstructure changed, mirror the change in the zh and ja navigation sections.