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

Or people that worry too much about characters being bytes. -Andrei Steph Fox wrote:

Well maybe half the problem with this is that people aren't really aware of what is or isn't the issue. As I (now) understand it, the only people affected by Unicode support will be those currently using mbstring, is that correct? - Steph ----- Original Message ----- From: "Andrei Zmievski" <andrei@gravitonic.com> To: "Steph Fox" <steph@zend.com> Cc: "Rasmus Lerdorf" <rasmus@lerdorf.com>; "Chris Stockton" <chrisstocktonaz@gmail.com>; "php-dev" <internals@lists.php.net> Sent: Thursday, January 24, 2008 1:33 AM Subject: Re: [PHP-DEV] why we must get rid of unicode.semantics switch ASAP

Hey, I can't do everything. -Andrei Steph Fox wrote:

Right, and that's something that does NOT appear in any notes anywhere. ----- Original Message ----- From: "Andrei Zmievski" <andrei@gravitonic.com> To: "Steph Fox" <steph@zend.com> Cc: "Rasmus Lerdorf" <rasmus@lerdorf.com>; "Chris Stockton" <chrisstocktonaz@gmail.com>; "php-dev" <internals@lists.php.net> Sent: Thursday, January 24, 2008 1:03 AM Subject: Re: [PHP-DEV] why we must get rid of unicode.semantics switch ASAP

Pass in "Hello World" where? And yes, you shouldn't have to do anything special (especially for English). The functions will work transparently. -Andrei Steph Fox wrote:

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