[pcre-dev] [Bug 1670] --color produces invalid UTF-8 for property matches

[admin]

https://bugs.exim.org/show_bug.cgi?id=1670

Hermann Zahnweh eximbugs.apri...@spamgourmet.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #2 from Hermann Zahnweh eximbugs.apri...@spamgourmet.com ---
D’oh, I didn’t realize I needed -u. Thanks! I never became aware of that
switch, probably because I expected Unicode to be the default, and I mostly
specified patterns in verbatim, so I guess byte-by-byte matching would have
worked there. With -u, everything works as expected. Though I guess I will have
to ping some people who use PCRE as a library.

-- 
You are receiving this mail because:
You are on the CC list for the bug.-- 
## List details at https://lists.exim.org/mailman/listinfo/pcre-dev 

[pcre-dev] [Bug 1670] --color produces invalid UTF-8 for property matches

[admin]

https://bugs.exim.org/show_bug.cgi?id=1670

--- Comment #1 from Philip Hazel p...@hermes.cam.ac.uk ---
Again, I thought I replied to this via email. As you did not specify -u or
--utf when you called pcre2grep, it would not be treating the input as UTF.
Intead, it would be processing it byte by byte. Please try again with the -u
option to see if that is the cause of the effect.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/pcre-dev