Re: [PHP] UTF 8 support - enable-zend-multibyte ( was Re: [PHP] php bug from 2003 still alive?! - )

2009-03-30 Thread Merlin Morgenstern
haliphax wrote: On Mon, Mar 30, 2009 at 12:34 PM, Merlin Morgenstern wrote: HI there, I now compiled php with zend multibyte. The trouble with the extra characters is now gone, but all special characters are now replaced with a questionmark! The document type shows utf-8, but somehow php seems

Re: [PHP] UTF 8 support - enable-zend-multibyte ( was Re: [PHP] php bug from 2003 still alive?! - )

2009-03-30 Thread haliphax
On Mon, Mar 30, 2009 at 12:34 PM, Merlin Morgenstern wrote: > HI there, > > I now compiled php with zend multibyte. The trouble with the extra > characters is now gone, but all special characters are now replaced with a > questionmark! The document type shows utf-8, but somehow php seems not to >

[PHP] UTF 8 support - enable-zend-multibyte ( was Re: [PHP] php bug from 2003 still alive?! - )

2009-03-30 Thread Merlin Morgenstern
HI there, I now compiled php with zend multibyte. The trouble with the extra characters is now gone, but all special characters are now replaced with a questionmark! The document type shows utf-8, but somehow php seems not to pars the content OK. Does nobody have the same problem? Regards,

Re: [PHP] UTF-8 support

2007-08-04 Thread Daniel Macedo
Yes it will, trim() was given the option to specify other characters in PHP 4.1.0. Rember that it's a byte function, so single byte characters can be handled, you just can't use it for multi-byte characters. ~ DM Naz Gassiep escreveu: Great! Thanks for the answer, that's very helpful. Will

Re: [PHP] UTF-8 support

2007-08-04 Thread Naz Gassiep
Great! Thanks for the answer, that's very helpful. Will trim() work if I specify charlists in the ASCII range? Not that I ever do, but just curious. - Naz Daniel Macedo wrote: Hi Naz, Any byte function is NOT safe for UTF-8. trim() works properly with UTF-8 IF you don't specify the charlist (

Re: [PHP] UTF-8 support

2007-08-04 Thread Daniel Macedo
Hi Naz, Any byte function is NOT safe for UTF-8. trim() works properly with UTF-8 IF you don't specify the charlist (second argument). This is because all whitespace characters are in the ASCII range, and therefore it won't corrupt the UTF-8 string. The explode() function will handle UTF-8 as

Re: [PHP] UTF-8 support

2007-08-04 Thread Naz Gassiep
I've seen that, there is no mb_trim() that I can see. - Naz. adel wrote: http://www.php.net/manual/en/ref.mbstring.php On 8/3/07, Naz Gassiep <[EMAIL PROTECTED]> wrote: The functions trim() and explode() appear to be munging multibyte UTF-8 strings. I can't find multibyte safe versions of t

Re: [PHP] UTF-8 support

2007-08-03 Thread adel
http://www.php.net/manual/en/ref.mbstring.php On 8/3/07, Naz Gassiep <[EMAIL PROTECTED]> wrote: > The functions trim() and explode() appear to be munging multibyte UTF-8 > strings. I can't find multibyte safe versions of them in the manual, do > they exist, or do I have to make my own? > - Naz. >

Re: [PHP] UTF-8 support

2007-08-03 Thread Jon Anderson
Naz Gassiep wrote: The functions trim() and explode() appear to be munging multibyte UTF-8 strings. I can't find multibyte safe versions of them in the manual, do they exist, or do I have to make my own? In what way are they munging the strings? I just tried with a bunch of UTF-8 characters p

[PHP] UTF-8 support

2007-08-02 Thread Naz Gassiep
The functions trim() and explode() appear to be munging multibyte UTF-8 strings. I can't find multibyte safe versions of them in the manual, do they exist, or do I have to make my own? - Naz. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php