Skip to content

i18n(zh_TW): align with Studio built-in en_US and fully refine Taiwanese localization#9

Open
chen21019 wants to merge 1 commit intocloudstack-llc:mainfrom
chen21019:i18n/zh-tw-studio-aligned-20260213
Open

i18n(zh_TW): align with Studio built-in en_US and fully refine Taiwanese localization#9
chen21019 wants to merge 1 commit intocloudstack-llc:mainfrom
chen21019:i18n/zh-tw-studio-aligned-20260213

Conversation

@chen21019
Copy link
Copy Markdown

Summary

This PR performs a full review and refinement of zh_TW.json to:

  1. align translations with Msty''s LLM/chat product context,
  2. use natural Taiwanese terminology,
  3. fix inconsistent, awkward, or misleading wording.

Context

There appears to be a version gap between the public msty-studio-i18n repo and the locale exported from Msty Studio.
This translation work was aligned against the newer Studio built-in en_US.json to avoid missing newer keys/features.

What was improved

  • Replaced terms that do not fit an LLM/AI UI context.
  • Standardized inconsistent wording across similar UI flows/features.
  • Standardized Prompts as "提示詞" (instead of generic/ambiguous alternatives).
  • Standardized Forge-related wording as "創建" (without leaving English terms).
  • Removed uncommon or unnatural phrases and rewrote them for fluent zh-TW UX.
  • Carefully verified template safety and formatting:
    • placeholders: {count}, {modelName}, {progress}, etc.
    • i18n references: @:...
    • plural pipeline forms: singular | plural
    • escaping and JSON validity

Validation

  • JSON parses successfully.
  • Key-path structure remains aligned with source keys.
  • No functional/code changes; translation-only update.

Note for maintainers

If possible, please consider syncing the public en_US.json baseline with the newer Studio built-in version first, so community translations can stay in sync with current app features.

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