This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Should glibc provide a builtin C.UTF-8 locale?
- From: Florian Weimer <fweimer at redhat dot com>
- To: Mike FABIAN <mfabian at redhat dot com>, keld at keldix dot com
- Cc: "Carlos O'Donell" <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Pravin Satpute <psatpute at redhat dot com>, Jens Petersen <petersen at redhat dot com>
- Date: Tue, 27 Oct 2015 22:43:22 +0100
- Subject: Re: Should glibc provide a builtin C.UTF-8 locale?
- Authentication-results: sourceware.org; auth=none
- References: <54DB8243 dot 3050903 at redhat dot com> <20151021174936 dot GA26317 at vapier dot lan> <5627DAAE dot 8060703 at redhat dot com> <20151021205540 dot GA30739 at www5 dot open-std dot org> <s9dr3kgfqlx dot fsf at ari dot site>
On 10/27/2015 01:22 PM, Mike FABIAN wrote:
> Do we care how a C.UTF-8 locale sorts outside of the ASCII range?
Maybe I'm approaching this from completely the wrong end, but I think
âLC_ALL=C sortâ and âLC_ALL=C.UTF-8 sortâ should have the same ordering
and speedâotherwise C.UTF-8 is somewhat less useful than it could be. I
think this means lexicographical ordering by unsigned bytes. Thanks to
UTF-8 magic, that coincides with codepoint ordering for well-encoded UTF-8.
Florian