Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47330
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.217 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=Vtj71bmNFA/s50ihhe8/f5+6YW1zJnGoL/5Y0mKekDMd8ZVScwO62kxhYDTroNBX5c
         NTy3ig9YoZMqHBXmd3JRLIMRdL4CBuod/itiaT6POAf3I0tzjOGyi+6d7LKbnrOxv1k1
         06fQlIAF2XSdKx4XmhjQeWSaKvdqsEIaO/8mU=
MIME-Version: 1.0
In-Reply-To: <4B9FCEA7.50108@lerdorf.com>
References: <4B9C9007.1080802@lsces.co.uk> <4B9EC3B2.7070901@zend.com>
	 <4B9F4196.9030404@lsces.co.uk>
	 <99cf22521003160448k5028ae61y70e1e61428d13280@mail.gmail.com>
	 <99cf22521003161040x4dba08fblb7e088cef16b64a9@mail.gmail.com>
	 <4B9FCEA7.50108@lerdorf.com>
Date: Tue, 16 Mar 2010 20:10:56 +0100
Message-ID: <fe05d1541003161210w42af19eap957c9632128df5d0@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: dreamcat four <dreamcat4@gmail.com>, Lester Caine <lester@lsces.co.uk>, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Where are we ACTUALLY on Unicode?
From: pierre.php@gmail.com (Pierre Joye)

On Tue, Mar 16, 2010 at 7:32 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> Well, the obvious original reason is that ICU uses UTF-16 internally and
> the logic was that we would be going in and out of ICU to do all the
> various Unicode operations many more times than we would be interfacing
> with external things like MySQL or files on disk. =A0You generally only
> read or write a string once from an external source, but you may perform
> multiple Unicode operations on that same string so avoiding a conversion
> for each operation seems logical.

Exactly, that's why I was not so affirmative about using UTF-8 over
UTF-16. I would like to evaluate both solutions with a small set of
PHP features (say some file ops, 1-2 DBs and part of the core string
functions) and see the impact of using UTF-8 or UTF-16. But it is
definitivelly not a small decision.


--=20
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org