AZAKI Shigeru; php-i18n@lists.php.net
> Subject: Re: [PHP-I18N] adding GB18030 support for mbstring
>
> That is not correct. .NET Names here are also used intenally in MS
> products as well as codepages, and doesn't necessarily reflect the
> actual codeset defined in the IANA cha
t;
>>
>> -Original Message-
>> From: Moriyoshi Koizumi [mailto:m...@mozo.jp]
>> Sent: Tuesday, February 02, 2010 10:54 PM
>> To: KITAZAKI Shigeru
>> Cc: php-i18n@lists.php.net
>> Subject: Re: [PHP-I18N] adding GB18030 support for mbstring
>>
..@mozo.jp]
Sent: Tuesday, February 02, 2010 11:32 PM
To: Tex Texin
Cc: KITAZAKI Shigeru; php-i18n@lists.php.net
Subject: Re: [PHP-I18N] adding GB18030 support for mbstring
That is not correct. .NET Names here are also used intenally in MS
products as well as codepages, and doesn't necessar
thanks, I understand Japanese scripts and encodings.
-Original Message-
From: KITAZAKI Shigeru [mailto:shigeru_kitaz...@cybozu.co.jp]
Sent: Wednesday, February 03, 2010 12:08 AM
To: Moriyoshi Koizumi; Tex Texin
Cc: php-i18n@lists.php.net
Subject: Re: [PHP-I18N] adding GB18030 support for
Moriyoshi Koizumi wrote:
> It just turned out ISO_2022,locale=ja,version=3 is actually ISO-2022-JP-MS.
Thank you for your valuable information.
I'll try ISO_2022,locale=ja,version=3 with ISO-2022-JP-MS.
Tex, thank you for your cooperation.
'halfwidth', called 'hankaku' in Japanese, is sometimes sp
gt; To: KITAZAKI Shigeru
> Cc: php-i18n@lists.php.net
> Subject: Re: [PHP-I18N] adding GB18030 support for mbstring
>
> It just turned out ISO_2022,locale=ja,version=3 is actually ISO-2022-JP-MS.
>
> Moriyoshi
>
> On Wed, Feb 3, 2010 at 10:22 AM, Moriyoshi Koizumi wrote:
>> None
From: KITAZAKI Shigeru [mailto:shigeru_kitaz...@cybozu.co.jp]
>> Sent: Tuesday, February 02, 2010 4:43 AM
>> To: Moriyoshi Koizumi
>> Cc: php-i18n@lists.php.net
>> Subject: Re: [PHP-I18N] adding GB18030 support for mbstring
>>
>> Koizumi-san
>>
>> Let me
:shigeru_kitaz...@cybozu.co.jp]
>> Sent: Tuesday, February 02, 2010 4:43 AM
>> To: Moriyoshi Koizumi
>> Cc: php-i18n@lists.php.net
>> Subject: Re: [PHP-I18N] adding GB18030 support for mbstring
>>
>> Koizumi-san
>>
>> Let me tell you the one concern a
> tex
>
>
> -Original Message-
> From: KITAZAKI Shigeru [mailto:shigeru_kitaz...@cybozu.co.jp]
> Sent: Tuesday, February 02, 2010 4:43 AM
> To: Moriyoshi Koizumi
> Cc: php-i18n@lists.php.net
> Subject: Re: [PHP-I18N] adding GB18030 support for mbstring
>
> Koizum
While that is one of the concerns, I don't quite think having multiple
encoding conversion libraries that requires huge RSS makes much sense.
Looking for possibilities to extend ICU itself should be worth a try.
Regards,
Moriyoshi
2010/2/2 KITAZAKI Shigeru :
> Koizumi-san
>
> Let me tell you the
Sent: Tuesday, February 02, 2010 4:43 AM
To: Moriyoshi Koizumi
Cc: php-i18n@lists.php.net
Subject: Re: [PHP-I18N] adding GB18030 support for mbstring
Koizumi-san
Let me tell you the one concern about mbstring-ng.
The current mbstring supports 'ISO-2022-JP-MS', this is different from
'I
Koizumi-san
Let me tell you the one concern about mbstring-ng.
The current mbstring supports 'ISO-2022-JP-MS', this is different from
'ISO-2022-JP'. And the current implementation of ICU can not convert
between ISO-2022-JP-MS and unicode correctly, I guess.
For example, Japanese hankaku katakana,
hi,
Moriyoshi Koizumi wrote:
> First thank you for your effort. But, I am under the impression that
> the conversion table looks too huge to include in a distribution
> (>30MB). Is there any way to get this more compressed?
>
> BTW, I created an extension that is near-compatible with mbstring an
anislav Malyshev [mailto:s...@zend.com]
> Sent: Monday, February 01, 2010 1:55 PM
> To: php-i18n@lists.php.net
> Subject: Re: [PHP-I18N] Re: [PHP-DEV] RE: [PHP-I18N] adding GB18030 support
> for mbstring
>
> Hi!
>
>> Right, pls read the thread, that's Moriyoshi is working
GB18030 support
for mbstring
Hi!
> Right, pls read the thread, that's Moriyoshi is working on. But can we
> do it in a minor release? I don't think so.
If it returns same results for existing encodings (which should be the
case, ideally, since the encodings are defined, but you kn
Hi!
Right, pls read the thread, that's Moriyoshi is working on. But can we
do it in a minor release? I don't think so.
If it returns same results for existing encodings (which should be the
case, ideally, since the encodings are defined, but you know...) then
why not? The external API would
Joye [mailto:pierre@gmail.com]
> Sent: Monday, February 01, 2010 12:11 PM
> To: Tex Texin
> Cc: Moriyoshi Koizumi; KITAZAKI Shigeru; php-i18n@lists.php.net;
> intern...@lists.php.net
> Subject: Re: [PHP-DEV] RE: [PHP-I18N] adding GB18030 support for mbstring
>
> hi,
>
> On
-I18N] adding GB18030 support for mbstring
hi,
On Mon, Feb 1, 2010 at 8:59 PM, Tex Texin wrote:
> Since ICU supports many conversions, including gb18030, and is regularly
> updated and is already a part of php, it makes no sense to include
> individually written conversions. ICU
Hi!
In an ideal world yes. But in our not so ideal world mbstring is still
here, is still used in many places inside PHP and I think it makes
sense too add more encoding if there is a need for them.
Can't we make mbstring to use ICU data so that if somebody uses the API
he gets the API, but e
hi,
On Mon, Feb 1, 2010 at 8:59 PM, Tex Texin wrote:
> Since ICU supports many conversions, including gb18030, and is regularly
> updated and is already a part of php, it makes no sense to include
> individually written conversions. ICU also gets considerable testing and
> review.
>
> Conversions
-
From: Moriyoshi Koizumi [mailto:m...@mozo.jp]
Sent: Sunday, January 31, 2010 11:29 PM
To: KITAZAKI Shigeru
Cc: php-i18n@lists.php.net; intern...@lists.php.net
Subject: Re: [PHP-I18N] adding GB18030 support for mbstring
Kitazaki-san,
First thank you for your effort. But, I am under the impression
Kitazaki-san,
First thank you for your effort. But, I am under the impression that
the conversion table looks too huge to include in a distribution
(>30MB). Is there any way to get this more compressed?
BTW, I created an extension that is near-compatible with mbstring and
based on ICU that of co
Hm, I just wonder why yet another encoding. Shouldn't unicode be
enough for every one?
2010/1/28 KITAZAKI Shigeru :
> We made a patch to add a mbfilter for GB18030 encoding for PHP-5.3.1.
> Please take a look at our blog:
> http://developer.cybozu.co.jp/oss/2010/01/php-mbstring-pa.html
>
> We wou
We made a patch to add a mbfilter for GB18030 encoding for PHP-5.3.1.
Please take a look at our blog:
http://developer.cybozu.co.jp/oss/2010/01/php-mbstring-pa.html
We would appreciate if you take this patch into the mainline.
BTW, our blog has various other patches for PHP in addition to thi
24 matches
Mail list logo
