public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mfabian at suse dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2648] localedata/locales/es_ES has incorrect LC_COLLATE <space> handling Date: Tue, 09 May 2006 16:01:00 -0000 [thread overview] Message-ID: <20060509160051.5368.qmail@sourceware.org> (raw) In-Reply-To: <20060509154921.2648.mfabian@suse.de> ------- Additional Comments From mfabian at suse dot de 2006-05-09 16:00 ------- Original comment in the Novell bugzilla: When LC_COLLATE=es_ES, the sort command ignores spaces in its sorting algorithm, so it sorts MAS PUJADAS, FRANCESC after MASOLIVER GARCIA, JAIME instead of before, even though the comments in /usr/share/i18n/locales/es_ES indicate that the sorting algorithm for this locales should take spaces into account (and sort them before punctuation characters, numbers and letters). This spanish customer is not using LC_COLLATE="POSIX" because the sort command gives incorrect results when dealing with characters with spanish accents so he has to use LC_COLLATE="es_ES.UTF-8" which is ignoring spaces. Even /usr/share/i18n/locales/es_ES states: LC_COLLATE % Base collation scheme: 1994-03-22 % Ordering algorithm: % 1. Spaces and hyphen (but not soft % hyphen) before punctuation % characters, punctuation characters % before numbers, % numbers before letters. I also tested it with every other language setting and the results are always the same: mortlach:~ # export LC_COLLATE="POSIX" mortlach:~ # sort demo AB CDESY ABC DETZ ABCD ETX mortlach:~ # export LC_COLLATE="en_GB.UTF-8" mortlach:~ # sort demo AB CDESY ABCD ETX ABC DETZ mortlach:~ # export LC_COLLATE="de_DE.UTF-8" mortlach:~ # sort demo AB CDESY ABCD ETX ABC DETZ So the question is why LC_COLLATE="POSIX" behaves differently to any other language setting, if this is a feature where is it documented and why is it so? It doesn't make sence that LC_COLLATE="POSIX" behaves different to the English settings (UK & US) which on the other hand behave exactly the same way as any other language setting so there must be a reason why this is so -- http://sourceware.org/bugzilla/show_bug.cgi?id=2648 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2006-05-09 16:01 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-09 15:49 [Bug libc/2648] New: " mfabian at suse dot de 2006-05-09 15:50 ` [Bug libc/2648] " mfabian at suse dot de 2006-05-09 15:53 ` mfabian at suse dot de 2006-05-09 15:53 ` mfabian at suse dot de 2006-05-09 15:56 ` mfabian at suse dot de 2006-05-09 16:00 ` mfabian at suse dot de 2006-05-09 16:01 ` mfabian at suse dot de [this message] 2006-05-09 16:01 ` mfabian at suse dot de 2006-05-09 16:02 ` mfabian at suse dot de 2006-05-09 16:05 ` mfabian at suse dot de 2006-05-10 15:18 ` drepper at redhat dot com 2007-02-17 18:44 ` drepper at redhat dot com 2007-02-23 15:26 ` mfabian at suse dot de 2007-02-23 15:53 ` mfabian at suse dot de 2007-02-24 9:00 ` Markus dot Kuhn at cl dot cam dot ac dot uk 2007-02-27 21:41 ` barbier at linuxfr dot org 2007-10-15 3:49 ` drepper at redhat dot com 2008-04-08 0:55 ` drepper 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=20060509160051.5368.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: linkBe 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).