From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/22964] New: The Japanese Era name will be changed on May 1, 2019
Date: Wed, 14 Mar 2018 08:09:00 -0000 [thread overview]
Message-ID: <bug-22964-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=22964
Bug ID: 22964
Summary: The Japanese Era name will be changed on May 1, 2019
Product: glibc
Version: 2.26
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: fweimer at redhat dot com
CC: libc-locales at sourceware dot org
Target Milestone: ---
Yoko Oguma pointed out that glibc hard-codes information about the Japanese Era
name:
era "+:2:1990/01/01:+*:平成:%EC%Ey年";/
"+:1:1989/01/08:1989/12/31:平成:%EC元年";/
"+:2:1927/01/01:1989/01/07:昭和:%EC%Ey年";/
"+:1:1926/12/25:1926/12/31:昭和:%EC元年";/
"+:2:1913/01/01:1926/12/24:大正:%EC%Ey年";/
"+:2:1912/07/30:1912/12/31:大正:%EC元年";/
"+:6:1873/01/01:1912/07/29:明治:%EC%Ey年";/
"+:1:0001/01/01:1872/12/31:西暦:%EC%Ey年";/
"+:1:-0001/12/31:-*:紀元前:%EC%Ey年"
This will change due to the abdication.
Additional information:
https://en.wikipedia.org/wiki/Japanese_imperial_transition,_2019
https://en.wikipedia.org/wiki/Japanese_era_name
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-03-14 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 8:09 fweimer at redhat dot com [this message]
2019-04-01 8:50 ` [Bug localedata/22964] " fweimer at redhat dot com
2019-04-01 8:54 ` fweimer at redhat dot com
2019-04-02 7:50 ` cvs-commit at gcc dot gnu.org
2019-04-02 18:49 ` carlos at redhat dot com
2019-04-03 4:01 ` cvs-commit at gcc dot gnu.org
2019-04-03 17:46 ` cvs-commit at gcc dot gnu.org
2019-04-03 20:35 ` srl@icu-project.org
2019-04-03 22:27 ` cvs-commit at gcc dot gnu.org
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-22964-716@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).