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 <shigeru_kitaz...@cybozu.co.jp>: > 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, GA, A with a sonant mark. > > Although it's better way to modify ICU itself, it takes long time. > How do you think of this? > > Moriyoshi Koizumi wrote: >> BTW, I created an extension that is near-compatible with mbstring and >> based on ICU that of course supports GB18030. See >> http://github.com/moriyoshi/mbstring-ng for detail. >> > > Regards, > Shigeru > -- PHP Unicode & I18N Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
