<div dir="ltr">I had submitted a Python script somewhere that simply walks through every versification in the Sword library and reports the number of extra/missing verses in a given OSIS file relative to each versification with a per-Testament breakdown. For instance it might give output similar to the following:<div><br></div><div>Old Testament:</div><div>3 verses found in file not in versification</div><div>1 verse found in versification not found in file</div><div><br></div><div>New Testament:</div><div>12 verses found in file not in versification</div><div>0 verses found in versification not found in file</div><div><br></div><div>That script still exists somewhere, although it might need to be tweaked if you're running the newest versions of the library. It doesn't lend itself well to automation, but you can use the output to select a versification for each module and feed it into any of your automation systems.</div><div><br></div><div>--Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Aug 23, 2015 at 4:00 PM, Kahunapule Michael Johnson <span dir="ltr"><<a href="mailto:Kahunapule@ebible.org" target="_blank">Kahunapule@ebible.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class="">
<div>On 08/23/2015 08:27 AM, Matěj Cepl
wrote:<br>
</div>
<blockquote type="cite">
<pre>On 2015-08-23, 09:29 GMT, Peter von Kaehne wrote:
</pre>
<blockquote type="cite">
<pre>Interesting and quite probably useful would be to know if any
'colonial' translations would benefit from any of these three
v11ns. I do think Malagassy was difficult to fit, also
Kahunapule might have translations from French Polynesian
background. </pre>
</blockquote>
</blockquote>
<br></span>
Yes, I have a variety of difficult-to-fit translations. Mostly this
has convinced me that <b>hard-coded versification is bad</b>. This
is especially true when you consider intentionally omitted verses
for textual criticism reasons, which set tends to vary based on who
is analyzing the text and making the translational decisions.<span class=""><br>
<pre></pre>
<blockquote type="cite">
<pre>There were some talks about script which would take a given OSIS
XML (or something else) and tries to match the text against all
available versifications looking for the best match. Does such
animal exist at all? Is it possible?</pre>
</blockquote>
<br></span>
Yes, this algorithm exists as part of <a href="http://haiola.org" target="_blank">Haiola</a>
(next release). It picks the least bad versification of those
available (i.e. hard coded into the version of the Sword Library
that I'm using). Badness is minimized as follows:<br>
1. Select the versification(s) with the minimum number of verses in
books not in the versification. (This narrows things down when
deuterocanon/apocrypha books are present.)<br>
2. Of those selected in step 1, select the versification(s) with the
minimum number of verses in chapters not in the versification. (Some
versifications lack Malachi 4, for example.)<br>
3. Of those selected in step 2, select the versification(s) with the
minimum number of verses that extend beyond the expected number of
verses in their chapter.<br>
4. Of those selected in step 3, select a versification with the
minimum number of verses defined in the versification but not
present in the current text.<br>
<br>
The actual implementation is more efficient than the above would
seem to indicate, as it does it with one pass through the Bible,
counting the misfits in each category, then one pass at the end
finding the least bad fit.<br>
<br>
The real issue, here, is how well Sword handles each category of
badness. It turns out that badness levels 1 and 2 are pretty bad.
Badness level 3 just results in some verses being combined with the
previous verse-- maybe several verses combined. Badness level 4
isn't really that bad, and is, in fact, pretty much unavoidable
unless you go with per-module versification, because we have lots of
partial translations, like sometimes just one or two books of the
Bible. The only reason I retain that test is to select KJV instead
of KJVA, SynodalP instead of Synodal, and NRSV instead of NRSVA for
Bibles with just the regular canon of 66 books or a subset of that.<br>
<br>
I'm also aware of some other scripts that try to find the best fit,
but they aren't as general or reliable as the above algorithm.<span class="HOEnZb"><font color="#888888"><br>
<div>-- <br>
<table border="0" cellpadding="7" cellspacing="3">
<tbody>
<tr>
</tr>
<tr>
<td><img src="cid:part2.01030805.04090705@eBible.org"></td>
<td><font size="4" color="#000000">Your partner in
electronic Bible publishing,<br>
<img src="cid:part3.01080705.01000106@eBible.org"><br>
</font></td>
</tr>
</tbody>
</table>
<table border="0" cellpadding="7" cellspacing="3">
<tbody>
<tr>
<td style="background:rgb(255,255,0)"><font color="#000000"><b>MICHAEL JOHNSON<br>
PO BOX 881143<br>
PUKALANI HI 96788-1143</b><br>
USA</font></td>
<td style="background:rgb(0,255,255)"><font color="#000000">
<a href="http://eBible.org" target="_blank">eBible.org</a><br>
<a href="http://MLJohnson.org" target="_blank">MLJohnson.org</a><br>
Mobile: +1 <b><a href="tel:808-333-6921" value="+18083336921" target="_blank">808-333-6921</a></b><br>
Skype: kahunapule</font></td>
</tr>
</tbody>
</table>
</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>