public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "rei4dan at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/23774] lv_LV collates Y/y incorrectly
Date: Sat, 22 Dec 2018 19:56:00 -0000	[thread overview]
Message-ID: <bug-23774-716-AHxGNwcI1d@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23774-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=23774

Reinis Danne <rei4dan at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rei4dan at gmail dot com

--- Comment #3 from Reinis Danne <rei4dan at gmail dot com> ---
sed-4.6 and grep-3.3 seem to have resolved this particular issue by
implementing rational range interpretation, but [a-ž] and [A-Ž] are buggy.

The former de-interleaves the capital letters for unaccented characters, but
accented capitals are left among the small letters.

Does glibc (2.28) offer alternative collations (or does grep does it)?
As far as I could tell the collation sequence is as specified in the locale:
Using LC_COLLATE=lv_LV.UTF-8
char    strxfrm
i       c2b7010201020101e29b96
I       c2b7010201070101e2afb7
ī       c2b70102140102020101e29bb7
Ī       c2b70102140107020101e2b096
y       c2b701030102
Y       c2b701030107
j       c382010201020101e29c96
J       c382010201070101e2b0a4
Using LC_COLLATE=C.UTF-8
char    strxfrm
i       6b
I       4b
ī       c4ad
Ī       c4ac
y       7b
Y       5b
j       6c
J       4c

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

  parent reply	other threads:[~2018-12-22 19:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-14  8:58 [Bug localedata/23774] New: " danko at very dot lv
2018-10-15 12:11 ` [Bug localedata/23774] " maiku.fabian at gmail dot com
2018-10-15 12:34 ` maiku.fabian at gmail dot com
2018-10-15 12:34 ` maiku.fabian at gmail dot com
2018-12-22 19:56 ` rei4dan at gmail dot com [this message]
2021-09-08 15:12 ` carlos at redhat dot com
2023-12-08 21:19 ` rudolfs.mazurs at gmail dot com
2024-02-01 22:10 ` rudolfs.mazurs at gmail dot com
2024-02-07  8:44 ` maiku.fabian at gmail dot com
2024-02-07  8:45 ` maiku.fabian at gmail dot com
2024-02-07 15:03 ` maiku.fabian at gmail dot com
2024-02-08  7:38 ` 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-23774-716-AHxGNwcI1d@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).