From: "bluebat at member dot fsf.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/17563] cmn_TW: add hanzi collation
Date: Thu, 10 Aug 2017 03:06:00 -0000 [thread overview]
Message-ID: <bug-17563-716-WX4qsfSdJR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17563-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17563
--- Comment #9 from Wei-Lun Chao <bluebat at member dot fsf.org> ---
(In reply to Mike FABIAN from comment #8)
> (In reply to Wei-Lun Chao from comment #7)
> > (In reply to Mike FABIAN from comment #6)
> > > Should the new collation also be used for zh_TW, or only
> > > for cmn_TW.
> > > By the way, what is the difference between zh_TW
> > > and cmn_TW, isn’t both Mandarin?
> >
> > As reasons for bug 15963, those 14 languages have been behind the
> > macro-language "zh" for a long time. Technically zh_TW and cmn_TW are the
> > same, but for fairness, IMHO, the locale zh_TW should be deprecated and
> > replaced with cmn_TW and other chinese locales.
> >
> > Personally I would like to differentiate cmn from zh with this radical
> > patch, which may be followed by similar patches against nan_TW, hak_TW,
> > lzh_TW and yue_HK.
>
> OK.
>
> How to test your patch?
>
> I did this:
>
> Without your patch:
>
> $ echo -e "黄\n木\n機\n期" | LC_ALL=cmn_TW.UTF-8 sort
> 期
> 木
> 機
> 黄
> $
>
> With your patch:
>
> $ echo -e "黄\n木\n機\n期" | LC_ALL=cmn_TW.UTF-8 sort
> 木
> 黄
> 期
> 機
> $
>
> That seems to show that I applied your patch correctly, right?
Yes, I used to test bug 16905 like this:
$ touch 黄 木 機 期
$ ls
$ LC_ALL=cmn_TW.UTF-8 ls
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-08-09 19:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 11:29 [Bug localedata/17563] New: [PATCH] add hanzi collation to locale cmn_TW bluebat at member dot fsf.org
2014-11-07 11:29 ` [Bug localedata/17563] " bluebat at member dot fsf.org
2016-02-19 10:49 ` [Bug localedata/17563] cmn_TW: add hanzi collation vapier at gentoo dot org
2016-08-10 10:28 ` bluebat at member dot fsf.org
2017-07-19 16:11 ` maiku.fabian at gmail dot com
2017-07-19 16:11 ` maiku.fabian at gmail dot com
2017-07-20 2:49 ` bluebat at member dot fsf.org
2017-08-08 10:02 ` maiku.fabian at gmail dot com
2017-08-08 10:02 ` bluebat at member dot fsf.org
2017-08-08 11:25 ` maiku.fabian at gmail dot com
2017-08-09 9:33 ` bluebat at member dot fsf.org
2017-08-09 13:14 ` maiku.fabian at gmail dot com
2017-08-10 3:06 ` bluebat at member dot fsf.org [this message]
2017-08-10 11:50 ` cvs-commit at gcc dot gnu.org
2017-08-10 13:13 ` maiku.fabian at gmail dot com
2017-08-10 13:21 ` maiku.fabian at gmail dot com
2017-08-10 13:37 ` maiku.fabian at gmail dot com
2017-08-11 7:53 ` bluebat at member dot fsf.org
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-17563-716-WX4qsfSdJR@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).