View Single Post
Old 04-14-2007, 09:13 AM   #24
wallcraft
reader
wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.
 
wallcraft's Avatar
 
Posts: 6,977
Karma: 5183568
Join Date: Mar 2006
Location: Mississippi, USA
Device: Kindle 3, Kobo Glo HD
Quote:
Originally Posted by wagnerian
I'm wondering how I can configure it to enable Korean encoding.
I asked on FBReader's Google Group and the answer is:

Quote:
FBReader uses 2 different modules for support character encodings.

The first module uses standard iconv modules. You can compile additional iconv modules and put it on your device. I think, this is the best way.

The second one uses xml files with encoding descriptions located in /usr/share/zlibrary/encodings (or something like, this name is valid for desktop version). You can create an additional xml file for Korean encoding and put it in your FBReader package.
On my Pepper Pad 3, the command
iconv --list
lists a huge number of encodings but perhaps there are fewer on the iLiad (or in the iLiad tool chain).

Also, the GNU libiconv supports four Korean encodings (EUC-KR, CP949, ISO-2022-KR, JOHAB) and so this may be missing from the iLiad.

Last edited by wallcraft; 04-14-2007 at 09:26 AM.
wallcraft is offline   Reply With Quote