Subject: Re: POW -- which locales Just Work?
From: Vlad Harchev (firstname.lastname@example.org)
Date: Thu Mar 01 2001 - 10:22:05 CST
On Thu, 1 Mar 2001, ha shao wrote:
> On Thu, Mar 01, 2001 at 04:09:52PM +0400, email@example.com wrote:
> > >
> > > 8. The resulting document gets saved as Unicode, if necessary, rather than
> > > in some platform-specific charset. This file can be opened and read
> > > properly on a different platform. (For example, Russian documents
> > > authored on Windows can be read on Linux, and vice versa.)
> > From this sentence one may think that saving in unicode is a better approach
> > than saving in native charset. It's wrong - since the charset is specified in
> > the xml header, storing documents in any charset will work fine (as long as
> > importing system's iconv understands that encoding). All that is needed is to
> > detect "current" encoding (used when exporting to .abw) correctly on all
> > platforms (so correct charset name is written to xml header). It seems that
> > charset detection is properly implemented only on unix currently (I wish to be
> > wrong - I didn't examine non-XP non-unix code closel).
> Well, maybe it is true for libxml version. But for expat version,
> CJK native encoding cannot be imported now. Besides, abiword
> exports CJK .abw characters as &xxxx; instead of native encoding.
> I had a patch to export CJK native characters but since I tried
> and failed to import them (with encoding=GB2312 set), I put it
> on hold now.
Yes, AW exports CJK chars as &xxxx; - it's trivial to export them in utf8 -
if it's more preferable. AW exports chars in native encoding only under utf8
locales. It would be nice if you drope a wishitem about this a week ago..
> I did not try link abiword with libxml yet. It segfault on me
> somewhere a few days ago.
Me too. I've stuck to expat.
> Best regard
This archive was generated by hypermail 2b25 : Thu Mar 01 2001 - 11:22:22 CST