<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi guys,<div class="">Sorry if this is the wrong place.</div><div class=""><br class=""></div><div class="">There is an old version of the Open English Bible on the website which needs updating. Someone helped me creating the modules a few years back.</div><div class=""><br class=""></div><div class="">I’m currently trying to automate building the OEB as much as possible so that we can put out more regular updates. Source is in USFM (which should be compliant now) and I have software which parses USFM using a python parser framework and can then spit out RTF, PDF, HTML etc etc with pluggable renderers [1]. The software isn’t OEB specific - it should handle most USFM - though it hasn’t been tested that much on other sources.</div><div class=""><br class=""></div><div class="">I would like to integrate this with the SWORD framework so that new OEB versions can be pushed out with as little human input as possible but I’m not sure what the recommended process is.</div><div class=""><br class=""></div><div class="">At the moment I don’t generate OSIS but could do that fairly easily if I had some help on what the OSIS should look like, or I could integrate with an existing USFM->OSIS generator.</div><div class=""><br class=""></div><div class="">Best wishes,</div><div class="">Russell</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">[1]: <a href="https://github.com/openenglishbible/USFM-Tools" class="">https://github.com/openenglishbible/USFM-Tools</a></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>