From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24293] Missing Minguo calendar support for TW locales
Date: Fri, 15 Mar 2019 09:13:00 -0000 [thread overview]
Message-ID: <bug-24293-716-6H4WbCSIsG@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 #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, master has been updated
via 238d60a1fb5081450ca57d3e20f6c1c27df9afb5 (commit)
from 5b06f538c5aee0389ed034f60d90a8884d6d54de (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=238d60a1fb5081450ca57d3e20f6c1c27df9afb5
commit 238d60a1fb5081450ca57d3e20f6c1c27df9afb5
Author: Felix Yan <felixonmars@archlinux.org>
Date: Thu Mar 7 17:40:02 2019 +0800
localedata: Add Minguo calendar support to Taiwanese locales [BZ #24293]
Minguo calendar is the official calendar system, and very widely used in
Taiwan. This commit adds its support into glibc.
Some background information: The government website (www.gov.tw) uses it,
popular public services like Taiwan HSR also use this calendar system.
Link to Wikipedia: https://en.wikipedia.org/wiki/Minguo_calendar
[BZ #24293]
* localedata/locales/zh_TW (era): Add, support Minguo calendar.
* localedata/locales/cmn_TW (era): Likewise.
* localedata/locales/hak_TW (era): Likewise.
* localedata/locales/lzh_TW (era): Likewise.
* localedata/locales/nan_TW (era): Likewise.
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 9 +++++++++
localedata/locales/cmn_TW | 4 ++++
localedata/locales/hak_TW | 4 ++++
localedata/locales/lzh_TW | 4 ++++
localedata/locales/nan_TW | 4 ++++
localedata/locales/zh_TW | 4 ++++
6 files changed, 29 insertions(+), 0 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-03-15 9:13 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 [this message]
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-6H4WbCSIsG@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).