That sounds "good" in my ears. Software that relys on "old" non-unicode behaviour must be written in a way two handle non-unicode and Unicode behaviour in two different ways. But for example a rewritten "Squirrelmail" that runs exlusively on PHP6 would be a good thing.
So you could write on your release notes: "We have this new version SquirrelMail++ that’s running only on hosts running PHP6. Using this would be a great speed and performance increase, because the Unicode addons are only available here. If you need an old non-unicode version, you have to stay with our old historic version." The old historic Squirrelmail version without Unicode support would be stays supported until some time. But all users would know: If I want to have new features, I should think about a change to PHP6, all other users could stay on the old version. In the case of the fantastic software "SquirrelMail++PHP6-only" (which I would use on my servers, too) I would think in this direction! ----- Uwe Schindler [EMAIL PROTECTED] - http://www.php.net NSAPI SAPI developer Bremen, Germany > -----Original Message----- > From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 14, 2007 4:00 PM > To: [EMAIL PROTECTED] > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6? > > Richard Lynch wrote: > >> $a = "マニュアル"; > >> echo $a[1]; > > > > Whoa. > > > > That was weird... > > Right, your mail client doesn't handle Unicode correctly. You might > want to do something about that. > > -Rasmus > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
