From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/23724] Albanian date formats are incorrect
Date: Mon, 01 Oct 2018 10:38:00 -0000 [thread overview]
Message-ID: <bug-23724-716-0ukoyNNz7H@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23724-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23724
--- Comment #2 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
I think it is not a problem because it is only how the dates are displayed,
also it does not mean that using 4 digits is impossible. Y2K problem, as far
as I understand it, is about how dates are stored internally. If some locale
conventions want to display year using 2 digits I think it is OK. A good
argument for me is when CLDR says so. Your link shows that 4 digits are also
used in Albanian language, it does not mean that 2 digit year is prohibited.
A quick grep shows that there are currently 106 locales using "%y" in d_fmt
including POSIX and the default C locale (a fallback when setting a locale
fails) plus 8 locales using "%Oy" or "%Ey", compared to the total of 294
locales which actually provide d_fmt (rather than using "copy"). I don't mind
if we set a rule which says that "%y" should never be suggested by glibc by
default and "%Y" should be used instead but we would have to change POSIX and C
locales as well which I think is out of our scope.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-10-01 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 20:54 [Bug localedata/23724] New: " digitalfreak at lingonborough dot com
2018-09-28 21:18 ` [Bug localedata/23724] " fweimer at redhat dot com
2018-10-01 10:38 ` digitalfreak at lingonborough dot com [this message]
2018-12-28 21:18 ` cvs-commit at gcc dot gnu.org
2018-12-28 21:23 ` 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-23724-716-0ukoyNNz7H@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).