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: Martin Sebor <msebor at gmail dot com>, Mike Frysinger <vapier at gentoo dot org>
Cc: GNU C Library <libc-alpha at sourceware dot org>
Date: Thu, 22 Oct 2015 10:27:58 -0700
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> <56290E31 dot 60208 at gmail dot com>

On 10/22/2015 09:26 AM, Martin Sebor wrote:

If the goal is to provide C.UTF-8 as the default for programs
that call setlocale(LC_ALL, "") when no localization environment
variables are set (or set to the empty string), I would suggest

to make it clear.

When I first saw the announcement, I also thought it meant that if a Cprogram didn't invoke setlocale, it'd get a UTF-8-compatible "C" locale(as happens under OS X). But in reading the thread it appears that allthat it means is that if a C program invokes setlocale with "C.UTF-8" orits equivalent, it'll work regardless of what's installed in the filesystem under the locale directory. It'd help to clarify this.

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: Martin Sebor

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