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]

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

From: Mike Frysinger <vapier at gentoo dot org>
To: Marko Myllynen <myllynen at redhat dot com>
Cc: libc-alpha at sourceware dot org
Date: Thu, 22 Oct 2015 09:18:01 -0400
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> <5628C99A dot 9020406 at redhat dot com>

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

Attachment: signature.asc
Description: Digital signature

References:
- Re: Should glibc provide a builtin C.UTF-8 locale?
  - From: Mike Frysinger
- Re: Should glibc provide a builtin C.UTF-8 locale?
  - From: Marko Myllynen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]