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

[Mike Frysinger]

On 22 Oct 2015 14:33, Marko Myllynen wrote:
> On 2015-10-21 20:49, 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
> > 
> > can people read it over and make sure i didn't miss anything and just
> > fix/update it when i did ;).
> 
> once the C.UTF-8 locale has landed, what shall we do with the C locale,
> more specifically with its transliteration data?
> 
> It was noticed earlier that it contains now ~Unicode 3.2 data with some
> local additions. Should we leave it as-is or drop anything
> non-ASCII/POSIX there?

unless someone has a compelling use case, we should punt it imo
-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/9a7b407a/attachment.sig>