Darby Felton <[EMAIL PROTECTED]> writes:
>
> Hi Josh,
>
> The reason that it is failing for you appears to be that your PCRE does
> not have UTF-8 support compiled in. This is likely the result of the
> particular distribution not having used the --enable-utf8 option.
>
> What this means to us is that the class should become aware of whether
> such support is available, and act accordingly.
>
> I'll go ahead and file a JIRA issue for this so that users of
> distributions that do not have PCRE UTF-8 support may still use the
> affected classes (though of course without UTF-8 support :) ).
>
> Best regards,
> Darby
>
My newslist reader must be slow, I'm responding but it only posts about 30
minutes later. I am not sure the UTF-8 issue is the problem here. I just ran
this simple test script and received no error:
ini_set('display_errors', 'On');
error_reporting(E_ALL);
preg_match('/[^[\p{L}\p{N}]]/u', 'testing123', $matches);
var_dump($matches);
My assumption based on the link you posted is that an unsupported option such as
/u would have given me a php warning message. I am looking for a way to
determine what options were used for the PCRE distribution... it is a RHEL5
package so I should be able to find it.
Josh
