From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/30761] zh-Hans: new locale
Date: Mon, 21 Aug 2023 08:46:44 +0000 [thread overview]
Message-ID: <bug-30761-716-b7OdXtsHVN@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 #8 from Florian Weimer <fweimer at redhat dot com> ---
This part does not make sense to me, sorry:
“
the most user of zh-Hans/zh-Hant are Chinese, for convenient the locale still
use CNY as the currency symbol.
”
What's the difference to the existing zh_CN and zh_HK locales? Just the name?
As I already said, we are not going to adopt the RFC 5646 scheme. The glibc
convention is actually a POSIX convention and widely used. I do not know why
the IETF standardized a completely new scheme; I assume they never intended to
apply it to locale names.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-21 8:46 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 [this message]
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-b7OdXtsHVN@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).