public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/22668] LC_COLLATE: the last character of ellipsis is not ordered correctly
Date: Mon, 29 Jun 2020 02:26:11 +0000 [thread overview]
Message-ID: <bug-22668-131-No1bQGayr3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22668-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22668
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2020-06-29
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
I confirm that this fix corrects the issue.
I've reviewed the code in question and indeed the right solution is to move the
cursor to the end of the ellipsis sequence which is pointed to by endp.
I actually end up triggering this when working on C.UTF-8. I saw the end
pointer in all long ellipsis sequences getting the wrong sorting value because
they didn't get any weights (they were being unlinked).
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2020-06-29 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22668-131@http.sourceware.org/bugzilla/>
2020-06-29 2:26 ` carlos at redhat dot com [this message]
2021-04-26 12:39 ` carlos at redhat dot com
2021-04-27 7:23 ` fweimer 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=bug-22668-131-No1bQGayr3@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: 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).