Doc #66420 [Opn->Wfx]: Doc should mention that support of PCRE for UTF8 is broken prior to 5.3

From: Date: Wed, 08 Jan 2014 01:11:31 +0000
Subject: Doc #66420 [Opn->Wfx]: Doc should mention that support of PCRE for UTF8 is broken prior to 5.3
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-10825@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=66420&edit=1 ID: 66420 Updated by: yohgaki@php.net Reported by: matteosistisette at gmail dot com Summary: Doc should mention that support of PCRE for UTF8 is broken prior to 5.3 -Status: Open +Status: Wont fix Type: Documentation Problem Package: Documentation problem PHP Version: Irrelevant Block user comment: N Private report: N New Comment: Thank you for reporting. However, 5.3 support is already ended. It would not be a good idea to add this description at this stage. You can add notes to the manual page. I appreciated if you add this note. Previous Comments: ------------------------------------------------------------------------ [2014-01-05 18:18:22] matteosistisette at gmail dot com Description: ------------ --- From manual page: http://www.php.net/reference.pcre.pattern.modifiers --- """ u (PCRE_UTF8) This modifier turns on additional functionality of PCRE that is incompatible with Perl. Pattern strings are treated as UTF-8. This modifier is available from PHP 4.1.0 or greater on Unix and from PHP 4.2.3 on win32. UTF-8 validity of the pattern is checked since PHP 4.3.5. """ Since the utf8 modifier is available since 4.1.0 (!!) one would expect utf8 support to work since that version unless otherwise stated in the documentation. (otherwise, what does one want a modifier for utf8 for, if utf8 is not supported?) No mention is done in this page that utf8 regular expressions on utf8 strings won't work in PHP versions prior to 5.3, but that is the case. See http://3v4l.org/ERDp5 Either utf8 is only supported as of 5.3.4, or there was a bug that rendered it useless that has only been fixed in 5.3.4. In either case, this must be documented with a gigantic red warning in this page. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=66420&edit=1

« previous php.doc.bugs (#10825) next »