Subject: Re: Bug 1614
From: Andrew Dunbar (hippietrail@yahoo.com)
Date: Fri Jun 22 2001 - 21:02:29 CDT
Dom Lachowicz wrote:
>
> Quoting Andrew Dunbar <hippietrail@yahoo.com>:
>
> > I just looked at this bug regarding german characters in mac word
> > documents. It looks to me like wv library does not support mac
> > encodings which I expect the problem to be. Does anybody know if
> > where in the wv code? My best guess is in wvnLocaleToLIDConverter()
> > where nLocale has the value of 0x4d which is not handled.
> >
>
> Hey,
>
> in wv/text.c there are some functions that probably aren't handling the 0x4d
> value properly. My first guess is wvLidToCodePageConverter isn't handling the
> lid properly. wvnLocaleToLidConverter probably isn't to blame here, but you're
> more than welcome to try it.
It just struck me: 0x4d is 'M' which is indeed used as a font identifier
for Macintosh fonts, and from there extended to identify mac character
sets in all kinds of places before our modern concept of encodings
identified by strings. RTF uses this also is its /fcharset.
Time to get hacking!
Andrew.
-- 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 : Fri Jun 22 2001 - 21:00:23 CDT