https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6225
--- Comment #6 from Mark Martinec <[email protected]> 2009-10-25 16:29:52 UTC --- The perl bug has been resolved now, see: http://rt.perl.org/rt3//Public/Bug/Display.html?id=69973 The problem and its resolution may have an impact on our choice of combining utf8 with non-utf8 strings vs. regexp. In particular, see the last paragraph: > Resolved by: > > commit 0abd0d78a73da1c4d13b1c700526b7e5d03b32d4 > Author: Yves Orton <demerphq at gmail.com> > Date: Sun Oct 25 20:37:08 2009 +0100 > > disable non-unicode case insensitive trie matching > > Also revert 8902bb05b18c9858efa90229ca1ee42b17277554 as it merely > masked one symptom of the deeper problems. > > Also fixes RT #69973, which was a segfault which was exposed by > 8902bb05, see the ticket for further details. > > http://rt.perl.org/rt3//Public/Bug/Display.html?id=69973 > > At the core of this is the problem that in unicode matching a bunch > of code points have case folding rules beyond just A-Z/a-z. Since > the case folding rules are decided at runtime by the string, we can't > use the same TRIE tables for both unicode/non-unicode matching. > > Until this is reconciled or some other solution is found case > insensitive matching only gets the TRIE optimisation when the pattern > is unicode. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
