Re: why we must get rid of unicode.semantics switch ASAP

Hey Andrei, You can't just say that without giving full details. We've seen all your 'this will cope with Russian, Hebrew, Greek, Japanese and Icelandic' demos. We haven't seen what happens to English, French or German - ever. So what happens if I pass in "Hello World", in English, and it's regarded as an an IS_UNICODE string? Would I know about it? Is there anything special I should do? Or does it just happen as always, and what-was-all-the-fuss-about? - Steph ----- Original Message ----- From: "Andrei Zmievski" <andrei@gravitonic.com> To: "Rasmus Lerdorf" <rasmus@lerdorf.com> Cc: "Chris Stockton" <chrisstocktonaz@gmail.com>; "php-dev" <internals@lists.php.net> Sent: Thursday, January 24, 2008 12:53 AM Subject: Re: [PHP-DEV] why we must get rid of unicode.semantics switch ASAP

Did you mean to say "can't make the default string IS_STRING"? Because that's the only reading that makes sense given the rest of the message. -Andrei Rasmus Lerdorf wrote:

If we get rid of the switch, then I agree that we can't make the default string IS_UNICODE. We would be crippling the implementation and taking a step backwards in terms of leading the way in Unicode adoption. The longterm goal for just about everyone has got to be a "Unicode everywhere" approach. It used to be that the Web was primarily a Western single-byte charset phenomena, but that hasn't been the case for years. All major applications out there have implemented various hacks to deal with these issues, some with more success than others.

-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php