Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53478
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 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=XdplnPXoHWPQC9wH4o7lRp2Fl0AJy+Ml1I9kHNA7cr5/wNMOXq49CmYWt8siuRY3U3
         VTxrtolxeserRolCaNITupGu9OfY/ukgcid9JpmqehKoQElKeSgrvZXsnGzS6TZ6Zl4Z
         Rl/BOkMGK82AvBj0CnKFcUp8CRMY64x/627zI=
MIME-Version: 1.0
In-Reply-To: <4E00818C.7040201@lsces.co.uk>
References: <BANLkTi=qbj_=dmNv__RN4LkDY4GgbTtGYQ@mail.gmail.com>
	<BANLkTiktU3Wau1d6DJt8NgKorBrZm1k=HA@mail.gmail.com>
	<A633CF2D7C7BED41B41F1E64F25507B806048849A2@MAILR001.mail.lan>
	<4DFF7A12.8060808@sugarcrm.com>
	<alpine.DEB.2.02.1106211152240.3774@whisky>
	<BANLkTikTRmc9k7dz3k2DH6LBiU3aA46LPA@mail.gmail.com>
	<4E00818C.7040201@lsces.co.uk>
Date: Tue, 21 Jun 2011 13:42:45 +0200
Message-ID: <BANLkTi=pKXghoh=9HVhT-uNVw9RaSgVTJg@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] foreach() for strings
From: pierre.php@gmail.com (Pierre Joye)

On Tue, Jun 21, 2011 at 1:33 PM, Lester Caine <lester@lsces.co.uk> wrote:
> Pierre Joye wrote:
>>>
>>> It depended on ICU there, and I would be against making a core thing in
>>> > =A0PHP 5.x depend on ICU.
>>
>> It can and should be done as part of intl, actually.
>>
>> But that's somehow unrelated to the proposal here, as it is about
>> byte, not characters :)
>
> I believe this may be where some of the new niggles may be coming from? W=
ith
> browsers returning unicode, it may be that some of the 'extra' characters
> are being returned as multibyte rather than as single bytes? Such as the
> problem reported on the general list currently. How do we ensure that we =
are
> dealing with single byte character strings nowadays?

As it has been stated numerous times in this thread and other, we do
not do anything with multi bytes systems, unicode, etc. mbstring and
intl do, but php's string as of now is all about bytes, array of bytes
if I may describe them this way.

And we can't change this behavior.

Cheers,
--=20
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org