[sword-devel] AmTract Encoding

Chris Little chrislit at crosswire.org
Thu Oct 25 13:37:13 MST 2007

No, this is not a bug. When we say Latin-1, we in fact mean Windows code 
page 1252. There should be a function somewhere within sword to convert 
this to UTF-8.

Not having a value set means use the default value, which for encoding 
is "Latin-1".


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 at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

More information about the sword-devel mailing list