This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug localedata/4628] Provide rump locales with ISO 8601 variants for use with LC_TIME
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 20 May 2016 13:54:12 +0000
- Subject: [Bug localedata/4628] Provide rump locales with ISO 8601 variants for use with LC_TIME
- Auto-submitted: auto-generated
- References: <bug-4628-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=4628
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #10 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Nicolas Mailhot from comment #9)
> (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)
Would it suffice to provide C.utf8@iso8601 for the purposes of overriding
LC_TIME and allowing you to use ISO 8601 time representation in the fullest? We
need not duplicate all locales, ISO 8601 is language independent.
--
You are receiving this mail because:
You are on the CC list for the bug.