Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53511
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 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=J/2TfxTwmZIfbuI5Aemmo2ZK0R+/TFrdke1y7fm4d8uNgNIqI2vnF6zXNhqkBTbLoU
         dum7x25jan3wGoN/E4tT/k7+puUMNs1zgxpClgFCgBr3V4Y2jmYJX7saHoeX3LGMLELp
         oXjaTPu65o43wRWrOexBW9X8g2960lyVYuNXg=
MIME-Version: 1.0
In-Reply-To: <4E01F0C6.6040401@thelounge.net>
References: <BANLkTi=qbj_=dmNv__RN4LkDY4GgbTtGYQ@mail.gmail.com>
	<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>
	<4E008EA3.4000403@lsces.co.uk>
	<A633CF2D7C7BED41B41F1E64F25507B80604884A3D@MAILR001.mail.lan>
	<41269.5975f3c3.1308671739.nsm@avilys.eik.lt>
	<4E00C370.9040803@thelounge.net>
	<BANLkTi=XGwMdcRo_qjf7KRuRQ9uCWHAMUQ@mail.gmail.com>
	<4E00C5D0.9020302@thelounge.net>
	<57392.5975f3c3.1308676323.nsm@avilys.eik.lt>
	<4E00DA33.9040504@thelounge.net>
	<58008.5975f3c3.1308687593.nsm@avilys.eik.lt>
	<4E00FEAC.3040500@thelounge.net>
	<52139.5975f3c3.1308720282.nsm@avilys.eik.lt>
	<4E01CEA0.2090607@thelounge.net>
	<op.vxg8al0ridpuyk@clk-0081.mshome.net>
	<4E01DE36.40009@thelounge.net>
	<op.vxhbs7y5idpuyk@clk-0081.mshome.net>
	<4E01F0C6.6040401@thelounge.net>
Date: Wed, 22 Jun 2011 09:49:16 -0400
Message-ID: <BANLkTimqdJm2r9FDnx-bq1srqsYEYXbD2w@mail.gmail.com>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: 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: ircmaxell@gmail.com (Anthony Ferrara)

> and why this will not return true if $str is ISO-8859-1?

For lower 7 bit characters (code points <=3D 127) it would return true.
But if there is a single higher character (outside of ascii), it would
only return true if the byte sequences follow UTF-8 semantics.  So it
would return false if ISO-8859-1.

For example, character =E9 is 0xe9 (code point 234) in ISO-8859, but
character 0xc3a9 in UTF-8.  So if it encountered a byte stream such as
0xe92041 ("=E9 A"), it knows it cannot be UTF-8 since 0xe920 is not a
valid byte sequence.  But if it saw 0xc3a92041, ("=E9 A"), it knows it
is valid UTF-8 (it could be another character set, but it is valid in
UTF-8)...

Please note that it's not checking if the string **is** UTF-8, just if
the byte sequences in the string are valid when interpreted as UTF-8.
You could have the Latin-1 string 0xc3a92041: ("=C3=A9 A") which parses as
valid UTF-8...

On Wed, Jun 22, 2011 at 9:40 AM, Reindl Harald <h.reindl@thelounge.net> wro=
te:
>
>
> Am 22.06.2011 15:30, schrieb Gustavo Lopes:
>> Em Wed, 22 Jun 2011 13:21:10 +0100, Reindl Harald <h.reindl@thelounge.ne=
t> escreveu:
>>
>>> Am 22.06.2011 14:14, schrieb Gustavo Lopes:
>>>> It's actually 3 lines:
>>>>
>>>> function str_is_utf8($str) {
>>>> =A0 =A0 return $str =3D=3D "" || htmlspecialchars($str, 0, "UTF-8");
>>>> }
>>>
>>>
>>> WTF should this do?
>>> this won't return boolean
>>>
>>
>> The reason it works is that
>> 1) || coerces the operands into booleans (if they get to be evaluated)
>> 2) htmlspecialchars returns "" on bad input sequence
>> 3) (bool) "" =3D=3D=3D false
>>
>> But even if you didn't know these things, you should have bothered to at=
 least test it
>> before sending this response
>
> and why this will not return true if $str is ISO-8859-1?
>
>