From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79460 invoked by alias); 20 May 2016 22:37:13 -0000 Mailing-List: contact libc-locales-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-locales-owner@sourceware.org Received: (qmail 73736 invoked by uid 48); 20 May 2016 21:08:36 -0000 From: "carlos at redhat dot com" 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 22:37:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: localedata X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: libc-locales at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2016-q2/txt/msg00283.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D4628 --- Comment #16 from Carlos O'Donell --- (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? >=20 > 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? Instead you want an arbitrary date and time that suits you but is easier th= an making and maintaining your own locale? Then we're back to Mike's suggestion in comment #13. Which might look like `export LC_TIME=3Den_US:C@iso8601` which says use US English language information for language-specific requirements, but consid= er the territory to be generic and following ISO 8601. I expect language specific entries would be: - abday - day - abmon - mon I expect the territory specific entries would be: - week - d_t_fmt - d_fmt - t_fmt - t_fmt_ampm - am_pm This is as Mike argues in his email. In which case users would see their language-specific day names, month name= s, etc, but the start of the week is always going to be Monday per ISO8601, and date and time formats will be ISO8601. The outliers are t_fmt_ampm, which doesn't exist in ISO8601, so it should I= MO be identical to t_fmt, and am_pm should be an empty set. Thus do we all agree that we *don't* want ISO 8601? That what we really want is layered locales with language/territory layerin= g? If you object, please describe some other kind of model that you're considering. --=20 You are receiving this mail because: You are the assignee for the bug.