From: Carlos O'Donell <carlos@redhat.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>,
GNU C Library <libc-alpha@sourceware.org>,
Mike Fabian <mfabian@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: Rational Ranges - Rafal and Mike's opinion? (Bug 23393).
Date: Tue, 24 Jul 2018 20:53:00 -0000 [thread overview]
Message-ID: <b3c5643d-3421-d255-2e26-227618148639@redhat.com> (raw)
In-Reply-To: <1591019639.560449.1532465115579@poczta.nazwa.pl>
On 07/24/2018 04:45 PM, Rafal Luzynski wrote:
> 23.07.2018 20:09 Carlos O'Donell <carlos@redhat.com> wrote:
>> [...]
>> Rafal,
>>
>> As localedata maintainer what is your opinion of changing the meaning
>> of [a-z], [A-Z], and [0-9] to be rational ranges for *all* locales
>> which mean exactly the latin character sequences you would expect
>> e.g. {a,b,c,d,e,f,g,h,i,j,k,l,n,m,o,p,q,r,s,t,u,v,w,x,y,z} for [a-z],
>> [A-Z] likewise, and {0,1,2,3,4,5,6,7,8,9}?
>
> Having discussed this off-list my answer is: I'm in favor of implementing
> rational ranges treating [a-z], [A-Z], [0-9], and all their subsets as
> code-point ranges. But I understand that this is possible only in 2.29.
> Therefore for 2.28 I support this data-based solution.
From the perspective of the user of the library and the locales the
rational ranges we implement will look as-if they were code point ranges
for the ranges in question e.g. a-z, A-Z, 0-9 and their subranges.
For 2.28 we will implement rational ranges for [a-z], [A-Z], and [0-9],
and all of their subsets via a data-only solution. Just wanted to make
it clear that all subsets will be treated as rational ranges.
It is only for other subsets like [!-~] (ASCII range) where we will not
have a rational range until we switch to making ranges operate on code
points. That will be a 2.29 optimization.
OK, I will prepare a patch to fix this.
Cheers,
Carlos.
next prev parent reply other threads:[~2018-07-24 20:53 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 19:43 [PATCH] Keep expected behaviour for [a-z] and [A-z] " Carlos O'Donell
2018-07-19 20:39 ` Florian Weimer
2018-07-20 18:49 ` Carlos O'Donell
2018-07-20 19:02 ` Rich Felker
2018-07-20 19:19 ` Florian Weimer
2018-07-20 21:56 ` Carlos O'Donell
2018-07-23 15:11 ` Florian Weimer
2018-07-23 18:09 ` Rational Ranges - Rafal and Mike's opinion? " Carlos O'Donell
2018-07-24 20:45 ` Rafal Luzynski
2018-07-24 20:53 ` Carlos O'Donell [this message]
2018-07-24 20:59 ` Carlos O'Donell
2018-07-25 15:44 ` Mike FABIAN
2018-07-25 15:54 ` [PATCHv3] Expected behaviour for a-z, A-Z, and 0-9 " Carlos O'Donell
2018-07-25 20:19 ` Florian Weimer
2018-07-25 20:25 ` Carlos O'Donell
2018-07-25 20:31 ` Florian Weimer
2018-07-25 20:57 ` [PATCHv4] " Carlos O'Donell
2018-07-26 2:34 ` [PATCHv4a] " Carlos O'Donell
2018-07-26 14:51 ` Florian Weimer
2018-07-26 14:59 ` Carlos O'Donell
2018-07-28 1:12 ` [WIPv5] " Carlos O'Donell
2018-07-30 17:40 ` Florian Weimer
2018-07-30 17:45 ` Carlos O'Donell
2018-07-30 17:54 ` Florian Weimer
2018-07-30 18:26 ` Carlos O'Donell
2018-07-30 18:34 ` Florian Weimer
2018-07-31 2:18 ` Carlos O'Donell
2018-07-25 21:06 ` [PATCHv3] " Rafal Luzynski
2018-07-25 21:12 ` Carlos O'Donell
2018-07-25 21:35 ` [PATCH] Keep expected behaviour for [a-z] and [A-z] " Carlos O'Donell
2018-07-25 22:50 ` Florian Weimer
2018-07-26 1:20 ` Carlos O'Donell
2018-07-26 8:09 ` Andreas Schwab
2018-07-26 9:16 ` Florian Weimer
2018-07-26 1:33 ` Jonathan Nieder
2018-07-26 1:49 ` Carlos O'Donell
2018-07-26 2:16 ` Jonathan Nieder
2018-07-26 3:48 ` Carlos O'Donell
2018-07-26 7:42 ` Florian Weimer
2018-07-26 8:18 ` Andreas Schwab
2018-07-26 9:15 ` Florian Weimer
2018-07-26 13:25 ` Carlos O'Donell
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=b3c5643d-3421-d255-2e26-227618148639@redhat.com \
--to=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mfabian@redhat.com \
/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).