public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper dot fsp at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12054] too many behaviors depend upon LC_ALL
Date: Sat, 25 Sep 2010 02:24:00 -0000	[thread overview]
Message-ID: <20100925022438.18616.qmail@sourceware.org> (raw)
In-Reply-To: <20100924213532.12054.bkorb@gnu.org>


------- Additional Comments From drepper dot fsp at gmail dot com  2010-09-25 02:24 -------
It is completely up to the user to select what they want.  If LC_ALL settings by
themselves are not sufficient use LANG and then some selective LC_PAPER etc
settings.  All the flexibility is there, it's just up to the user to use it.

And what you call "brain-damaged" sorting is what almost everyone else
(especially those not infected by expectations from character encoding) think is
correct.  Go into a library and see what is the right way to sort.

All this can be controlled and overwritten using the variables influencing
setlocale.  Just use them.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


http://sourceware.org/bugzilla/show_bug.cgi?id=12054

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2010-09-25  2:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 21:35 [Bug libc/12054] New: " bkorb at gnu dot org
2010-09-25  2:24 ` drepper dot fsp at gmail dot com [this message]
     [not found] <bug-12054-131@http.sourceware.org/bugzilla/>
2014-06-30  7:59 ` [Bug libc/12054] " fweimer at redhat dot com

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=20100925022438.18616.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).