This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Output of `locale -a` could be in mixed encodings?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Paul Eggert <eggert at cs dot ucla dot edu>, GNU C Library <libc-alpha at sourceware dot org>, libc-locales at sourceware dot org
- Date: Tue, 20 Jan 2015 21:20:54 -0500
- Subject: Re: Output of `locale -a` could be in mixed encodings?
- Authentication-results: sourceware.org; auth=none
- References: <54BF0329 dot 5050604 at redhat dot com> <54BF093D dot 4090100 at cs dot ucla dot edu>
On 01/20/2015 09:04 PM, Paul Eggert wrote:
> Carlos O'Donell wrote:
>> We should stop using aliases that are anything but ASCII to avoid
>> future problems.
>
> Yes, that sounds right. If you comment out the "franÃais" and
> "bokmÃl" lines from locale.alias, I assume that fixes the problem?
> If so, let's do that. The fancier fixes you mention also sound nice,
> but omitting the non-ASCII aliases should be helpful anyway, for
> programs other than 'locale' itself.
Won't such a fix break existing applications relying on this alias
to operate correctly?
What I need is a way to mark the locale deprecated, accept it as an
alias, but not display it in `locale -a`.
Thus I think the robust backwards compatible solution is just slightly
more complicated.
In that case we would add a `francais` option and hide `franÃais`
and `bokmÃl` but still accept them. We would also add a test to validate
that all of the glibc locales are within ASCII.
Did I miss something?
Cheers,
Carlos.