This is the mail archive of the
mailing list for the glibc project.
Re: Should glibc provide a builtin C.UTF-8 locale?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Rich Felker <dalias at libc dot org>
- Cc: Joseph Myers <joseph at codesourcery dot com>, Paul Eggert <eggert at cs dot ucla dot edu>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 12 Feb 2015 12:12:55 -0500
- 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> <54DC0546 dot 3080102 at redhat dot com> <alpine dot DEB dot 2 dot 10 dot 1502121207010 dot 10529 at digraph dot polyomino dot org dot uk> <54DCC3A2 dot 9050105 at redhat dot com> <20150212160810 dot GR23507 at brightrain dot aerifal dot cx>
On 02/12/2015 11:08 AM, Rich Felker wrote:
> One more thing -- in the absence of ANY LC_*/LANG vars being set,
> POSIX leaves the default locale for setlocale(x, "")
> implementation-defined. Would it be justifiable to make C.UTF-8 the
> default in this case instead of plain C, so that suppression of UTF-8
> support never happens accidentally (e.g. when stripping the
> environment for security), only by explicitly setting LC_ALL=C or
That is a difficult question. I don't have enough experience to say
one way or the other. However, as maintainer for Fedora I have the
ability to decide in some way for the distribution. My preference
would be for the default to be C.UTF-8, this way python3 and others
could rely on UTF-8 even in stripped environments. The goal for this
discussion and change being to produce builtin UTF-8 support that
doesn't just disappear.