From: "sourceware at robrwo dot sent.com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/27174] New: CLDR v38 and en_GB date issues
Date: Tue, 12 Jan 2021 16:20:20 +0000 [thread overview]
Message-ID: <bug-27174-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27174
Bug ID: 27174
Summary: CLDR v38 and en_GB date issues
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: sourceware at robrwo dot sent.com
CC: libc-locales at sourceware dot org
Target Milestone: ---
I ran across an issue with CLDR v38 that may affect the
unicode-cldr-core package. (I believe the latest package used is v32 but
it's worth being aware of this issue.)
One of the changes is for en_GB to change the date abbreviation for
"September" from "Sep" to "Sept". This will break software that is
relying on locale information to parse or generate dates, and may also
break any formatting that expects 3-letter months.
A thread which discusses how it affects a DateTime::Local perl module is
at https://groups.perlists.pm/sympa/arc/london.pm/2021-01/msg00007.html
but I imagine this will affect anything that relies on CLDR data.
I have reported the issue to the Unicode group at
https://unicode-org.atlassian.net/browse/CLDR-14412
I have also noted the bug on the Ubuntu Translators list at
https://lists.ubuntu.com/archives/ubuntu-translators/2021-January/007729.html
where I was referred to here.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-01-12 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 16:20 sourceware at robrwo dot sent.com [this message]
2021-01-12 16:22 ` [Bug localedata/27174] " sourceware at robrwo dot sent.com
2021-01-12 16:27 ` fweimer at redhat dot com
2021-01-12 16:31 ` sourceware at robrwo dot sent.com
2021-01-12 16:35 ` gunnarhj at ubuntu dot com
2021-01-12 16:36 ` fweimer at redhat dot com
2021-01-12 16:39 ` fweimer at redhat dot com
2021-01-12 16:39 ` sourceware at robrwo dot sent.com
2021-01-12 16:40 ` sourceware at robrwo dot sent.com
2021-01-12 17:06 ` fweimer at redhat dot com
2021-01-12 17:15 ` sourceware at robrwo dot sent.com
2021-01-12 17:18 ` fweimer at redhat dot com
2021-01-29 14:39 ` fweimer at redhat 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-27174-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).