From: "hector.monacci at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/22550] es_ES locale (and other es_* locales): collation should treat ñ as a primary different character, sync the collation for Spanish with CLDR
Date: Wed, 06 Dec 2017 10:05:00 -0000 [thread overview]
Message-ID: <bug-22550-716-aKFkAivjlo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22550-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22550
--- Comment #9 from Héctor M. Monacci <hector.monacci at gmail dot com> ---
I agree with Mike.
I think it is way better to synchronize all the variants of the Spanish
language around an official decision taken 23 years ago, by general
international agreement, taught in schools since, and recently reasserted in
2010 when a new Panhispanic Orthography was published
(https://www.diariolibre.com/noticias/el-alfabeto-despide-letras-ch-y-ll-BNdl272715).
This would lead to treat Ñ as the only extra standalone letter in Spanish,
always sorted after N.
My local copy of es_ES (up-to-date Void Linux) has this right now:
LC_COLLATE
% Copy the template from ISO/IEC 14651
copy "iso14651_t1"
END LC_COLLATE
This, of course, is horrible. It even ignores Ñ as a standalone letter.
Please, we need to move ahead. We are late to the party by some years now.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-12-06 10:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 14:32 [Bug localedata/22550] New: " maiku.fabian at gmail dot com
2017-12-05 14:38 ` [Bug localedata/22550] " maiku.fabian at gmail dot com
2017-12-05 14:46 ` maiku.fabian at gmail dot com
2017-12-05 15:18 ` carlos at redhat dot com
2017-12-05 15:20 ` carlos at redhat dot com
2017-12-05 15:31 ` carlos at redhat dot com
2017-12-05 15:47 ` carlos at redhat dot com
2017-12-05 16:13 ` hector.monacci at gmail dot com
2017-12-06 7:12 ` maiku.fabian at gmail dot com
2017-12-06 8:38 ` maiku.fabian at gmail dot com
2017-12-06 10:05 ` hector.monacci at gmail dot com [this message]
2017-12-06 10:28 ` hector.monacci at gmail dot com
2017-12-06 10:37 ` hector.monacci at gmail dot com
2017-12-09 11:26 ` hector.monacci at gmail dot com
2017-12-09 11:32 ` hector.monacci at gmail dot com
2017-12-09 11:35 ` maiku.fabian at gmail dot com
2017-12-20 14:31 ` maiku.fabian at gmail dot com
2018-02-27 16:55 ` cvs-commit at gcc dot gnu.org
2018-02-28 14:13 ` maiku.fabian at gmail dot com
2018-03-02 12:59 ` cvs-commit at gcc dot gnu.org
2018-03-31 12:32 ` jeremip11 at gmail 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=bug-22550-716-aKFkAivjlo@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@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).