This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug localedata/15578] kk_KZ: various updates


https://sourceware.org/bugzilla/show_bug.cgi?id=15578

--- Comment #14 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Marko Myllynen from comment #13)
> (In reply to Timur Birsh from comment #12)
> > 
> > > I quickly checked the updated patch but I didn't see my previous comments
> > > addressed in it or explained here. From the previous email:
> > > 
> > > > - I don't know the rationale for LC_IDENTIFICATION/category changes
> > > 
> > > This is still unclear, why change this?
> > 
> > This change based on the uk_UA locale.
> 
> 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.pdf,
> 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 who
are working at the ISO level and taking our cues from them where it makes sense
and at the same time considering backwards compatibility with our current
users. Is there a compatibility impact for these changes?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]