From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20255 invoked by alias); 18 Nov 2015 19:58:32 -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 22027 invoked by uid 48); 18 Nov 2015 17:46:37 -0000 From: "carlos at redhat dot com" To: libc-locales@sourceware.org Subject: [Bug localedata/15578] kk_KZ: various updates Date: Wed, 18 Nov 2015 19:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: localedata X-Bugzilla-Version: 2.18 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned 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: 2015-q4/txt/msg00068.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D15578 --- Comment #14 from Carlos O'Donell --- (In reply to Marko Myllynen from comment #13) > (In reply to Timur Birsh from comment #12) > >=20 > > > I quickly checked the updated patch but I didn't see my previous comm= ents > > > addressed in it or explained here. From the previous email: > > >=20 > > > > - I don't know the rationale for LC_IDENTIFICATION/category changes > > >=20 > > > This is still unclear, why change this? > >=20 > > This change based on the uk_UA locale. >=20 > I investigated this a bit more. The LC_IDENTIFICATION/category is defined= in > ISO 14652, see http://www.open-std.org/jtc1/SC22/WG20/docs/n972-14652ft.p= df, > which defines two values (i18n/posix) but the current convention in glibc > seems to be to have them like in en_US, de_DE, and the current kk_KZ so I > don't think the change is needed. Given that this information is probably > not used by any program it shouldn't matter much but might be better to > follow the example set by some of the most widely scrutinized locales. We should be following international standards where applicable and those w= ho are working at the ISO level and taking our cues from them where it makes s= ense and at the same time considering backwards compatibility with our current users. Is there a compatibility impact for these changes? --=20 You are receiving this mail because: You are on the CC list for the bug.