Chris Little wrote:
On Thu, 16 Jan 2003 [EMAIL PROTECTED] wrote:It will be interesting to see if the Sword Module system stabilizes in light of OSIS.
The above statement was actually mine.
Naive question alert...Sword will not be dropping any module formats as a result of OSIS. OSIS is being used as an import format at the moment. In the future, we might base additional formats on OSIS, but they will still be proprietary additions to the OSIS format (like indexes into the files). We don't intend to build a DOM parser into Sword.Similar to what others have suggested, you might think of just doing an OSIS reader and not try to read Sword modules. There are quite a few of them and you'll need to be quite familiar with C++ in order to understand the code that reads/writes them.
You mean I can't reverse engineer them from the text markup itself?
The Java frontend, does it use the Sword libraries or will there be Java code for reading Sword modules?
It is quite possible I am underestimating the task of reading/parsing Sword modules. I thought the modules/text/rawtext/***/ot modules/text/rawtext/***/nt were simply text files which the Sword libraries parsed to create what was sent to the front end.
Am I missing something significant?
Is all I need not in those files?
Thanks.
Jimmie Houchin
_______________________________________________
sword-devel mailing list
[EMAIL PROTECTED]
http://www.crosswire.org/mailman/listinfo/sword-devel
