Should glibc provide a builtin C.UTF-8 locale?

[Mike Frysinger]

On 22 Oct 2015 11:13, Rich Felker wrote:
> On Wed, Oct 21, 2015 at 01:49:36PM -0400, Mike Frysinger wrote:
> > i've created a C.UTF-8 page where i've tried to gather all the points
> > people made in this thread:
> > 	https://sourceware.org/glibc/wiki/Proposals/C.UTF-8
> 
> On the wiki I see, under differences from C:
> 
> - LC_COLLATE: Sort using the Unicode codepoint 
> 
> But this does not seem to be a difference. Unicode codepoint order is
> identical to UTF-8 code unit order as unsigned char, i.e. the same as
> the C locale.

i was thinking of overlong encodings, but i guess those are technically
invalid according to the spec.  i think it's still worth calling out in
the doc, but we can include an aside that highlights things.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20151022/89c767ba/attachment.sig>