--- Begin Message ---
Subject: |
grep -P does not set PCRE2_UCP |
Date: |
Fri, 6 Jan 2023 21:41:53 +0100 |
Hi
Using grep -P for boundary matches yields incorrect results with
non-ASCII letters:
$ echo 'Öst' | grep -P '\bs'
Öst
The output should be nothing in this case, and the culprit seems to be
this line in pcresearch.c:
flags |= PCRE2_UTF;
If the PCRE2_UCP flag is added according to this, the program behaves
correctly:
flags |= PCRE2_UTF|PCRE2_UCP;
The pcre2grep test program in the pcre2 has the same problem, and I
filed an issue there too:
https://github.com/PCRE2Project/pcre2/issues/185
A Twitter discussion with more examples:
https://twitter.com/gro_tsen/status/1610972356972875777
Kind regards
--
Karl Pettersson
Uppsala, Sverige/Sweden
https://static-dust.klpn.se/
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#60618: unicode characters are not identified as such for \w and \b with -P |
Date: |
Sat, 7 Jan 2023 18:28:49 -0800 |
On Fri, Jan 6, 2023 at 11:37 PM Jim Meyering <jim@meyering.net> wrote:
> On Fri, Jan 6, 2023 at 11:28 PM Jim Meyering <jim@meyering.net> wrote:
> > On Fri, Jan 6, 2023 at 7:49 PM Carlo Arenas <carenas@gmail.com> wrote:
> > > Reported to PCRE[1] with mention of GNU grep being also affected.
> > >
> > > [1] https://github.com/PCRE2Project/pcre2/issues/185
> >
> > Yikes. This is a big deal.
> > Thank you for the patch and added test.
I've also added the new names to THANKS.in and pushed this:
https://git.savannah.gnu.org/cgit/grep.git/commit/?id=5e3b760f65f13856e5717e5b9d935f5b4a615be3
--- End Message ---