We generally do not encourage export from Sword Modules to something
else. The reason is to avoid the growth of Chinese whisper like ever
worsening errors and information loss.
All our modules have the source website/organisation in the
configuration file. You can usually obtain the text from there and
create any other format you wish.
Peter von Kaehne
CrossWire volunteer
The SWORD Project has utilities, available at
http://www.crosswire.org/ftpmirror/pub/sword/utils/win32/.
You can download sword-utilities-1.6.2.zip
Inside you will find mod2osis.exe
This will give you a start on the XML.
However, you would probably be better off finding the original source of
the SWORD module in the first place. This is usually listed in the
.conf file.
You can also get developer information for SWORD at
http://www.crosswire.org/sword/develop/index.jsp
Here you can sign up for the SWORD developer list, if you want.
Peace,
David
mod2osis is lossy.
There is significant loss of information in the circle - OSIS-XML ->
Sword module -> exported OSIS XML
The first step ignores info which is of no relevance to our modules, the
latter, most painfully loses information on verse linkage.
This is not a way you would want to go. Unless you would want to
contribute to the plethora of rotten and deteriorating Bible texts on
the internet.
Peter
Usually the best thing to do is use the Sword libraries and API to
parse the modules, letting it do the dirty work with it's own format
rather than trying to re-invent the format parsing wheel yourself. If
you explain a little more what you are trying to accomplish folks here
might be able to make more specific software architecture suggestions.
Caleb
2012/1/2 evstevemd <mwinj...@gmail.com>:
> --
> You received this message because you are subscribed to the Google Groups "Open Scriptures" group.
> To post to this group, send email to openscr...@googlegroups.com.
> To unsubscribe from this group, send email to openscripture...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/openscriptures?hl=en.
>
The documentation of libsword is not grand, but it is all there.
There is
a) the wiki
b) a large set of code examples (within the source)
c) source comments
d) API documentation
e) the mailing list sword-devel
f) the existing frontends which make use of the API.
Peter