From: Wei-Lun Chao <bluebat@member.fsf.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: localedata: Updates for Taiwanese locales [BZ #24409]
Date: Tue, 20 Apr 2021 13:37:06 +0800 [thread overview]
Message-ID: <CAP1CgNLEF8m7CKA4j8H2eKXwqu+M+NeYNVw+SG6S-7TE02FePg@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOoDUAkhHfC2dEB_uXfK5v47cNWwnF7pM=FSL8tJT4z79Q@mail.gmail.com>
H.J. Lu <hjl.tools@gmail.com> 於 2021年4月20日 週二 上午10:01寫道：
>
> On Thu, Apr 8, 2021 at 12:06 AM 趙惟倫 via Libc-alpha
> <libc-alpha@sourceware.org> wrote:
> >
> > Rationale:
> > * Header cleanup: make the header of localedata files consistent
> > * Remove space (abmon): remove the extra prefix space in abmon 1~9
> > * Add (week): add the missing definition of week and first_weekday to 2
> > * Change (thousands_sep): change the thousands_sep from [,] to ['] to
>
> Is space better than ['] as the decimal separator?
Do you mean: thin-space <U2009> better than ['] as thousands separator?
If so, Yes, it can be considered.
>
> > avoid confusion of grouping 4 with usual grouping 3
> > * Simplify (yesexpr) and (noexpr): remove unusual full-width characters
> > * Add collation: add missing collation used in cmn_TW
> >
> > Changelog:
> > * localedata/locales/cmn_TW: Header cleanup; Remove space (abmon); Add
> > (week); Change (thousands_sep); Simplify (yesexpr) and (noexpr).
> > * localedata/locales/hak_TW: Likewise and add collation.
> > * localedata/locales/nan_TW: Likewise and add collation.
> > * localedata/locales/lzh_TW: Likewise and add collation.
>
> Isn't 孟春, 仲春, 季春, 孟夏, 仲夏, 季夏, 孟秋, 仲秋, 季秋, 孟冬, 仲冬, 季冬 for
> lunar calendar?
Yes, you are right. They are not so appropriate. Have you any
suggestion for lzh_TW, or we should just keep using 一月…十二月 as in
cmn_TW?
>
> --
> H.J.
next prev parent reply other threads:[~2021-04-20 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 7:05 趙惟倫
2021-04-20 2:00 ` H.J. Lu
2021-04-20 5:37 ` Wei-Lun Chao [this message]
2021-04-20 12:48 ` H.J. Lu
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=CAP1CgNLEF8m7CKA4j8H2eKXwqu+M+NeYNVw+SG6S-7TE02FePg@mail.gmail.com \
--to=bluebat@member.fsf.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).