Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30263
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.230 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=dumEjk1W2Canl4ptrrJZHUuiKDPA5egWXTOrW6tENv4Rlli56q31GTmkN5rzWbvzW/GsDoQTDGi1R/0lzdcAbiQyKl+tcGma6zD5yOWObfOiDKlfX7Uwve4/gMpIAO4uubmu7b2qjqauxk1VVB24woK7qGx3o8fmX/7EOjYexYM=
Message-ID: <4858f9d90706190949s618b572bpf3fbb48a1c9f9c7c@mail.gmail.com>
Date: Tue, 19 Jun 2007 18:49:13 +0200
Sender: stefan.walk@gmail.com
To: "Tomas Kuliavas" <tokul@users.sourceforge.net>
Cc: internals@lists.php.net
In-Reply-To: <49348.78.61.224.253.1182270469.squirrel@avilys.eik.lt>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-2022-JP; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1181829227.3478.3.camel@localhost.localdomain>
	 <7d5a202f0706141844l3c75b556hdbecbcd5a43747c9@mail.gmail.com>
	 <4671F184.2020401@lerdorf.com>
	 <6sof73dj69ldpspfc5ukrc58qr9ckbin2b@4ax.com>
	 <4677E7B1.2080305@lerdorf.com>
	 <fe05d1540706190808o1d9305b3td74edd6d1c75c97@mail.gmail.com>
	 <4677F3FA.3010000@pooteeweet.org>
	 <49348.78.61.224.253.1182270469.squirrel@avilys.eik.lt>
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: et@php.net ("Stefan Walk")

On 19/06/07, Tomas Kuliavas <tokul@users.sourceforge.net> wrote:
> I don't care about Unicode support, because it breaks things. I suspect
> that PHP6 Unicode extension won't give me controls that I have in PHP5 and
> PHP4 strings. PHP6 Unicode support is not designed for international
> environment. It is designed for nationalized environments and allows PHP
> script developers to code in their native language. Code written in
> French, Russian, Arabic, Japanese or Chinese is not international. Only
> some people can read it. Only some people can see difference between ァ()
> and ィ(). If I have to debug code written in Japanese or Arabic, language
> is the main barrier in understanding the code.

You're spreading FUD about PHP6s unicode support. Writing code in your
own native language has nothing to do with the unicode support in
PHP6. You can already do that in PHP4 if you use utf-8, since any
sequence of codepoints > 127 translates to a byte-sequence that is a
valid identifier for php.
Have a look at http://www.icu-project.org/ to see what the unicode
features in php6 are really about.

Regards,
Stefan (who also thinks that the switch is of no use,
unicode_semantics should be on all the time. And at least it shouldn't
be off in php.ini-dist and php.ini-recommended)