<div dir="ltr">Remeber that we have Crosswire's github organization living at <a href="https://github.com/crosswire">https://github.com/crosswire</a> :)</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 17, 2015 at 11:02 AM, Peter von Kaehne <span dir="ltr"><<a href="mailto:refdoc@gmx.net" target="_blank">refdoc@gmx.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Dear all,</div><div><br></div><div>For the last few months John Austin, some friends of his, myself and others have worked on getting our usfm - to - osis process onto a safer and more solid footing. </div><div><br></div><div>There remains still a lot of work. </div><div><br></div><div>This is where we are right now:</div><div><br></div><div>We ran a small git repository which contains a set of makefiles and scripts on our own gitosis install on CrossWire server. This has now moved to GitHub to improve external contributions and general workflow. The "canonical" repository is under my name</div><div><br></div><div><a href="https://github.com/refdoc/Module-tools" target="_blank">https://github.com/refdoc/Module-tools</a></div><div><br></div><div>Much development of usfm2osis.py and XSL files will happen in John Austin's branch. These will from time to time merged back into the "canonical" repo.</div><div><br></div><div>The main scripts in it are usfm2osis.py, <a href="http://xreffix.pl" target="_blank">xreffix.pl</a> (which undergoes a complete SAX based rewrite, which will be uploaded shortly), several XSLT sheets and 2 main makefiles, which both should take a source straight to a published module. One from USFM, the other from externally produced OSIS.</div><div><br></div><div>We also will hold on to a local copy of u2o.py by Ryan (adyeths), which we will continue to test heavily (+ produce lists with issues found). At this moment we will not use it to replace usfm2osis.py. This is the current consensus of discussions between John and me, mostly. The reasons for this are manifold and not suitable for here, but the matter remains obviously under discussion. In short we are not wedded to any particular usfm-to-osis process, but will continue with the devil we know until we are sure a jump to any other script is safe and gives more long term perspective.</div><div><br></div><div>I will merge back regularly the Github repo into our CrossWire git repo, but will remove write access to it for all but myself to ensure all development happens on Github. DM wants to make that repo also visible for general reading, but this has not happened yet. </div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Peter</div><div><br></div><div><br></div><div><br></div></font></span></div><br>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">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><br></div>