Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56028
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <op.v4dah7ftidpuyk@clk-0081.mshome.net>
References: <CAGa2bXb4EjSRAevwnx=RCJayHe0DiLbcLWxP3Zp79xC=V==GqQ@mail.gmail.com>
 <4EB23E3D.3010908@zend.com> <CAGa2bXamS5re6w4wHtWq4=SyWWdroSQh1vrECJqe_QVT9yw_TA@mail.gmail.com>
 <4EB25BF3.7040703@zend.com> <CAGa2bXao0+55J=V_eM5bCVQ9wn4YYbmiLhxs+uF7ksp44DhoRw@mail.gmail.com>
 <CAGa2bXZTMa2XhDD1tDTi+usgyjSrqvxU6kdAc6zJHuQo-i2hcw@mail.gmail.com>
 <op.v4c60mspidpuyk@clk-0081.mshome.net> <CAGa2bXY4O7pBGLB1K2huh_GRBo8Z3BB38hvjfrmRVbSoQNb5eQ@mail.gmail.com>
 <CAGa2bXaGrSYzZ5_kRyTDnnfjHarbh6HNRUiUBk+SMvgz5WA4Zg@mail.gmail.com> <op.v4dah7ftidpuyk@clk-0081.mshome.net>
Date: Thu, 3 Nov 2011 20:26:55 +0900
Message-ID: <CAGa2bXaifAnq=axuuGPxQTrCSOWPtmqUJBSZJJkKk1RBN7uvKw@mail.gmail.com>
To: Gustavo Lopes <glopes@nebm.ist.utl.pt>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Zend Multibyte support
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

Hi Gustavo,

Thanks for reply.

As long as bison didn't understand multibyte chars, parser would not
work well with them.
Your reply is exactly what I expected.

Thank you for clarification.

--
Yasuo Ohgaki
yohgaki@ohgaki.net



On Thu, Nov 3, 2011 at 8:07 PM, Gustavo Lopes <glopes@nebm.ist.utl.pt> wrot=
e:
> Em Thu, 03 Nov 2011 10:31:47 -0000, Yasuo Ohgaki <yohgaki@ohgaki.net>
> escreveu:
>
>> One last quick question.
>> Zend/tests/multibyte/multibyte_encoding_001.phpt sets
>> mbstring.internal_encoding=3DSJIS.
>>
>> Does PHP 5.4+ suppose to work with SJIS(or other similar encoding)
>> internal_encoding?
>>
>
> No. What matters is that the parser generated by bison is able to recogni=
ze
> the tokens. In an ASCII (as opposed to EBCDIC) machine, this means the
> encoding must be ASCII compatible.
>
> This is the table for SJIS:
> =C2=A0http://icu-project.org/icu-bin/convexp?conv=3Dibm-943_P15A-2003&s=
=3DALL
>
> It would appear that it was ASCII compatible =E2=80=93 \x20-\x7E represen=
t
> U+0020-U+007E, but if you take a closer look you'll see that these bytes =
can
> also appear as part of larger sequences.
>
> For instance, in this script:
>
> <?php
> function a=E6=BC=BE() {}
>
> the character =E6=BC=BE is represented with =C2=A0\xE0\x40, where \x40 re=
presents @ in
> ASCII, so this would give an error, the same this would give an error:
>
> <?php
> function a=C3=A0@() {}
>
> would give an error. In fact, If I save the first script as UTF-8 and the=
n
> run PHP:
>
> $ ./php -d zend.multibyte=3D1 -d zend.script_encoding=3DUTF-8 -d
> mbstring.internal_encoding=3DSJIS sjis.php
> php: Zend/zend_language_scanner.l:126: encoding_filter_script_to_internal=
:
> Assertion `internal_encoding &&
> zend_multibyte_check_lexer_compatibility(internal_encoding)' failed.
> Aborted
>
> it gives an assertion error.
>
> --
> Gustavo Lopes
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>