On Saturday, June 1, 2002, at 12:34 AM, Autrijus Tang wrote:
On Fri, May 31, 2002 at 06:18:55AM +0900, Dan Kogai wrote:
As a matter of fact GB18030 is ALREADY supported via Encode::HanExtra
by
Autrijus Tang. The only reason GB18030 was not included in Encode main
is sheer size of the map.
Yes, partly because it was not implemented algorithmically. :)
I was browsing http://www-124.ibm.com/cvs/icu/charset/data/ucm/ and
toying
with uconv, and wondered:
1) Does Encode have (or intend to have) them all covered?
No, Unless they appear in www.unicode.org. Though some of them are
actually adopted. Useful it may be I found raw ICM too Big and too
Blue :)
2) If not, would a Encode::ICU be wise?
I'm not so sure. But if I were the one to implement Encode::ICU, it
will not be just a compiled collection of UCM files but a wrapper to all
library functions that ICU has to offer. I, for one, am too lazy for
that.
3) A number of encodings are in HanExtra but not their ucm repository,
namedly big5plus, big5ext and cccii. Is is wise to feed back to them
under the name of e.g. perl-big5plus.ucm?
You should in time and I should, too, because I have expanded UCM a
little so that you can define combined characters commonly seen in
Mac*. But I don't see any reason to be in hurry for the time being.
If any of you are a member of team ICU you may redirect this dialogue to
your team so we can work together in future (after 5.8.0, that is).
Dan the Encode Maintainer
