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

[Paul Eggert]

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 C 
program 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 all 
that it means is that if a C program invokes setlocale with "C.UTF-8" or 
its equivalent, it'll work regardless of what's installed in the file 
system under the locale directory. It'd help to clarify this.