Troy A. Griffitts wrote:
Hey guys. A couple days back I added a new repository: crosswire-java for all the java tools we use on the site.Currently in the JSword repositories is a bunch of sword-java. Will you be moving that? I hope to get them all into a nice project and take out a bunch of silly hardcoded paths and such, then we can easily fix things like this. I doubt we're specifying an encoding when reading the conf files in, but don't remember. I'll try to have a look when I get this new project up and running. I'm in favour of defining a rule that says the .conf file is the same encoding as the module (defined by the Encoding= entry in the .conf) And since the default encoding is UTF-8According to http://www.crosswire.org/sword/develop/swordmodule/ the default is Latin-1, which was clarified by Chris in an earlier thread to be cp1252. Here is the excerpt from the page: Encoding is the encoding name for the module character encoding. Currently, the only supported values are Latin-1 and UTF-8. (Latin-1 is default, but UTF-8 is preferred.) Of the 290+ modules about 180 have an Encoding=UTF-8. I don't know if all of these use utf-8 for their conf, but I could check. All the others don't have the tag at all and therefore default to cp1252. I am guessing that alot of the remaining modules use 7-bit ascii and therefore are also utf-8. But that is neither here or there. , JSword could assume UTF-8 and only reread the ones that specify otherwise-- I don't think there are many modules that specify otherwise, but on handhelds and such, I don't want to remove the ability for alternate encodings. Ideas? |
_______________________________________________ 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
