Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53479
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.125 cause and error)
Message-ID: <4E008EA3.4000403@lsces.co.uk>
Date: Tue, 21 Jun 2011 13:29:23 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-2.2 SeaMonkey/2.0.14
MIME-Version: 1.0
To: "internals@lists.php.net" <internals@lists.php.net>
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> <BANLkTi=pKXghoh=9HVhT-uNVw9RaSgVTJg@mail.gmail.com>
In-Reply-To: <BANLkTi=pKXghoh=9HVhT-uNVw9RaSgVTJg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] foreach() for strings
From: lester@lsces.co.uk (Lester Caine)

Pierre Joye wrote:
> 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
>>>>>   PHP 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? With
>> 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.

That is exactly the point. I suppose what I am asking is how people ensure that 
what they are feeding into simple strings are single byte when cut and past 
nowadays does not make a distinction?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php