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: Paul Eggert <eggert at cs dot ucla dot edu>
To: GNU C Library <libc-alpha at sourceware dot org>
Date: Tue, 17 Feb 2015 07:54:17 -0800
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> <54DBFA8D dot 8030107 at cs dot ucla dot edu> <20150217112942 dot GJ544 at vapier>

Mike Frysinger wrote:

i also vaguely recall OS X supports something like this ?  should
we proactively attempt to harmonize here ?

In OS X, the C locale uses UTF-8 but things are seriously confused:nl_langinfo(CODESET) returns "US-ASCII" and MB_CUR_MAX is 1, among other things.See:


http://lists.gnu.org/archive/html/bug-gnulib/2012-01/msg00342.html

Perhaps an OS X expert can chime in, as I don't really understand what it'strying to do in this area.

Follow-Ups:
- Re: Should glibc provide a builtin C.UTF-8 locale?
  - From: Rich Felker

References:
- Should glibc provide a builtin C.UTF-8 locale?
  - From: Carlos O'Donell
- Re: Should glibc provide a builtin C.UTF-8 locale?
  - From: Paul Eggert
- Re: Should glibc provide a builtin C.UTF-8 locale?
  - From: Mike Frysinger

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