Subject: Re: i18n of abiword -- charset mapping
From: Pruet Boonma (pruet@eng.cmu.ac.th)
Date: Sun Jan 16 2000 - 02:55:06 CST
Quoting Justin Bradford <justin@ukans.edu>:
> > general hint
> > ------------
> > Insofar as we\'re likely to need a bunch of to/from conversions between
> > Unicode and various charsets or codepages, it seems like we may need a
> new
> > set of efficient mapping classes which can be used for both purposes. As
> a
> > quick-and-easy XP solution, the usual table-driven macro magic with
> header
> > files ought to work nicely here, so long as we\'re willing to compile the
> > tables into the code.
> >
> > Since these tables can be quite sizeable, it\'s probably worth debating
> the
> > proposed approach and APIs on this list before implementing them.
>
> iconv does charset mapping. We can convert input to unicode, and then
> later, if the font requires it, convert to some other charset encoding.
>
> This is fairly standard thing, I believe, but many implementations aren\'t
> very good. This is used in wv, and Caolan has his own implementation for
> bad OSes. It might make sense to use native iconv/Caolan\'s backup for this
> purpose, rather than creating yet another set of tables.
I think that Caolan already at tis-620<->unicode in wv. And if we can use it so we did not require
other translation table.
pruet
>
> Of course, there might be other requirements I\'m missing, but from my
> understanding of the problem, iconv is all we need.
>
> Justin
>
This archive was generated by hypermail 2b25 : Sun Jan 16 2000 - 02:54:02 CST