From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/9842] en_CA: incorrect date format
Date: Wed, 10 Aug 2016 10:28:00 -0000 [thread overview]
Message-ID: <bug-9842-716-EBO6ks8hrE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9842-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=9842
--- Comment #7 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 71b67af1ffa57a0322ac1bd77141060fffc4b4e4 (commit)
from 9b3d1336f7f3b6161289627b769a95ec5321e931 (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=71b67af1ffa57a0322ac1bd77141060fffc4b4e4
commit 71b67af1ffa57a0322ac1bd77141060fffc4b4e4
Author: Martin Pitt <martin.pitt@ubuntu.com>
Date: Fri Aug 14 01:22:37 2015 -0400
locales: en_CA: update d_fmt [BZ #9842]
The date format in en_CA/LC_TIME specifies the date format as "%d/%m/%y".
However, it should be "%Y-%m-%d". This is the standard date format in
Canada as specified by the Canadian Standards Association in CSA
Z234.5:1989,
which adopts the ISO 8601 standard.
Here's the web page from the National Research Council of Canada
citing ISO 8601 as the standard date/time format in Canada:
http://www.nrc-cnrc.gc.ca/eng/services/time/faq/#Q8
International Standard ISO 8601 specifies numeric representations
of date and time. The recommended full format is of the form
2001-12-31 23:59:28.73 UTC. The intent of this standard is to avoid
confusion in international communications which can arise with the
many different national notations. This format has the advantage
that it permits dates to be readily sorted in chronological order
by computer systems.
Windows 8+ and OS X also switched to this format.
-----------------------------------------------------------------------
Summary of changes:
localedata/ChangeLog | 5 +++++
localedata/locales/en_CA | 2 +-
2 files changed, 6 insertions(+), 1 deletions(-)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-08-10 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9842-716@http.sourceware.org/bugzilla/>
2014-07-01 21:38 ` [Bug localedata/9842] Incorrect date format in en_CA.utf8 locale fweimer at redhat dot com
2015-08-10 21:26 ` dan.mcgregor at usask dot ca
2015-08-29 22:53 ` vapier at gentoo dot org
2015-08-29 22:53 ` vapier at gentoo dot org
2015-08-29 22:53 ` vapier at gentoo dot org
2016-02-19 10:50 ` [Bug localedata/9842] en_CA: incorrect date format vapier at gentoo dot org
2016-08-10 10:28 ` vapier at gentoo dot org
2016-08-10 10:28 ` cvs-commit at gcc dot gnu.org [this message]
2016-08-10 10:29 ` vapier at gentoo dot 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-9842-716-EBO6ks8hrE@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).