From: "taozuhong at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/30761] zh-Hans: new locale
Date: Wed, 16 Aug 2023 00:33:20 +0000 [thread overview]
Message-ID: <bug-30761-716-4ao80o3QgO@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 #6 from taozuhong <taozuhong at hotmail dot com> ---
(In reply to Florian Weimer from comment #2)
> We are not going to adapt RFC 4646 syntax. The present syntax is too widely
> used for it to be changed. A locale contains more than just a language
> setting, so naming locales after languages would be somewhat misleading
> anyway.
>
> We can add country-agnostic Chinese language locales, but the proposed
> zh-Hans locale still CNY as the currency symbol and other references to
> mainland China. See the syr locale for a recently added locale that is
> expected to be country-agnostic.
>
> Under our present scheme, these new locales should probably called zh@Hans
> and zh@Hant. We already have uses of the cmn language tag, maybe that's more
> appropriate in context?
Thanks for your feedback awfully.
https:www.rfc-editor.org/rfc/rfc5646
https:www.unicode.org/reports/tr35/
based on the specification RFC 5646 / Unicode TR35, these specs fully
considered the compatibility of the Glibc language present scheme, the language
tag format gave us a way to mixed them together, the specification thinks:
---------------------------------------------------------------------------
| zh_Hans | Chinese, in simplified script (=zh, zh-Hans, zh-CN, zh-Hans-CN) |
---------------------------------------------------------------------------
| zh_Hant | Chinese, in traditional script |
---------------------------------------------------------------------------
and the language cmn should mapped to zh-Hant, cmn-TW mapped to zh-Hant-TW.
the most user of zh-Hans/zh-Hant are Chinese, for convenient the locale still
use CNY as the currency symbol.
and we can fork new locale like zh-Hans-MY/zh-Hans-ID if needed.
for GLibc long live, the language present scheme should follow specs, keep
origins for compatibility, new locales use new scheme for future.
so, I insist on using the locale name: zh-Hans / zh-Hant.
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-16 0:33 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 [this message]
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-4ao80o3QgO@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).