In UTF-16 builds it used to work. In UTF-8 mode, it doesn't. However, narrower characters like \f are matched. Looking at the C code, both \f and \x2028 should be matched if PCRE2_BSR_UNICODE is set and the macro EBCDIC is undefined.
This is a lower priority bug but may indicate deeper issues, like wide UTF-8 characters (2+ bytes) being mishandled.
In
text-2
branch.In UTF-16 builds it used to work. In UTF-8 mode, it doesn't. However, narrower characters like
\f
are matched. Looking at the C code, both\f
and\x2028
should be matched ifPCRE2_BSR_UNICODE
is set and the macroEBCDIC
is undefined.This is a lower priority bug but may indicate deeper issues, like wide UTF-8 characters (2+ bytes) being mishandled.