Pierre Joye wrote:
On Tue, Jun 21, 2011 at 1:33 PM, Lester Caine<les...@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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
