<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 10, 2020 at 4:08 PM Philip White <<a href="mailto:philipwhite@cedarville.edu">philipwhite@cedarville.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I'm interested in building a linux command line module viewer. From<br>
the wiki and the FAQ, it seems that the only way to work with the<br>
modules available from the website is to use the SWORD library. If the<br>
raw OSIS files were available, then I think I could write a<br>
low-dependency piece of software (counting all dependencies) since I<br>
will probably not use everything that the library provides.<br></blockquote><div><br></div><div>Sword is a very low dependency piece of software. The only dependencies I know of are optional: ICU, cURL and CLucene, mostly. It's tough to get much lower dependency than Sword. Also, there is already a command line viewer included with Sword that is very featureful: diatheke.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Is there a place I can get OSIS modules for something like the KJV<br>
with Strong's numbers module? My understanding is that the modules<br>
format acts as a sort of DRM for those modules that need to have some<br>
copyright protection. However, a lot of Bibles, commentaries, and<br>
books are public domain, so there would be nothing preventing the<br>
distribution of the OSIS files.<br></blockquote><div><br></div><div>Crosswire maintains the OSIS for the KJV module. However, other sources could come from any number of different locations. You'd have to check every conf module independently to determine if it mentions where the source files are. Some do, some do not. For some the source could come from a different format (e.g. ThML, GBF, plain-text, Sword's proprietary imp format, etc).<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
In summary, my question is how I can obtain the files in the<br>
standardized OSIS format instead of the undocumented modules format<br>
that modules on the website come in.<br></blockquote><div><br></div><div>This is the beauty of the Sword library. It hides all the rest of those questions:</div><div>1) Which format did it come from? OSIS? ThML? Who even knows?</div><div>2) What is the source of the original text? Could be nearly anywhere.</div><div>3) What is the source encoding? Could be lots of things. Sword will normalize this all to UTF-8 for you.</div><div><br></div><div>I would highly encourage you to use the Sword library itself. It's already a very small, very dependency-weak library. You may be surprised at how easily it ports to all manner of destinations.</div><div><br></div><div>--Greg<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Thanks,<br>
Philip<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote></div></div>