Jeremy, We use cp1252 (Microsoft's extension of iso8859-1, aka Latin 1) or utf8 as the encoding for the modules. The <92> indicates that it is cp1252. When the Encoding= is missing from the conf, then the file should be understood Encoding=Latin1.
Try changing to a font that includes Microsoft's extensions to Latin 1. You can get the MS fonts by following the instructions here: http://corefonts.sourceforge.net Hope this helps, DM Jeremy Erickson wrote: > Hi, > I noticed that some of the keys in the AmTract lexicon module (such > as "Abraham's Bosom") have apostrophes that don't work properly in the > frontends. In BibleTime (or at least the development code), the apostrophes > show up as boxes, and the contents are not fetched. GnomeSword actually > crashes when attempting to access those entries. I opened the raw > amtract.dat file in Vim and did "set encoding=latin1", which showed the > apostrophe as a "~R" (this being an indicator that it was some sort of > nonprinting character.) Upon "set encoding=utf8", it shows up as "<92>", > which is another indication of a nonprinting or unavailable character. Thus, > it seems the encoding is neither UTF8 nor Latin1. The amtract.conf file has > no "Encoding=" line. > Is this a bug in the module? > > -Jeremy Erickson > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
