From: Wei-Lun Chao <bluebat@member.fsf.org>
To: TAMUKI Shoichi <tamuki@linet.gr.jp>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] localedata: Updates for Taiwanese locales [BZ #24409]
Date: Fri, 19 Nov 2021 22:48:47 +0800 [thread overview]
Message-ID: <CAP1CgNLGvMJbQv2YCM4ndR4z3pJ7zagXQ2hCGXajdUJCWTVD-g@mail.gmail.com> (raw)
In-Reply-To: <202105161001.AA00006@tamuki.linet.gr.jp>
Dear Shoichi,
Thanks for your explanation.
I'll add this part of patch.
TAMUKI Shoichi <tamuki@linet.gr.jp> 於 2021年5月16日 週日 下午6:04寫道:
>
> Hello Wei-Lun-san,
>
> From: Wei-Lun Chao <bluebat@member.fsf.org>
> Subject: Re: [PATCH v2] localedata: Updates for Taiwanese locales [BZ #24409]
> Date: Thu, 13 May 2021 13:10:12 +0800
>
> > > > 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.
> > >
> > > If elements from 0 to 59 are defined for alt_digits in lzh_TW, there
> > > are the following problems:
> > >
> > > $ LANG=lzh_TW date -d "1959-04-01 09:00:00" +"%Oy<U5E74>"
> > > <U4E94><U5341><U4E5D><U5E74>
> > > $ LANG=lzh_TW date -d "1960-04-01 09:00:00" +"%Oy<U5E74>"
> > > 60<U5E74>
> > >
> > > Up to 99 elements should be defined for alt_digits.
> >
> > First, alt_digits works like "alt_numbers". I don't know how to just
> > map each digit to another character.
> > Before this patch, alt_digits covers 0..31, and this patch covers
> > 0..59. I am not sure, is it worthy to extend
> > to 0..99, because those presentations are not suitable for year
> > numbers. For example:
> > $ LANG=lzh_TW date -d "1959-04-01 09:00:00" +"%Oy<U5E74>"
> > We will expect <U4E94><U4E5D><U5E74> instead of <U4E94><U5341><U4E5D><U5E74>
>
> I understand what you are concerned about.
>
> In Japan, for example, it is not sutable to use number names to
> express another form of year notation using alternative numeric
> symbols in years such as AD 1984 and AD 645. It is commonly expressed
> in positional notation. I think the situation is the same in Taiwan.
>
> On the other hand, for example, it is not suitable to use positional
> notation to express another form of year notation using alternative
> numeric symbols in years such as AD 78. It is commonly expressed in
> number names. Please see the attached file alt_digits.png.
>
> I think that these boundaries are empirically determined by whether
> the numerical value is 2 digits or less or 3 digits or more.
> Therefore, it makes sense to define alt_digits up to 99.
>
> Regards,
> TAMUKI Shoichi
prev parent reply other threads:[~2021-11-19 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 5:38 Wei-Lun Chao
2021-05-07 21:23 ` Carlos O'Donell
2021-05-10 3:07 ` Wei-Lun Chao
2021-05-11 11:15 ` TAMUKI Shoichi
2021-05-13 3:53 ` Wei-Lun Chao
2021-05-16 21:46 ` TAMUKI Shoichi
[not found] ` <202105161000.AA00005@tamuki.linet.gr.jp>
2021-11-19 14:47 ` Wei-Lun Chao
2021-05-11 12:41 ` TAMUKI Shoichi
2021-05-13 5:10 ` Wei-Lun Chao
2021-05-16 21:46 ` TAMUKI Shoichi
[not found] ` <202105161001.AA00006@tamuki.linet.gr.jp>
2021-11-19 14:48 ` Wei-Lun Chao [this message]
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=CAP1CgNLGvMJbQv2YCM4ndR4z3pJ7zagXQ2hCGXajdUJCWTVD-g@mail.gmail.com \
--to=bluebat@member.fsf.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=tamuki@linet.gr.jp \
/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).