From 627a7895564679975632d9b637b27e9c09d3d985 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Sun, 23 Dec 2018 13:33:07 -0700 Subject: Add regnode EXACTFUP, for problematic If a non-UTF-8 pattern contains a MICRO SIGN, this special node is now created. This character is the only one not needing UTF-8 to represent, but its fold does need UTF-8, which causes some issues, so it has to be specially handled. When matching against a non-UTF-8 target string, the pattern is effectively folded, but not if the target is UTF-8. By creating this node, we can remove the special handling required for the nodes that don't have a MICRO SIGN, in a future commit. --- regcomp.sym | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'regcomp.sym') diff --git a/regcomp.sym b/regcomp.sym index ab9943def4..bdbe059cc5 100644 --- a/regcomp.sym +++ b/regcomp.sym @@ -108,7 +108,7 @@ EXACTFAA EXACT, str ; Match this string using /iaa rules (w/len) (stri # End of important relative ordering. EXACTFU_SS EXACT, str ; Match this string using /iu rules (w/len); (string not UTF-8, only portions guaranteed to be folded; folded length > unfolded). - +EXACTFUP EXACT, str ; Match this string using /iu rules (w/len); (string not UTF-8, not guaranteed to be folded; and its Problematic). # In order for a non-UTF-8 EXACTFAA to think the pattern is pre-folded when # matching a UTF-8 target string, there would have to be something like an # EXACTFAA_MICRO which would not be considered pre-folded for UTF-8 targets, -- cgit v1.2.1