From: "bluebat at member dot fsf.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24293] Missing Minguo calendar support for TW locales
Date: Sun, 17 Mar 2019 01:11:00 -0000 [thread overview]
Message-ID: <bug-24293-716-y7s3m2iKDv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24293-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24293
--- Comment #11 from Wei-Lun Chao <bluebat at member dot fsf.org> ---
(In reply to Felix Yan from comment #6)
> > 3. Years before the first year should be prefixed with
> > <U6C11><U570B><U524D>, not with <U6C11><U524D>.
> I believe <U6C11><U524D> is correct according to multiple sources
> (government websites, wikipedia, etc). Some links:
>
> https://land.gov.taipei/cp.aspx?n=1C18A16DCE9C4260
> https://zh.wikipedia.org/wiki/
> %E6%B0%91%E5%9C%8B%E7%B4%80%E5%B9%B4#%E6%A6%82%E8%A6%81
AFAK, it's for something not exist like:
abera "+:2:1913//01//01:+*:<U6C11>:%EC%Ey";/
"+:1:1912//01//01:1912//12//31:<U6C11>:%EC<U5143>";/
"+:1:1911//12//31:-*:<U6C11><U524D>:%EC%Ey"
> I did not find a source for <U6C11><U570B><U524D>, on the other hand. There
> is also confusion in this usage, as <U6C11><U570B><U524D>3<U5E74> could mean
> either <U6C11><U524D>3<U5E74> or the three-year range of
> <U6C11><U570B>1~3<U5E74>.
For the range usage, we use <U6C11><U521D>.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-03-17 1:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 16:55 [Bug localedata/24293] New: " felixonmars at gmail dot com
2019-03-07 7:47 ` [Bug localedata/24293] " bluebat at member dot fsf.org
2019-03-15 7:11 ` bluebat at member dot fsf.org
2019-03-15 9:13 ` cvs-commit at gcc dot gnu.org
2019-03-15 9:26 ` digitalfreak at lingonborough dot com
2019-03-15 9:56 ` bluebat at member dot fsf.org
2019-03-15 10:20 ` felixonmars at gmail dot com
2019-03-15 10:39 ` felixonmars at gmail dot com
2019-03-15 11:39 ` digitalfreak at lingonborough dot com
2019-03-15 16:05 ` felixonmars at gmail dot com
2019-03-15 20:32 ` digitalfreak at lingonborough dot com
2019-03-17 1:11 ` bluebat at member dot fsf.org [this message]
2019-04-02 7:50 ` cvs-commit at gcc dot gnu.org
2019-04-02 8:56 ` bluebat at member dot fsf.org
2019-04-05 20:45 ` digitalfreak at lingonborough 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-24293-716-y7s3m2iKDv@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).