ID:               19909
 Updated by:       [EMAIL PROTECTED]
 Reported By:      paul at honeylocust dot com
-Status:           No Feedback
+Status:           Bogus
 Bug Type:         mbstring related
 Operating System: any
 PHP Version:      4.3.0-pre1
 New Comment:

Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions.  Due to the volume
of reports we can not explain in detail here why your report is not
a bug.  The support channels will be able to provide an explanation
for you.

Thank you for your interest in PHP.




Previous Comments:
------------------------------------------------------------------------

[2002-11-10 18:20:41] [EMAIL PROTECTED]

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.



------------------------------------------------------------------------

[2002-10-14 16:22:40] [EMAIL PROTECTED]

Since when has PCRE been a multibyte string encoding?
Can you be more specific about what you need?

PHP ships with UTF-8 enabled PCRE by default (if you
use the bundled PCRE), and has done since before 4.2
for unix (4.2 and later for windows).

mbstring != PCRE; their functions are completely different.

------------------------------------------------------------------------

[2002-10-14 14:48:41] paul at honeylocust dot com

Mbstring doesn't provide support for PCRE.  This is unfortunate since
there is (experimental) UTF-8 support in PCRE which is as simple to
turn on as flipping a compile flag and specifying an option to
pcre_compile()

------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=19909&edit=1

Reply via email to