Use zh_CN/zh_TW/zh_HK/zh_SG instead of zh_Hans/zh_Hant for Chinese language code

[lumingzh]

Describe the problem

The apps using zh_Hans from weblate can't display Chinese UI on GNOME, not test other desktop environment. Collision changed from zh_Hans to zh_CN and works normal now.

Describe the solution you'd like

Use zh_CN/zh_TW/zh_HK/zh_SG for Chinese.

Describe alternatives you've considered

No response

Screenshots

No response

Additional context

OS: Fedora Silverblue 35
DE: Gnome Shell 41
APP: Installed from flathub as flatpak

[nijel]

There is no one solution that would fit all use cases. That's why there is Language code style, see Adding new translations for more info. What might make sense is to add another option there that would cover POSIX style identifiers with legacy codes for Chinese.

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

[sonnyp]

@nijel is this something "Linux" could fix on their side? Like fallback to zh_CN for zh_Hans and vice versa ?

Where would that be - glibc?

[nijel]

This is just about naming of translation files created in Weblate. Once the file exists, Weblate doesn't care whether it is called zh_CN or zh_Hans.

[sonnyp]

I understand. I meant fixing on a higher level – where Weblate is not involved.

I guess I'm looking for the right place to file a feature request so that this doesn't happen in the first place if the Linux stack understands that zh_CN = zh_Hans and so on.

[nijel]

Ah, that might be indeed in glibc.

[sonnyp]

For the record and in case someone is interested in picking this up, Fedora already requested this from glibc and the developers basically said "yes but tricky”, which I understand as "ok if someone is willing to put the effort into it".

https://sourceware.org/legacy-ml/libc-alpha/2019-10/msg00358.html