public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
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: Sat, 09 Dec 2017 11:32:00 -0000	[thread overview]
Message-ID: <bug-22550-716-1U8t1AYr0q@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 #13 from Héctor M. Monacci <hector.monacci at gmail dot com> ---
I have just attached another interesting proof.

Back in 1992, i.e., years before the Agreement was reached in 1994, there were
some very prestigious dictionaries that already used the new alphabet (without
CH and LL as independent letters).

The image is from page 241 of hte Gran Diccionario Salvat, originally published
in Barcelona. My copy is from a local edition in Buenos Aires. The newspaper La
Nación published it as a series of installments.

The fact that, back in this publication of 1992, only the Ñ was a special
Spanish character (and not CH and LL) didn't upset anybody.

It is a quarter of a century since. It is time to move on.

Please, can we agree on this?

We need Ñ to be treated properly under es_* locales, and especially under
LC_COLLATE sections. And we need to abandon support, at least as default, for
CH and LL as independent letters.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-12-09 11:32 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
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 [this message]
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-1U8t1AYr0q@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).