Hello, I don't know if this helps or if you already found what you, but I noticed no reply. I was looking for similar information last week and was waiting to see what kind of replies you received. Here is what I learned from a little browsing.
The *.conf files show the file encoding format. Example, the kjv.conf has a line which reads SourceType=GBF I don't know what all formats their are but here are a few links. GBF http://www.ebible.org/bible/gbf.htm ThML http://www.ccel.org/ThML/ OSIS http://www.bibletechnologies.net/ module.conf http://sword.sourceforge.net/cgi-bin/twiki/view/Swordapi/ConfFileLayout I can't speak as to *.vss it looks like binary to me. ;) So it may not be necessary for you as you would probably implement its functionality within your own tools? And I haven't seen the NIV as it is locked. Hope this helps. This is the starting point I am taking for my project. Jimmie Houchin Curtis W. Ruck wrote: > I am working on a personal implementation of Sword for Java (I use linux > & winxp often). I know about the group working on Jsword, but I prefer > to write things my own way under the GPL. The only thing though, is I > can't find any module documentation. I first would like to start with > the text modules, get those implemented, browseable, searchable, etc... > Then get the other module types working. But, I can't figure out the > module file formats. Some rawtexts look decently easy to parse, but I > am clueless by the .vss files, other rawtexts look ugly like the NIV > beta rawtext from the ftpsite. > > Any starting blocks for these? I know a little C, no C++, and I really > wouldn't enjoy reading though Sword code, figuring out how to parse the > files.
