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: Thu, 07 Mar 2019 07:47:00 -0000 [thread overview]
Message-ID: <bug-24293-716-qwmQb3jn9T@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24293-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24293
Wei-Lun Chao <bluebat at member dot fsf.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bluebat at member dot fsf.org
--- Comment #1 from Wei-Lun Chao <bluebat at member dot fsf.org> ---
(In reply to Felix Yan from comment #0)
> Minguo calendar is the official calendar system, and very widely used in
> Taiwan, it would be nice to have the support in glibc.
Confirmed. "Minguo" calendar is widely used in offical and educational
occasions.
> Some background information: The government website (www.gov.tw) uses it,
> popular public services like Taiwan HSR also uses this calendar system.
In most current cases two calendars coexist, but shifting to Gregorian calendar
is the trend.
> Link to wikipedia: https://en.wikipedia.org/wiki/Minguo_calendar
According to Chinese National Standard "CNS 7648", Gregorian calendar is the
main calendar while "Minguo" calendar as secondary representation.
Referring to reporter's blog:
https://blog.felixc.at/2018/11/add-minguo-calendar-support-as-glibc-localedata-era/
Three extra lines could be proposed(untested):
era "+:2:1913//01//01:+*:<U6C11><U570B>:%EC%Ey<U5E74>";/
"+:1:1912//01//01:1912//12//31:<U6C11><U570B>:%EC<U5143><U5E74>";/
"+:1:1911//12//31:-*:<U6C11><U570B><U524D>:%EC%Ey<U5E74>"
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-03-07 7:47 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 ` bluebat at member dot fsf.org [this message]
2019-03-15 7:11 ` [Bug localedata/24293] " 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
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-qwmQb3jn9T@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).