From: "nicolas.mailhot at laposte dot net" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/4628] Provide rump locales with ISO 8601 variants for use with LC_TIME
Date: Fri, 20 May 2016 13:20:00 -0000 [thread overview]
Message-ID: <bug-4628-716-EorPcUstCq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-4628-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=4628
--- Comment #9 from Nicolas Mailhot <nicolas.mailhot at laposte dot net> ---
(In reply to Florian Weimer from comment #8)
> But not towards ISO 8601. People use “Thu, 2016-03-17 at 15:18 +0000”
> (taken from <http://article.gmane.org/gmane.comp.mozilla.crypto/18562>).
> But that's not even close to ISO 8601 (which goes far beyond “YYYY-MM-DD”).
That's a strawman, the datetime concept does not exist in human language, no
datetime will ever appear in human sentences (you'll get dates and times, the
format of which is perfectly appropriate in iso 8601 for humans).
Besides, iso 8601 is a very flexible spec, and provides for variations whenever
needed. The W3C profile is just a profile of iso 8601 (for HTML/XML code)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-05-20 13:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-4628-716@http.sourceware.org/bugzilla/>
2016-02-04 13:57 ` fweimer at redhat dot com
2016-05-20 12:44 ` dwmw2 at infradead dot org
2016-05-20 12:44 ` fweimer at redhat dot com
2016-05-20 13:20 ` nicolas.mailhot at laposte dot net [this message]
2016-05-20 13:55 ` carlos at redhat dot com
2016-05-20 13:59 ` fweimer at redhat dot com
2016-05-20 14:04 ` carlos at redhat dot com
2016-05-20 19:13 ` carlos at redhat dot com
2016-05-20 19:13 ` vapier at sourceware dot org
2016-05-20 22:36 ` gunnarhj at ubuntu dot com
2016-05-20 22:37 ` carlos at redhat dot com
2016-05-20 23:28 ` gunnarhj at ubuntu dot com
2017-08-02 13:57 ` yjf.victor at foxmail dot com
2018-06-24 0:50 ` joerg_bugzilla_sourceware at reisenweber dot net
2018-06-24 0:55 ` joerg_bugzilla_sourceware at reisenweber dot net
2021-12-21 14:18 ` dwmw2 at infradead dot org
2022-01-06 22:03 ` carlos at redhat dot com
2022-01-06 22:04 ` carlos at redhat dot com
2022-01-06 22:04 ` carlos at redhat dot com
2022-01-06 22:04 ` carlos at redhat dot com
2022-01-07 9:48 ` nicolas.mailhot at laposte dot net
2022-01-07 10:58 ` dwmw2 at infradead dot org
2022-01-07 11:29 ` nicolas.mailhot at laposte dot net
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-4628-716-EorPcUstCq@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).