dmsmith555 at yahoo.com
Fri Jun 11 10:27:53 MST 2004
I think that J-Sword's handling of modules is complex. Perhaps I am not
the best to comment but here is one anyway:
The general architecture of J-Sword is that there is a translator/parser
for each encoding of a module. When a passage is displayed it is parsed
and then converted into OSIS. The parsers are written to be somewhat
fault tolerant, but to my knowledge, they do not fix bad data. I have
found that in some cases the parsers just get confused. There is an
attempt to log faults that are found so that the original can be cleaned up.
I think I read in the archives that when Joe and others did the parser
work, they had to fix up a lot of the modules to get j-sword to work.
It should be fairly easy to write a mod2osis using j-sword. There is
sample code on how to do it for a passage in
tmp at nitwit.de wrote:
> Sword's mod2osis utility apparently is somewhat buggy at least it does not
> create valid XML. I'm new to jsword but as its source base is quite complex I
> want to ask if somebody has written a replacement for mod2osis or written a
> parser that corrects the invalid files.
More information about the jsword-devel