[GH-ISSUE #1017] [Feature]: Add Traditional Chinese (zh-TW) locale and fill missing zh-CN keys #714

New issue

Closed

opened 2026-05-06 12:32:15 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 12:32:15 +02:00

Owner

Originally created by @Minidoracat on GitHub (Apr 18, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1017

Originally assigned to: @Minidoracat on GitHub.

Problem or Use Case

Traditional Chinese users have no native locale — BamBuddy currently ships 7 locales (en, de, fr, it, ja, pt-BR, zh-CN). Users in Taiwan / Hong Kong / Macau who prefer 繁體中文 fall back to English.
zh-CN drifts from en.ts by ~96 keys (line count: zh-CN = 4982 vs en = 5078). Features added since the last locale sync (#627) have only been translated into a subset of locales, so simplified-Chinese users currently see English fallbacks in parts of the UI.

Proposed Solution

Open a PR that:

Adds frontend/src/i18n/locales/zh-TW.ts with the full key set (Traditional Chinese).
Syncs zh-CN.ts against en.ts so every key has a Simplified Chinese translation.
Registers zh-TW in frontend/src/i18n/index.ts and the language picker.
Ensures CI's locale-parity test passes for all 8 locales.

Happy to own the implementation end-to-end.

Alternatives Considered

Traditional-Chinese users using zh-CN as a stopgap: character and terminology differences (你 / 妳, 个 / 個, 体 / 體, program vs. 程式 / 程序, video vs. 影片 / 视频) make it read awkwardly.
Auto-converting zh-CN → zh-TW at runtime: lossy, skips real terminology choices that a human translator should make.

Feature Category

UI/UX

Priority

Would improve my workflow

Contribution

I would be willing to help implement this feature

Checklist

I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @Minidoracat on GitHub (Apr 18, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1017 Originally assigned to: @Minidoracat on GitHub. ### Problem or Use Case - **Traditional Chinese users have no native locale** — BamBuddy currently ships 7 locales (en, de, fr, it, ja, pt-BR, zh-CN). Users in Taiwan / Hong Kong / Macau who prefer 繁體中文 fall back to English. - **`zh-CN` drifts from `en.ts` by ~96 keys** (line count: `zh-CN = 4982` vs `en = 5078`). Features added since the last locale sync (#627) have only been translated into a subset of locales, so simplified-Chinese users currently see English fallbacks in parts of the UI. ### Proposed Solution Open a PR that: 1. Adds `frontend/src/i18n/locales/zh-TW.ts` with the full key set (Traditional Chinese). 2. Syncs `zh-CN.ts` against `en.ts` so every key has a Simplified Chinese translation. 3. Registers `zh-TW` in `frontend/src/i18n/index.ts` and the language picker. 4. Ensures CI's locale-parity test passes for all 8 locales. Happy to own the implementation end-to-end. ### Alternatives Considered - Traditional-Chinese users using `zh-CN` as a stopgap: character and terminology differences (你 / 妳, 个 / 個, 体 / 體, program vs. 程式 / 程序, video vs. 影片 / 视频) make it read awkwardly. - Auto-converting `zh-CN` → `zh-TW` at runtime: lossy, skips real terminology choices that a human translator should make. ### Feature Category UI/UX ### Priority Would improve my workflow ### Contribution - [x] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested