Add native Vietnamese localization support - #1247
Conversation
|
Codex review: needs maintainer review before merge. Reviewed June 7, 2026, 6:34 AM ET / 10:34 UTC. Summary Reproducibility: not applicable. this is a feature PR rather than a bug report. The diff and screenshots provide a high-confidence verification path for the new visible Vietnamese UI behavior. Review metrics: 3 noteworthy metrics.
Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Rank-up moves:
Risk before merge
Maintainer options:
Next step before merge
Security Review detailsBest possible solution: Land the focused Vietnamese localization after normal checks and maintainer acceptance, keeping the new catalog and parity test while letting release-owned notes be adjusted by the release flow if needed. Do we have a high-confidence way to reproduce the issue? Not applicable; this is a feature PR rather than a bug report. The diff and screenshots provide a high-confidence verification path for the new visible Vietnamese UI behavior. Is this the best way to solve the issue? Yes; the PR follows the existing localization pattern by adding an AGENTS.md: found and applied where relevant. Codex review notes: model gpt-5.5, reasoning high; reviewed against 1583d6cc1005. Label changesLabel changes:
Label justifications:
Evidence reviewedWhat I checked:
Likely related people:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. How this review workflow works
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 80b5a37a91
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "30d spend" = "chi tiêu 30 ngày"; | ||
| "Cache read" = "Đọc bộ nhớ đệm"; | ||
| "Claude Admin API 30 day spend trend" = "Claude Quản trị viên API Xu hướng chi tiêu 30 ngày"; | ||
| "OpenRouter API key spend trend" = "OpenRouter <span> class="w0"></span> xu hướng chi tiêu chính"; |
There was a problem hiding this comment.
Escape embedded quotes in the Vietnamese strings file
When the app language is set to Vietnamese, this unescaped class="w0" attribute makes vi.lproj/Localizable.strings invalid; plutil -lint reports a missing semicolon on this line, so Foundation cannot load the table and Vietnamese lookups fall back instead of using the new translations. Escape the embedded quotes or remove the generated HTML fragment so the .strings file parses.
Useful? React with 👍 / 👎.
|
Implemented and polished native Vietnamese localization based on the review feedback. Updated UI screenshots:
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. Re-review progress:
|
80b5a37 to
eef4385
Compare
eef4385 to
7a8ced8
Compare
|
Merged as b442183. Tested:
CI for exact head
Verification images: not applicable; no UI visual change in the maintainer fixup. |





Summary:
vi) as a native app language option.vi.lproj/Localizable.stringsresource file.language_vietnameselabels to the existing language packs so the language picker can display Vietnamese consistently.Validation:
swift test --filter PreferencesPaneSmokeTestsvi.lprojkey parity withen.lproj.