[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Case insensitivity seems to ignore lower bound of interval

From: Eric Blake
Subject: Re: Case insensitivity seems to ignore lower bound of interval
Date: Thu, 05 May 2011 11:11:27 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110428 Fedora/3.1.10-1.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.10

On 05/05/2011 10:59 AM, Aharon Robbins wrote:
>> No need.  It's already been attempted in the past.
>> http://sourceware.org/bugzilla/show_bug.cgi?id=12045
>> http://sourceware.org/bugzilla/show_bug.cgi?id=12051
> The first one looks like the main one. Has Ulrich responded to it?

12045 is a documentation request (to at least mention why CEO [collation
element ordering] appears screwy for different locales, and how to
properly write a locale file so that CEO does what you normally expect),
which, to my knowledge, Uli hasn't responded to.

12051 is a request to change away from CEO to any other scheme, and Uli
flat out rejected that, even though POSIX no longer requires CEO.  In
other words, Uli says that the burden is on the locale file writer, and
not on glibc.

But without good documentation on how to write a proper locale file, and
without prods to all of the owners of broken locale files, it's an
uphill battle to get CEO ordering to consistently be useful.  And that
only covers you if you are on a system with glibc which uses CEO
semantics, rather than on any other system where the libc semantics of
range expressions has who-knows-what behavior.

Yes, it would really be nice if all four of bash, gawk, sed, and grep
could agree on the same interpretation of non-C range semantics, and
implement that regardless of the underlying libc behavior.  But what
semantics should we settle on?

It's an age-old problem, with no nice solutions.

Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]