This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales project.
[Bug localedata/4628] Provide rump locales with ISO 8601 variants for use with LC_TIME
- From: "gunnarhj at ubuntu dot com" <sourceware-bugzilla at sourceware dot org>
- To: libc-locales at sourceware dot org
- Date: Fri, 20 May 2016 23:27:08 +0000
- Subject: [Bug localedata/4628] Provide rump locales with ISO 8601 variants for use with LC_TIME
- Auto-submitted: auto-generated
- References: <bug-4628-716 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=4628
--- Comment #17 from Gunnar Hjalmarsson <gunnarhj at ubuntu dot com> ---
On 2016-05-20 23:08, carlos at redhat dot com wrote:
> --- Comment #16 from Carlos O'Donell <carlos at redhat dot com> ---
> (In reply to Gunnar Hjalmarsson from comment #15)
>> On 2016-05-20 17:30, carlos at redhat dot com wrote:
>>> Does that clarify why non-English speakers should be able to set
>>> LC_TIME to C@iso8601?
>>
>> I'm afraid it isn't that easy. LC_TIME includes month and weekday
>> names, which are often used by e.g. calendar apps.
>
> Then you don't want LC_TIME to follow ISO 8601?
I want to encourage/make it easier (not enforce) to use ISO 8601 like date and
time formats. That's one thing. Another thing is that LC_TIME unfortunately(?)
includes localized month and weekday names.
> Which might look like `export LC_TIME=en_US:C@iso8601` which says use
> US English language information for language-specific requirements,
> but consider the territory to be generic and following ISO 8601.
>
> I expect language specific entries would be:
> - abday
> - day
> - abmon
> - mon
If those could be broken out from LC_TIME somehow, it would indeed make some
things easier. Suppose it whouldn't be easily accomplished, though...
--
You are receiving this mail because:
You are the assignee for the bug.