Thanks for all the info. On the last point, I did mean read directly from USFM. I don't know the format well-enough, but presumably if other software uses it, then maybe we could have a go at displaying the best we can...<div>
Chris</div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 8 November 2012 10:17, 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">Hi Chris,<br>
<br>
> Von: Chris Burrell <<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>><br>
<div class="im"><br>
> I've found some instructions on transforming usfm/x to osis on the wiki<br>
> but<br>
> was wondering how difficult it would be to automate a lot of it?<br>
<br>
</div>Several of us have been starting to think and experiment with this too.<br>
<br>
Basically it is easy to automate as such. The problem is around cleaning up.<br>
<br>
There is a thread earlier this year where some of this was discussed. The basic plan is to use a git repository and git hooks with scripts attached to that. Some infrastructure is up, but not much else has happened yet.<br>
<div class="im">><br>
> is it such that there is too much manual cleaning up?<br>
<br>
</div>Manual/mechanical cleaning up is a huge need, unfortunately. I have not yet encountered a truly clean USFM text, despite all claims by various USFM experts.<br>
<div class="im">><br>
> also, I was wondering if there's any appetite in developing a driver to<br>
> read such modules, within sword or jsword...<br>
<br>
</div>You mean to read directly USFM?<br>
<span class="HOEnZb"><font color="#888888"><br>
Peter<br>
</font></span></blockquote></div><br></div>