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, 22 Aug 2023 02:53:12 +0000 [thread overview]
Message-ID: <bug-30761-716-vk3ux5rJnL@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 #14 from taozuhong <taozuhong at hotmail dot com> ---
> What's the difference to the existing zh_CN and zh_HK locales? Just the name?
Let's make it simple ASAP:
zh_CN = Simplified Chinese + China mainland
zh_HK = Traditional Chinese + China Hong Kong
zh_TW = Traditional Chinese + Chinese Taiwan
zh_MO = Traditional Chinese + China Macau
zh_Hans = (zh_CN + zh_HK + zh_TW + zh_MO + zh_SG + Simplified Chinese + Others
if want Simplified Chinese)
zh_Hant = (zh_CN + zh_HK + zh_TW + zh_MO + zh_SG + Traditional Chinese + Others
if want Traditional Chinese)
the current locale could map to zh_Hans/zh_Hant:
zh_CN = zh_Hans_CN
cmn_CN = zh_Hans_CN
wuu_CN = zh_Hans_CN
zh_HK = zh_Hant_HK
cmn_HK = zh_Hant_HK
yue_HK = zh_Hant_HK
zh_TW = zh_Hant_TW
cmn-TW = zh_Hant_TW
cmn_TW = zh_Hant_TW
nan_TW = zh_Hant_TW
hak_TW = zh_Hant_TW
lzh_TW = zh_Hant_TW
yue_TW = zh_Hant_TW
So it we keep use zh_CN/zh_HK locale names scheme, then we must add the follow
locale names:
Simplified Chinese
cmn: zh_CN(China mainland), zh-SG (Singapore), zh-MY (Malaysia), zh-ID
(Indonesia), ......
wuu: wuu_CN(China mainland)
yue: maybe exist
nan: maybe exist
hak: maybe exist
lzh: maybe exist
Traditional Chinese
cmn: zh_TW (Chinese Taiwan), zh_HK (China Hong Kong), zh_MO (China Macau),
......
yue: yue_HK(China Hong Kong)
nan: nan_TW(Chinese Taiwan)
hak: hak_TW(Chinese Taiwan)
lzh: lzh_TW(Chinese Taiwan)
yue: yue_TW(Chinese Taiwan)
While you are facing the choices, which one will be choiced?
zh_Hans/zh_Hant VS
zh_CN/zh_HK/zh_TW/zh_SG/zh_MY/zh_ID/zh_MO/yue_HK/nan_TW/hzk_TW/wuu_CN/....
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-22 2:53 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
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 [this message]
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-vk3ux5rJnL@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).