This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Keep expected behaviour for [a-z] and [A-z] (Bug 23393).
- From: Florian Weimer <fweimer at redhat dot com>
- To: Carlos O'Donell <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Rich Felker <dalias at aerifal dot cx>, Mike Fabian <mfabian at redhat dot com>, Zorro Lang <zlang at redhat dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Thu, 26 Jul 2018 00:50:37 +0200
- Subject: Re: [PATCH] Keep expected behaviour for [a-z] and [A-z] (Bug 23393).
- References: <9d6f47ec-f9eb-ead0-889c-3b9aae66551c@redhat.com> <4de6a552-8b4c-ffe0-caf2-0a2d07a908f4@redhat.com>
On 07/25/2018 11:35 PM, Carlos O'Donell wrote:
I have committed only the most conservative fix for this issue, which is
to deinterlace the lower and upper case ranges.
I think we are too late to commit rational ranges, and we can do that in
2.29 when it opens. Right now I want to remove the blocker that is causing
regressions for en_US.UTF-8 scripts that use [a-z], and [A-Z].
How is this the most conservative fix, relative to glibc 2.27 upstream?
[a-z] still matches lots of non-ASCII characters, which it did not before.
When I meant that we left regression-fixing territory, I was talking
about the locales which had iso14651_t1_common customizations.
Thanks,
Florian