Skip to content

i18n: complete the zh-rCN translation and align its terminology - #761

Open
zyl6932 wants to merge 1 commit into
librepods-org:android/rewritefrom
zyl6932:pr/i18n-zh-rcn
Open

i18n: complete the zh-rCN translation and align its terminology#761
zyl6932 wants to merge 1 commit into
librepods-org:android/rewritefrom
zyl6932:pr/i18n-zh-rcn

Conversation

@zyl6932

@zyl6932 zyl6932 commented Sep 1, 2026

Copy link
Copy Markdown

What this does

values-zh-rCN covered 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_name and flavor are translatable="false").

Breakdown of the diff:

count
newly translated (had no zh entry) 65
existing entries reworded for terminology 62
existing entries kept as they were 148
entries dropped 0

Terminology

The reworded 62 follow Apple's own Simplified Chinese wording for the features they name, rather than a literal translation of the English:

before after
Noise Control 噪音控制 听音模式
Transparency 透明模式 通透模式
Adaptive 适应性 自适应
Conversational Awareness 对话意识 对话感知
Personalized Volume 个人化音量 个性化音量

The intent is that someone who has used AirPods with an iPhone in Chinese finds the same words here.

Verification

  • aapt2 compile on the file: passes.
  • Format specifiers checked programmatically against values/strings.xml — every %d / %s in a translation matches the English string it stands in for.
  • No unescaped apostrophes, no dropped keys, no empty values.

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 5 trailer. 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 new values/strings.xml, specifier checking, aapt2 validation) were done by the model with tooling rather than by eye.

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>
@kavishdevar

Copy link
Copy Markdown
Member

the Apple wording above is what I asked for

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.

@Augkit

Augkit commented Sep 1, 2026

Copy link
Copy Markdown

@kavishdevar

上面苹果的表述就是我要求的

我并不完全相信模型真的知道苹果用了哪些具体的翻译。如果有人,最好是能读CN的人,能把它和xOS做个比较,那就太好了。

我本该一开始就处理好这件事,但我觉得有翻译总比没有翻译好。

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.

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.

3 participants