[sword-devel] Font problem in conf file

johnduffy at cgcf.net johnduffy at cgcf.net
Wed Dec 2 05:27:56 MST 2009

Thanks Eeli,

I've since opened the Net Bible UTF-8 conf file in Notepad++ and saved it as
a different filename for the Bible in Irish.  Then, erased the text, and
wrote it all in from the keyboard as I did for an ANSI version similarly
beforehand.  Now, this file works in Xiphos, is visible in BibleDesktop, and
also appears in BibleCS (although with the incorrect diacritics as before in
my previous UTF-8 conf files).  So it appears that while my previous UTF-8
files were just that, and some converted using tools, there is now a
difference which makes this one work.  There seems to be a problem with file
format being UTF-8 but character format being different, which I was not
able to get to the bottom of.  But since this is sort of working (apart from
diacritics in BibleCS, like Net Bible also), I'll leave it at that for the

The Bible module files also appear as UTF-8 in Notepad++, and the Bible text
appears correctly in BibleCS, Xiphos, and BibleDesktop.

P.S. even with the svnr1972 beta of BibleTime I still cannot navigate to
anything other than Rev 1:1 in any Bible version.
John Duffy

> -----Original Message-----
> From: Eeli Kaikkonen [mailto:eekaikko at mail.student.oulu.fi] 
> Sent: 02 December 2009 11:58
> To: johnduffy at cgcf.net; SWORD Developers' Collaboration Forum
> Subject: Re: [sword-devel] Font problem in conf file
> On Wed, 2 Dec 2009 johnduffy at cgcf.net wrote:
> > It seems that the conf file text must be limited to the basic ASCII
> > character set, and saved in ANSI format.  Is this correct?  
> Or, I could be
> > making a silly mistake on the encoding (files attached for 
> comparison).
> >
> > Help much appreciated.
> I think there's no definitive answer to that. Plain ASCII isn't enough
> in any case. See 
> http://www.crosswire.org/wiki/DevTools:confFiles which
> tells that actual utf8 characters are preferred IF the module has
> Encoding=UTF-8. Howver, it's not clear if this can be interpreted to
> mean also other encodings in some way, e.g. must iso8859-1 encoded
> module has also iso8859-1 encoded .conf file. I would say yes, so that
> Encoding= field would always describe both the module and the 
> conf file.
> If the Encoding is UTF-8, the conf file has utf8 characters and a
> fronted doesn't show it properly, then it's a bug in the frontend.
>   Yours,
> 	Eeli Kaikkonen (Mr.), Oulu, Finland
> 	e-mail: eekaikko at mailx.studentx.oulux.fix (with no x)

More information about the sword-devel mailing list