From: Joseph Myers <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Leonhard Holz <leonhard.holz@web.de>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH V4][BZ #18441] fix sorting multibyte charsets with an improper locale
Date: Tue, 29 Mar 2016 22:05:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1603292143440.15654@digraph.polyomino.org.uk> (raw)
In-Reply-To: <56FAA951.7020000@redhat.com>
On Tue, 29 Mar 2016, Carlos O'Donell wrote:
> I believe this is technically inaccurate since it allows all 4-byte
> sequences, when in reality the limit is at U+10FFFF?
That glibc accepts UTF-8 according to the definition in the 2003 edition
of ISO 10646 rather than the definition in the 2011 and later editions is
a known issue. I've filed bug 19883 for it since I couldn't find an
existing bug report in Bugzilla. I don't think it's particularly relevant
to any patch not aiming to fix that bug, but:
> You need not fix it, but we should add a comment saying that for the
> sake of simpler code we're allowing those 4-byte sequences which are
> not normally accepted.
I'd think a reference to this code in bug 19883 might be more useful - or
something in that bug giving a standard (greppable) wording for a comment
identifying places needing updating for the current UTF-8 (or in some
cases UCS-4) definition, with such a comment added in this code.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-03-29 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 10:29 Leonhard Holz
2016-03-29 16:12 ` Carlos O'Donell
2016-03-29 22:05 ` Joseph Myers [this message]
2016-03-29 22:17 ` Zack Weinberg
2016-05-23 7:37 Leonhard Holz
2016-06-17 5:39 ` Leonhard Holz
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=alpine.DEB.2.10.1603292143440.15654@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=leonhard.holz@web.de \
--cc=libc-alpha@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).