public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "barbier at linuxfr dot org" <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, 27 Feb 2007 21:41:00 -0000 [thread overview]
Message-ID: <20070227214116.29701.qmail@sourceware.org> (raw)
In-Reply-To: <20060509154921.2648.mfabian@suse.de>
------- Additional Comments From barbier at linuxfr dot org 2007-02-27 21:41 -------
> Why did you fix the similar problem in Polish locale reported in
> http://sourceware.org/bugzilla/show_bug.cgi?id=388
> ?
>
> Was the information supplied in that bug report so much better?
In BZ388, bug submitter provided references. In your bug report,
there is none. One can argue than native speakers know collation
rules for their language, but at least for French this is obviously
wrong ;)
> And what about the comment in /usr/share/i18n/locales/es_ES:
>
> % Ordering algorithm:
> % 1. Spaces and hyphen (but not soft
> % hyphen) before punctuation
> % characters, punctuation characters
> % before numbers,
> % numbers before letters.
>
> This comment doesn't agree with the current implementation, does it?
Right, AFAICT these collation rules came from an earlier draft of
iso14651_t1, coefficients for U0020 had been fixed but this comment
has not been updated.
Anyway I came to a bookshop today and had a look at a Spanish
dictionary. Spaces were significant in this dictionary:
san
san bernardo
sana-something, I do not remember the exact word
IMHO you can try to either find references as in BZ388, or give
detailed references (ie. not as I did above, I had no pen to write
down details) to several well known Spanish dictionaries which sort
words as you describe.
--
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:[~2007-02-27 21:41 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
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 [this message]
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=20070227214116.29701.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).