i18n: complete the zh-rCN translation and align its terminology - #761
Open
zyl6932 wants to merge 1 commit into
Open
i18n: complete the zh-rCN translation and align its terminology#761zyl6932 wants to merge 1 commit into
zyl6932 wants to merge 1 commit into
Conversation
The Simplified Chinese file covered 210 of the 344 strings and predated the heart-rate, recorder, BLE-settings and permissions screens entirely. It now covers all 342 translatable ones (app_name and flavor are marked translatable="false"). 62 existing entries were also reworded to match Apple's own Simplified Chinese terminology for the features they name — 听音模式 for noise control, 通透模式 for transparency, 自适应 for adaptive, 对话感知 for conversational awareness — so the app reads the way the AirPods settings on an iPhone do instead of being translated literally from the English. Verified with aapt2 compile. Format specifiers were checked against the default strings: every %d / %s in a translation matches the one in the English string it stands in for. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Member
I'm not entirely convinced that a model knows what the exact translations are used by Apple. It'd be great if someone, preferably if someone who can read CN, compare this to xOS. I should've taken care of this in the first place, but I felt like having some translations is better than having no translations at all. |
After reviewing commits, the iOS terminology looks mostly correct. Some of the descriptions are worded a little differently, but the meaning is still accurate, and I’ve left review comments on those. For translations that aren’t iOS-specific, I’d trust Claude Opus 5 more. |
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.
What this does
values-zh-rCNcovered 210 of the 344 strings and predated the heart-rate, recorder, BLE-settings and permissions screens entirely — those pages rendered in English on a Chinese device. This fills it in to 342 of 342 translatable strings (app_nameandflavoraretranslatable="false").Breakdown of the diff:
Terminology
The reworded 62 follow Apple's own Simplified Chinese wording for the features they name, rather than a literal translation of the English:
The intent is that someone who has used AirPods with an iPhone in Chinese finds the same words here.
Verification
aapt2 compileon the file: passes.values/strings.xml— every%d/%sin a translation matches the English string it stands in for.Not verified: how each string looks in its actual layout. A few of the longer new ones (
hrm_alert_warning,contact_github_supporting_text) may want a second look for line wrapping on narrow screens.AI disclosure
The translations and the merge were produced by Claude Opus 5 via Claude Code; the commit carries a
Co-Authored-By: Claude Opus 5trailer. I reviewed the terminology choices — the Apple wording above is what I asked for, and I use the app in Chinese daily on my own device. The mechanical parts (key-set diffing against the newvalues/strings.xml, specifier checking,aapt2validation) were done by the model with tooling rather than by eye.