Repository navigation
Conversation
…ect, and file viewer
Contributor
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
Contributor
|
The following comment was made by an LLM, it may be inaccurate: |
Resolve zh.ts/zht.ts conflicts after the upstream GUI refactor: keep added keys that still exist in en.ts and drop the ones removed upstream, remove orphan keys, and add the 67 keys that became newly missing in both locales so zh/zht match en (986 keys, missing=0, orphan=0).
6 tasks
This branch has not been deployed
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.
Issue for this PR
Closes #53858
Supersedes #52039 (auto-closed by the issue-compliance workflow before its body was converted to the template structure; preserved there for history).
Type of change
What does this PR do?
Restores full zh/zht parity with
en.ts(986/986 keys, missing=0, extra=0), so Chinese locales stop falling back to English.History of this branch: the original commit filled the 93-key gap that #52039 reported (pairing page, provider-connect wizard, file viewer, plus smaller
session.*/settings.*gaps). Since then upstream restructured the dictionaries (GUI features moved into built-in extensions, ~677 lines removed per file), so the branch was merged with current v2 and the gap recomputed:session.location.*keys upstream accidentally dropped from zh/zht while keeping them inen.ts).Original scope detail:
settings.pairing.*,pair.*,command.server.pair,server.connect.link.expired) — the entire Settings → Pairing screen rendered in English; reported in [BUG]: zh/zht locale dictionaries missing 93 keys present in en (pairing, provider connect, file viewer) #52039.provider.connect.*keys: Console/device-code, OAuth, remote server, API-key flows).file.view.preview/source/openInBrowser, …), plus smallersession.*/settings.*/home.*/command.*/common.*gaps.Translation notes: placeholders (
{{...}}) and$OPENCODE_*env vars untouched; terminology followspackages/app/AGENTS.md§Localization (提供商/会话/工作树/…); zht uses Taiwanese vocabulary (連線/設定/檔案) and was scanned for simplified-character leakage;file.view.fontSampleintentionally keeps the English pangram since it previews Latin glyph coverage.How did you verify your code works?
{{...}}matchen.tsexactly (0 mismatches)bunx prettier --checkon both files → cleanpackages/appfull suite → 740 pass / 0 fail; browser suite → 167 pass / 0 failScreenshots / recordings
Text-only locale additions; the Pairing page (previously English) now renders in Chinese. No layout change.
Checklist