This is the mail archive of the libc-alpha@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] |
On 13 Apr 2016 14:57, Carlos O'Donell wrote: > On 04/13/2016 12:39 PM, Mike Frysinger wrote: > > The ISO 14652 standard defines the valid values for the category > > keyword as only two options: > > posix:1993 > > i18n:2002 > > > > The vast majority of locales had changed the "i18n" string to the > > name of its own locale (e.g. "ak_GH:2013") as well as tweaking the > > date (presumably thinking it should be the date of submission). > > > > Convert all of them to "i18n:2002" for consistency. > > Any chance you can tighten the parser to reject anything but the > two valid category keywords? i figured someone would ask for that eventually :). it's not clear to me how many valid values there are because the ISO 14652 standard is difficult to obtain. i've only be able to find 1999 and 2002 copies, but i'm pretty sure there's other revisions as well. maybe we start off only accepting these two values and worry about the rest later ? the other aspect is that, while we might validate some sanity on the category fields in general, the code (afaict) is not structured for actually handling the differences. for example, if the locale says posix:1993 or i18n:1999 (which the older ISO 14652 1999 standard allows), we don't change the parsing behavior to reject features that are new to i18n:2002. i guess one thing at a time: let's update localdef to only accept these two values and reject all others. i'll look at that before merging this patch in case it's easy to do. -mike
Attachment:
signature.asc
Description: Digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |