From: Mike FABIAN <mfabian@redhat.com>
To: Jean-Baptiste Holcroft <jean-baptiste@holcroft.fr>
Cc: libc-alpha@sourceware.org, libc-locales@sourceware.org
Subject: Re: Language code changes over time: zh_CN -> zh_Hans
Date: Fri, 11 Oct 2019 20:41:00 -0000 [thread overview]
Message-ID: <s9dk19bvwu6.fsf@taka.site> (raw)
In-Reply-To: <9c492c49060a079cf36b28269ea2a981@holcroft.fr> (Jean-Baptiste Holcroft's message of "Thu, 10 Oct 2019 17:22:47 +0200")
Jean-Baptiste Holcroft <jean-baptiste@holcroft.fr> ããã¯ããã¾ãã:
> Hi,
>
> the Fedora community is migrating to the Weblate translation platform.
> This translation platform uses zh_Hans, zh_Hant, zh_Hant_HK by
> default, instead of zh_CN, zh_TW and zh_HK.
Does it have to use these?
This is also weblate:
https://l10n.opensuse.org/projects/yast-network/#languages
https://l10n.opensuse.org/languages/zh_CN/yast-network/
https://l10n.opensuse.org/languages/zh_TW/yast-network/
And it uses zh_CN and zh_TW. So that seems possible with weblate.
I think it would be easier to use zh_CN, zh_TW, zh_SG, zh_HK
in weblate instead changing glibc to accept zh_Hans_CN etc.
If you look into the folders /usr/share/locale/zh_TW and
/usr/share/locale/zh_HK on a linux system, you will find that there are
many translations there. 1020 .mo files in
/usr/share/locale/zh_CN/LC_MESSAGES/ on my Fedora 30 and 977 .mo files
in /usr/share/locale/zh_TW/LC_MESSAGES. And no translations at all in
/usr/share/locale/zh_Hans_CN/LC_MESSAGES/ and
/usr/share/locale/zh_Hant_TW/LC_MESSAGES/. Although these directories
exist, they are empty. So switching to zh_Hans_CN would be quite
a lot of effort:
- changing glibc to accept zh_Hans_CN.UTF-8 (Not sure whether that is
even possible)
- Changing all these packages with the translations.
It might be possible to change gettext: If the locale is zh_CN.UTF-8,
it could look in the zh_CN folder as it does not and if no .mo file
is found there, it could try zh_Hans_CN as well.
But that is also not an easy change.
I think using zh_CN and zh_TW in weblate is easiest and
looking at the above weblate site used by openSUSE, it seems possible.
--
Mike FABIAN <mfabian@redhat.com>
ç¡ç ä¸è¶³ã¯ããä»äºã®æµã ã
next prev parent reply other threads:[~2019-10-11 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 15:22 Jean-Baptiste Holcroft
2019-10-10 16:25 ` Florian Weimer
2019-10-11 20:27 ` Mike FABIAN
2019-10-10 20:53 ` Carlos O'Donell
2019-10-11 20:41 ` Mike FABIAN [this message]
2019-10-12 9:35 ` Jean-Baptiste
2019-10-12 13:52 ` Mike FABIAN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s9dk19bvwu6.fsf@taka.site \
--to=mfabian@redhat.com \
--cc=jean-baptiste@holcroft.fr \
--cc=libc-alpha@sourceware.org \
--cc=libc-locales@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).