Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25562
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 192.38.9.232 cause and error)
Message-ID: <004d01c6d21d$34bffe00$6602a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Derick Rethans" <derick@php.net>,
	"Michael Wallner" <mike@php.net>
Cc: <internals@lists.php.net>
References: <2b9a524b62303d2b7c3f5e20a7b86537@gravitonic.com> <94.1C.26632.7BBFEF44@pb1.pair.com> <Pine.LNX.4.62.0609061904360.3698@localhost>
Date: Thu, 7 Sep 2006 03:30:29 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: RFC: unicode.semantics: runtime or not?
From: steph@zend.com ("Steph Fox")

>> Andrei Zmievski wrote:
>>
>> > 1. ZEND_INI_SYSTEM and make people run two copies of Apache if they 
>> > want
>> > both modes. This is architecturally more simple and more robust, I 
>> > believe.
>> > 2. ZEND_INI_PERDIR and let people switch modes as described above. This
>> > is a lot of work and will probably result in quite a few edge cases
>> > where we used to rely on stability of one mode (such as APC or
>> > serialization, for example).
>>
>> I think it would be best for all of us to go the more robust route
>> and make unicode.semantics only changeable in php.ini.
>
> I concur.

Me too, if it counts any. I think the people that really need Unicode 
support (aka most of the world) will have it enabled as soon as it's 
possible to do so, and those that don't (USA and some of Europe) won't care 
about it enough to adopt until they get a Chinese client or so. At which 
point they'll have to change their ideas anyway...

- Steph

>
> regards,
> Derick