Skip to content

i18n: sync zh_CN catalogs to the production build's canonical versions#265

Open
sanchuanhehe wants to merge 1 commit into
theopensourceway:mainfrom
sanchuanhehe:chore/sync-zh-cn-locales-from-production
Open

i18n: sync zh_CN catalogs to the production build's canonical versions#265
sanchuanhehe wants to merge 1 commit into
theopensourceway:mainfrom
sanchuanhehe:chore/sync-zh-cn-locales-from-production

Conversation

@sanchuanhehe

Copy link
Copy Markdown
Member

Makes the editorial repo the single home for the zh_CN translation catalogs.

Why

The translation catalogs are maintained by the production build, but a copy was also committed here in #261. Since then the production-side catalogs received fixes (footnotes, cross-reference paths, redirected URLs from the recent build remediation) and the copy here drifted out of date and unused.

CONTRIBUTING.md / README.md in the production repo already describe guidebook/locales/ as the catalog location, so this aligns the actual files with the documented design.

What

  • Sync locales/zh_CN/LC_MESSAGES/*.po to the current, build-consistent versions (12 files updated).
  • Ignore compiled *.mo artifacts (the production Sphinx build compiles catalogs in place).

Companion change

A production PR points locale_dirs at this submodule's locales/ and removes the duplicate copy there, so translations live only here and production consumes them through the submodule. Verified locally: English + zh_CN build with 0 warnings and the catalog-freshness check is idempotent against these files.

Refs the i18n infrastructure discussion #260.

The zh_CN translation catalogs are maintained by the production build and had
drifted from the copy committed here in theopensourceway#261. Sync them to the current,
build-consistent versions (footnote/cross-reference/redirect fixes from the
recent build remediation) and ignore compiled *.mo artifacts.

This makes the editorial repo the single home for translation catalogs; the
production repo will consume them via the submodule.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant