public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldocassola at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/16608] New: es_US locale has invalid collation rules for 'ch' and 'll' Date: Wed, 19 Feb 2014 17:38:00 -0000 [thread overview] Message-ID: <bug-16608-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16608 Bug ID: 16608 Summary: es_US locale has invalid collation rules for 'ch' and 'll' Product: glibc Version: 2.18 Status: NEW Severity: normal Priority: P2 Component: localedata Assignee: unassigned at sourceware dot org Reporter: aldocassola at gmail dot com CC: libc-locales at sourceware dot org The es_EC locale file (which depends on es_US) defines 'ch' and 'll' as standalone letters for collation. This is an incorrect collation procedure according to the rules of the Spanish Royal Academy since 1997 (see http://www.rae.es/consultas/exclusion-de-ch-y-ll-del-abecedario) According to the above rules, words with ch and ll are to be sorted as simply having a 'c' and 'h' and double 'l' E.g.: incorrect (current): file_ce, file_cf, file_cg, file_cz, file_ch correct (expected): file_ce, file_cf, file_cg, file_ch, file_cz The es_ES file specifies the correct behavior and the rest of es_* files depend on it. Please either make es_EC depend on es_ES or fix es_US -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-02-19 17:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-19 17:38 aldocassola at gmail dot com [this message] 2014-02-19 17:39 ` [Bug localedata/16608] " aldocassola at gmail dot com 2014-02-19 18:28 ` carlos at redhat dot com 2014-02-19 18:42 ` aldocassola at gmail dot com 2014-02-19 18:52 ` carlos at redhat dot com 2014-02-19 19:08 ` aldocassola at gmail dot com 2014-02-19 21:04 ` aldocassola at gmail dot com 2014-02-19 21:06 ` aldocassola at gmail dot com 2014-06-13 8:13 ` fweimer at redhat dot com 2024-01-04 12:05 ` maiku.fabian 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-16608-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: 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).