Skip to content

Add Traditional Chinese (zh-cht) translation - #131

Open
naruko-hstk wants to merge 2 commits into
Ylianst:masterfrom
naruko-hstk:feature/TraditionalChineseTranslation
Open

naruko-hstk wants to merge 2 commits into
Ylianst:masterfrom
naruko-hstk:feature/TraditionalChineseTranslation

Conversation

@naruko-hstk

@naruko-hstk naruko-hstk commented Sep 29, 2026 •

Copy link
Copy Markdown

MeshCommander ships a Simplified Chinese build but no Traditional Chinese one, so users in Taiwan, Hong Kong and Macau have to fall back to English or Simplified Chinese.

This adds a zh-cht language, the same code MeshCentral already uses for Traditional Chinese:

  • translate/translate.json and translate/translate01.json: a zh-cht field next to every existing zh-chs string (1535 and 1527 strings respectively).
  • index_zh-cht.html: the generated page, with <html lang="zh-cht">.

Terminology follows Taiwanese IT conventions rather than a plain character-level conversion — 網路, 伺服器, 檔案, 憑證, 解析度, 滑鼠, 記憶體, 韌體, and so on.

The language submenu in index.html is left untouched, since it does not list every shipped language today (Korean is already absent) and changing it would require regenerating all other localized pages.

@naruko-hstk
naruko-hstk force-pushed the feature/TraditionalChineseTranslation branch from 2302561 to 4b0c87c Compare September 29, 2026 18:02
Add a zh-cht field next to every existing zh-chs string in translate.json
and translate01.json, using Taiwanese IT terminology conventions rather
than a plain character-level conversion. The zh-cht code matches the one
already used by MeshCentral's translation files.
Generate index_zh-cht.html from the zh-cht strings in translate.json and
set the html lang attribute to zh-cht.
@naruko-hstk
naruko-hstk force-pushed the feature/TraditionalChineseTranslation branch from 4b0c87c to c376916 Compare September 29, 2026 18:08
@naruko-hstk naruko-hstk changed the title Add Traditional Chinese (zh-chz) translation Add Traditional Chinese (zh-cht) translation Sep 29, 2026
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