public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Carlos O'Donell <carlos@redhat.com>,
	 GNU C Library <libc-alpha@sourceware.org>,
	libc-locales@sourceware.org
Subject: Re: Output of `locale -a` could be in mixed encodings?
Date: Wed, 21 Jan 2015 04:50:00 -0000	[thread overview]
Message-ID: <54BF2EC3.2000809@cs.ucla.edu> (raw)
In-Reply-To: <54BF0D06.6020000@redhat.com>

Carlos O'Donell wrote:

> Won't such a fix break existing applications relying on this alias
> to operate correctly?

There shouldn't be any such applications.  Applications are already on notice 
that they should not be relying on these obsolete aliases.

This bug is biting us now because recent versions of GNU grep are stricter about 
treating non-text input as binary.  Existing applications that apply 'grep' to 
locale.alias may have problems if locale.alias is incompatible with the current 
locale's encoding.  This suggests that locale.alias (including its comments) 
should be ASCII only.

> What I need is a way to mark the locale deprecated, accept it as an
> alias, but not display it in `locale -a`.

That would also be nice, though I expect it's lower priority.  I assume that it 
could be done with an ASCII-only locale.alias, somehow.

  reply	other threads:[~2015-01-21  4:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21  1:38 Carlos O'Donell
2015-01-21  2:06 ` Paul Eggert
2015-01-21  2:30   ` Carlos O'Donell
2015-01-21  4:50     ` Paul Eggert [this message]
2015-01-21  2:37 ` Joseph Myers
2015-01-21 16:19 ` Martin Sebor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54BF2EC3.2000809@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-locales@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).