governance

How leji.org is translated

leji.org is written in English and translated language by language. This page records what governs where two versions differ, how a translation is made, which references its terminology follows, and how to report a mistake.

English is the page of record

Every page is written in English first. A translated page is a translation of that page and says so under its title, and where the two differ the English text governs. The specification's translations are informative: the normative text is the English on the frozen 1.0 line, and each translated specification page carries a banner saying so.

How a translation is made

Pages are drafted with an agent-assisted workflow and then approved page by page before they ship. Two independent reviewing engines, neither of which drafted the page, check fidelity to the English, terminology against the language's glossary, and fluency, and the page ships only when both agree.

Terminology

Each language keeps a glossary of the terms Leji uses. Where a term already has an established rendering in a well-known open-source project's human translation, the glossary follows it or records a reasoned exception. Those references are aids, never sources. The list below is kept current as translations of those projects appear and disappear.

Simplified Chinese

• MDN Web Docs (zh-CN)
• Kubernetes docs (zh-cn)
• Pro Git (zh)
• GitHub Docs (zh)
• Python 3 docs (zh-cn)
• Vue.js (zh)
• Vite (zh)
• React (zh-hans)
• TypeScript (zh)
• Keep a Changelog (zh-CN)
• Semantic Versioning (zh-CN)
• Hugging Face Agents Course (zh-CN)

Japanese

• Pro Git (ja)
• GitHub Docs (ja)
• Kubernetes docs and glossary (ja)
• MDN Web Docs (ja)
• React (ja)
• Vue (ja)
• Python docs (ja)
• Python Packaging User Guide (ja)
• WCAG 2.1 (ja, WAIC)
• W3C spec common content (ja)
• W3C (ja)
• Keep a Changelog (ja)
• Semantic Versioning (ja)
• Vite (ja)
• Rails Guides (ja)
• OpenStack Security Guide (ja)

Brazilian Portuguese

• Pro Git (pt-br)
• GitHub Docs (pt)
• Kubernetes docs (pt-br)
• Python docs (pt-br)
• MDN Web Docs (pt-BR)
• W3C WCAG 2.0 authorized translation (pt-br)
• Django docs (pt-br)
• React docs (pt-br)
• Astro docs (pt-br)
• Keep a Changelog (pt-BR)
• TypeScript site (pt)
• Vue docs (pt)

Spanish

• Pro Git (es)
• Git's Spanish localization (po/es.po)
• Kubernetes docs and glossary (es)
• MDN Web Docs (es)
• Python docs (es)
• React docs (es)
• Keep a Changelog (es)
• Semantic Versioning (es)
• Conventional Commits (es)
• Open Source Guides (es)
• GitHub Docs (es)
• Astro docs (es)

Vietnamese

• Git's Vietnamese localization (po/vi.po)
• Kubernetes docs and glossary (vi)
• Semantic Versioning 2.0.0 (vi)
• Vue.js docs (vi, Vue 2)
• The Twelve-Factor App (vi)
• Contributor Covenant 2.1 (vi)
• GNOME GTK localization (po/vi.po)
• Vietnamese national-standard drafts (standards-document vocabulary)
• Vietnamese Wikipedia (secondary)

Staying current

Every translated page records which revision of its English source it follows. A check on every build fails it if any translation has fallen behind its source, so a published translation is never older than the English it translates. The revision is recorded, not displayed.

Reporting a mistake

Every translated page carries two links under its title: one opens an issue with the language and the page already filled in, the other opens the page's own source file for a pull request. The one-page specification view is the exception: it is composed from several documents rather than one, so its issue link sits in the banner at the top and an edit link sits beside each document heading. A correction is reviewed like any other change and lands with the next release.

What is not translated

Command names, flags, paths, JSON keys, and code samples stay in English; the comments inside a code sample are translated. The JSON Schema files themselves and the raw markdown routes stay English.