From: "taozuhong at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/30761] zh-Hans: new locale
Date: Tue, 15 Aug 2023 02:03:59 +0000 [thread overview]
Message-ID: <bug-30761-716-xsejiqN9MT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30761-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30761
--- Comment #1 from taozuhong <taozuhong at hotmail dot com> ---
Chinese has two scripts/variants: Simplified Chinese and Traditional Chinese,
and the two variants are supported in different countries:
Simplified: zh-CN (Mainland), zh-SG (Singapore), zh-MY (Malaysia), zh-ID
(Indonesia)
Traditional: zh-TW (Taiwan), zh-HK (Hong Kong), zh-MO (Macau) 、....
Question
The locales in used can't cover all Chinese users, especial the users outside
the mainland of China, Hong Kong and Taiwan; the App developers will cost more
time to support them.
Chinese support solution
Since Windows Vista and later, RFC 4646 has been chosen as the locale tag, W3C
also support them, the language identification format is:
<Language>-<Script>-<Region>
The corresponding language codes are as follows:
Simplified: zh-Hans-CN / zh-Hans-SG / zh-Hans-MY / zh-Hans-ID / ...
Traditional: zh-Hant-CN / zh-Hant-HK / zh-Hant-TW / zh-Hant-MO / ...
if GLibc could support Chinese language encoding: zh-Hans/zh-Hant, Chinese
translation will cover all of Chinese users, and just maintain two po files.
To simplify and improve the Chinese support, please support the Chinese
language encoding zh-Hans/zh-Hant.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-15 2:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 1:55 [Bug localedata/30761] New: " taozuhong at hotmail dot com
2023-08-15 1:56 ` [Bug localedata/30761] " taozuhong at hotmail dot com
2023-08-15 2:03 ` taozuhong at hotmail dot com [this message]
2023-08-15 9:43 ` fweimer at redhat dot com
2023-08-15 9:47 ` saihaze at outlook dot com
2023-08-15 9:54 ` fweimer at redhat dot com
2023-08-15 11:27 ` saihaze at outlook dot com
2023-08-16 0:33 ` taozuhong at hotmail dot com
2023-08-21 8:43 ` fweimer at redhat dot com
2023-08-21 8:46 ` fweimer at redhat dot com
2023-08-22 1:54 ` taozuhong at hotmail dot com
2023-08-22 2:14 ` bluebat at member dot fsf.org
2023-08-22 2:17 ` saihaze at outlook dot com
2023-08-22 2:33 ` taozuhong at hotmail dot com
2023-08-22 2:38 ` saihaze at outlook dot com
2023-08-22 2:53 ` taozuhong at hotmail dot com
2023-08-26 13:42 ` taozuhong at hotmail dot com
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=bug-30761-716-xsejiqN9MT@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@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).