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
yohg...@ohgaki.net
On Thu, Nov 3, 2011 at 8:07 PM, Gustavo Lopes wrote:
> Em Thu, 03 No
Em Thu, 03 Nov 2011 10:31:47 -, Yasuo Ohgaki
escreveu:
One last quick question.
Zend/tests/multibyte/multibyte_encoding_001.phpt sets
mbstring.internal_encoding=SJIS.
Does PHP 5.4+ suppose to work with SJIS(or other similar encoding)
internal_encoding?
No. What matters is that the par
$ sapi/cli/php -d zend.multibyte=1 -d zend.script_encodinSJIS -d
mbstring.internal_encoding=UTF8 -d mbstring.output_encoding=UTF8 sjis.php
表
Too many different encodings :)
Thanks. Dmitry.
On 11/03/2011 01:38 PM, Yasuo Ohgaki wrote:
Oops, I thought "?" was due to terminal encoding, but I d
One last quick question.
Zend/tests/multibyte/multibyte_encoding_001.phpt sets
mbstring.internal_encoding=SJIS.
Does PHP 5.4+ suppose to work with SJIS(or other similar encoding)
internal_encoding?
--
Yasuo Ohgaki
yohg...@ohgaki.net
--
PHP Internals - PHP Runtime Development Mailing List
To uns
Hi Gutavo,
Now I see what is going on. I thought string is treated as just a
bunch of data once
is was compiled and passed through.
$ ./sapi/cli/php -d zend.multibyte=1 -d zend.script_encoding=SJIS -d
mbstring.internal_encoding=utf-8 sjis.php 表
Thanks for your time.
May be I should document thi
Em Thu, 03 Nov 2011 09:38:11 -, Yasuo Ohgaki
escreveu:
Oops, I thought "?" was due to terminal encoding, but I double checked
with
redirecting to a file.
$ ./sapi/cli/php -d zend.multibyte=1 -d zend.script_encoding=SJIS
sjis.php > tt
It became "?" instead of "表"..
It seems somethin
Oops, I thought "?" was due to terminal encoding, but I double checked with
redirecting to a file.
$ ./sapi/cli/php -d zend.multibyte=1 -d zend.script_encoding=SJIS sjis.php > tt
It became "?" instead of "表"..
It seems something wrong.
Thanks for you time.
--
Yasuo Ohgaki
yohg...@ohgaki.net
On
Hi Dimity,
Now it seems working as it supposed. Thanks.
$ ./sapi/cli/php -d zend.multibyte=1 -d zend.script_encoding=SJIS sjis.php?
(? is due to my terminal encoding. It sets to UTF-8)
It seems LEAK problem was gone with PHP 5.4, too.
[yohgaki@dev php-src-5.4]$ TEST_PHP_EXECUTABLE=./sapi/cli/ph
I suppose PHP can't autodetect SJIS encoding and needs a hint
for 5.4
$ php -d zend.multibyte=1 -d zend.script_encoding=SJIS sjis.php
5.3 must be compiled with --enable-zend-multibyte, then
$ php -d mbstring.script_encoding=SJIS for 5.3
(I've just tested 5.4 but not 5.3. Just don't have 5.3 c
Hi Dimity & Rui,
I was trying to see if PHP 5.4 and trunk was also affected by this bug report.
--with-zend-multibyte and --enable-debug reports LEAK with run-test.php
https://bugs.php.net/bug.php?id=60194
So I configured as "./configure --enable-debug"
Sorry for being a lazy reader. I could tu
Hi Yasuo,
how did you see that "Zend Multibyte Support" weren't enabled?
$ sapi/cli/php -d zend.multibyte=1 -i | grep -i multibyte
Zend Multibyte Support => provided by mbstring
zend.multibyte => On => On **
Multibyte Support => enabled
Multibyte string engine => libmbfl
Multibyte (japanese
Hi,
It is almost same for me.
What kind of configure option you are using ?
For me (Ubuntu 11.10),
if I made PHP-5.4 with 'configure --enable-mbstring', it works fine.
But, if I made it with 'configure --enable-mbstring
--with-apxs2=/usr/bin/apxs2', a Shift_JIS encoded PHP script causes the
pars
Hi all,
I noticed that "Zend Multibyte Support" won't be on with
./sapi/cli/php -d zend.multibyte=1
nor
zend.multibyte=on (in php.ini)
This happens both php-src and php-src-5.4.
According to php.ini-production from php-src:
; If enabled, scripts may be written in encodings that are incompatible
13 matches
Mail list logo
