This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCHv3] Expected behaviour for a-z, A-Z, and 0-9 (Bug 23393).
On 07/25/2018 05:06 PM, Rafal Luzynski wrote:
> 25.07.2018 22:25 Carlos O'Donell <carlos@redhat.com> wrote:
>> [...]
>> I had to fix the following locales:
>>
>> modified: localedata/locales/ar_SA
>> modified: localedata/locales/km_KH
>> modified: localedata/locales/lo_LA
>> modified: localedata/locales/or_IN
>> modified: localedata/locales/sl_SI
>> modified: localedata/locales/th_TH
>>
>> They all re-arranged ASCII character collation element ordering like tr_TR,
>> and so they needed manual fixing.
>
> Please check bg_BG. It also has a large reorder: puts all Cyrillic characters
> before Latin. (However, this may not be relevant at all.)
Right, that won't affect the rational range for ASCII.
The new tst-fnmatch.input has this:
886 bg_BG.UTF-8 "a" "[a-z]" 0
887 bg_BG.UTF-8 "z" "[a-z]" 0
888 bg_BG.UTF-8 "A" "[a-z]" NOMATCH
889 bg_BG.UTF-8 "Z" "[a-z]" NOMATCH
890 bg_BG.UTF-8 "A" "[A-Z]" 0
891 bg_BG.UTF-8 "Z" "[A-Z]" 0
892 bg_BG.UTF-8 "a" "[A-Z]" NOMATCH
893 bg_BG.UTF-8 "z" "[A-Z]" NOMATCH
Which tests the range extremes, and it passes.
It doesn't reorder any actual LATIN characters and so it's safe.
Cheers,
Carlos.