Subject: Re: Patch: Multi-encoding Text import/export
From: Andrew Dunbar (email@example.com)
Date: Mon May 21 2001 - 03:12:54 CDT
Vlad Harchev wrote:
> On Mon, 21 May 2001, Hubert Figuiere wrote:
> > According to Vlad Harchev <firstname.lastname@example.org>:
> > >
> > > In fact, the native encoding of RTF (as specified by \ansicpg) is ignored by
> > > word itself - it uses current font charset (specified by \fcharset) when
> > > interpreting non-unicode characters (i.e. the ones, not specified with
> > > \uNNNN).
> > But RTF can have encoding specified by \mac \ansi \pc or \pca kerwords.
> > And Abiword does handle this correctly as well as word. When storing Abiword
> > does use \ansi
> > \ansicpg is an extension used to have more encodings as the need raised years
> > later
> It seems that \ansicpgNNN etc are ignored by word (or at least by wordpad
> from windows95) - they interpret characters using charset of the font in
> current group (charset of the font is specified by \fcharset) and completely
> ignore argument of \ansicpg. Abiword on the other hand is fully driven by the
> argument of \ansicpg and completely ignores \fcharset when parsing rtfs - and
> we even have an issue in bugzilla that marks it as a bug, with nice test
> document (and I even commented on it there - AFAIK it's the only my comment in
> entire bugzilla :). But AbiWord sets \fcharset argument correctly when
> exporting rtfs.
> So \ansicpg seems to be obsolete.
I'm just about to submit a patch for the \fcharset problem. What
other software besides MS Wordpad and MS Word use RTF? I'd like to
run a few tests.
-- http://linguaphile.sourceforge.net _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b25 : Sat May 26 2001 - 03:51:05 CDT