Simplified Chinese translation exists in a fork, plus a general translation call

[SysAdminDoc]

CallShield currently ships English only, all 1,243 strings of it. But while looking through forks I found that @wj-on-git has already done a complete Simplified Chinese localization: proper values-zh-rCN resources for strings and plurals, about 1,400 lines of translation work.

@wj-on-git, would you open a PR with the values-zh-rCN resource files? I'd take just the resource additions, without the compiled release changes from your branch, so the diff stays clean and your translation ships in the next official release with your name on the commit. If you'd rather not deal with the PR mechanics, tell me here and I'll cherry-pick the resource files with your authorship preserved.

And this issue can stay open as the general translation thread: if you speak another language and want CallShield in it, comment here and claim it. app/src/main/res/values/strings.xml is the source of truth. Partial translations are fine, the call screening and blocking screens matter most, the settings backwaters can come later.

[SysAdminDoc]

Two things have changed on this side that make a translation PR easier to land, plus a review of the zh-rCN work in the fork.

I reviewed the translation rather than just eyeballing it. @wj-on-git, it holds up well: 1071 of 1103 strings (97.1%), all 30 plurals present and correct, and — the part that actually matters — zero format-specifier errors. Not one %1$s or %d lost, reordered into the wrong arity, or changed type. That is the failure mode that throws at the moment a string is displayed, and on this app that can mean the call-screening notification on a device in a language I cannot read, so it is the thing I was most worried about. Nothing to fix there.

There is now a checker so nobody has to take my word for it. docs/TRANSLATING.md covers the resource layout and the priority order for partial translations, and scripts/check_translations.py reports coverage and fails on format-specifier drift, missing plural categories, and one thing that is very easy to miss:

python scripts/check_translations.py --dir path/to/values-zh-rCN

The easy-to-miss one: a locale also has to be listed in res/xml/locales_config.xml (as zh-CN, BCP-47, not the values-zh-rCN directory form). Without that line the translation ships but never appears in Android's per-app language picker — it only shows up for users whose entire device is set to that language.

One heads-up before you regenerate. v1.7.29 removed 145 unused strings, 70 of them dead accessibility labels. That is 145 fewer strings to translate, but it does mean the current fork copy has ~146 keys that no longer exist upstream. They are harmless — Android ignores unknown names — but the checker will list them, and dropping them keeps the diff honest.

The offer stands unchanged: open a PR with just the values-zh-rCN resources and the locales_config.xml line, and it ships in the next release with your commits and your authorship. If you would rather not deal with the PR mechanics, say so here and I will cherry-pick it with your authorship preserved — I would just rather you got the commit.

And this stays the general translation thread. app/src/main/res/values/strings.xml is the source of truth, now 1,103 strings. Comment here to claim a language; partial translations are genuinely welcome, since Android falls back to English per string.