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: Joseph Myers <joseph at codesourcery dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 11 Feb 2015 20:35:19 -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> <alpine dot DEB dot 2 dot 10 dot 1502112102460 dot 19244 at digraph dot polyomino dot org dot uk>
On 02/11/2015 04:03 PM, Joseph Myers wrote:
> On Wed, 11 Feb 2015, Carlos O'Donell wrote:
>> Is anyone opposed to having glibc contain a builtin C.UTF-8 locale?
> What's the advantage of this being built-in, rather than simply shipped
> with glibc for compiling with localedef (and listed in
> localedata/SUPPORTED) like all the other locales?
The only advantage, and the main reason for having it is that it can
be depended upon at all times regardless of the state of the operating
system, mounted filesystems, or user removal of locales.
Thus if a developer deploys for say a future RHEL8 with glibc X.Y, where
X.Y has a builtin C.UTF-8, they can with certain knowledge know it is
always there regardless of administrative configuration. Just like they
depend on our core APIs.
I'm sorry if I didn't make that clear.