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 and > based on ICU that of course supports GB18030. See > http://github.com/moriyoshi/mbstring-ng for detail.
I worry about it, too, because GB18030 has very large amount of characters. If it's possible to calculate correspondent code points between unicode and GB18030 at run time, we can reduce them probably. I, however, don't figure out the way not to use the conversion table yet. And, I'm thankful to your excellent work, mbstring-ng. Is there any milestones to include it in the mainline? We hope it is available on both MS Windows and POSIX-based system such as Linux. they use different config.* macros and different compilers, and so on. If there are more people who want to use GB18030 with 'mbstring', it had better to add new encodings although I don't know how many people want it. At least, I want to use GB18030 encoding in the same manner with existing ones. Pierre Joye wrote: > However it is obvious that the mid/long term goal should be to replace > it completely with ICU. I agree with you, of course, in our not so ideal world :) Thanks, Shigeru -- PHP Unicode & I18N Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
