On Sun, 2002-05-05 at 21:00, Tomohiro KUBOTA wrote: > At 02 May 2002 23:54:37 +1000, > Roger So wrote: > > Note that the source from Li18nux will try to use its own encoding > > conversion mechanisms on Linux, which is broken. You need to tell it to > > use iconv instead. > > I didn't know that because I am not a user of IIIMF nor other Li18nux > products. How it is broken?
The csconv library that IIIMF comes with doesn't work properly (at least I didn't get it to work), possibly because of endianess issues. csconv is meant to be a cross-platform replacement for iconv. > > Maybe I should attempt to package it for Debian again, now that woody is > > almost out of the way. (I have the full IIIMF stuff working well on my > > development machine.) > > I found that Debian has "iiimecf" package. Do you know what it is? It's the IIIM Emacs Client Framework. As the name implies, it's an implementation of an IIIM client in Emacs. I've never tried it out, as I don't use Emacs. :) Is it used by anyone? Last time I checked, popularity-contest said nobody was using it... > > I _do_ think xkb is sufficient for Japanese though, if you limit > > "Japanese" to only hiragana and katagana. ;) > > I believe that you are kidding to say about such a limitation. > Japanese language has much less vowels and consonants than Korean, > which results in much more homonyms than Korean. Thus, I think > native Japanese speakers won't decide to abolish Kanji. > (Please don't be kidding in international mailing list, because > people who don't know about Japanese may think you are talking > about serious story.) Sorry, it wasn't meant to be a serious comment. :) Cheers Roger -- Roger So Debian Developer Sun Wah Linux Limited i18n/L10n Project Leader Tel: +852 2250 0230 [EMAIL PROTECTED] Fax: +852 2259 9112 http://www.sw-linux.com/ -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
