fix(i18n): refine Traditional Chinese interface copy - #5191
Open
AcerYue0 wants to merge 1 commit into
Open
Conversation
Generated-by: Codex
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refine Traditional Chinese interface copy across Desktop, shared UI, and the TUI. Fix literal translations and remaining Simplified Chinese, clarify message-delivery and Host-control wording, and align credentials, archive, connection, and application terminology.
Examples:
開啟或關閉工作欄的面→開啟或關閉工作欄面板符合不到任何人→無法對應到任何使用者憑證檢查已透過→憑證檢查已通過视觉→視覺Update existing render/copy expectations. Catalog keys, interpolation expressions, executable logic, English, and Simplified Chinese are unchanged.
Verification
npm run build,npm run typecheck,npm run lint,npm run format:check.git diff --check.Windows pre-commit encountered
spawnSync biome.cmd EINVAL. Ran Biome check on all 23 staged files, the ASF header check, protocol epoch guard, and staged whitespace check directly; all passed before bypassing that hook for the commit.AI use
Tool(s) and scope: Codex reviewed and edited zh-TW copy, updated existing expectations, and ran validation.
Checklist
Does this PR entail a change in behavior?