<html>
<body>
(I don't know if you've already got this - I found it unsent in my Out
box)<br><br>
Thanks David. <br><br>
Yes, we will be using lots of modules. <br><br>
On your link I found an example: <br><br>
<pre><verse eID='Exod.22.2-Exod.22.4'/>
</pre>So I searched a bunch of modules (about 130) for
RegEx [0-9]-[A-Z]<br>
I found verse spans in lots of dictionaries & commentaries <br>
and in Bibles with notes & XRefs (eg ESV, LEB, Luther, NET, MHC)
<br>
But I didn't find any using verse spans like that described. <br><br>
Looks like something we should watch out for, but it won't occur often.
<br><br>
David IB<br><br>
<br>
At 13:28 20/11/2012, David F. Haslam wrote:<br>
<blockquote type=cite class=cite cite="">Hi David,<br><br>
The warning was mainly geared to modules other than ChiUn &
ChiUns.<br>
<i>I just thought you might have more stuff in the pipeline for Tyndale
STEP,<br>
so I didn't wish to leave you imagining that there were no pitfalls in
using the IMP format method.</i><br><br>
When I referred to a verse range, this is best illustrated in USFM
format.<br>
The extreme case I mentioned need not concern you, but in Paratext the
line began as follows:<br><br>
<tt>\v 12-83 blah blah .....</tt><br><br>
When converted from USFM to OSIS this sort of thing becomes much more
complicated.<br>
I already described the principles of linked verse ranges in this section
of a wiki talk page:<br>
<a href="http://crosswire.org/wiki/Talk:OSIS_Bibles#Linked_verses">
http://crosswire.org/wiki/Talk:OSIS_Bibles#Linked_verses</a><br>
<i>Albeit the reason for doing so was to correct a different
misapprehension arising in another translation conversion project.<br>
</i><br>
Paratext verse range tagging can be a nightmare! We've often seen things
like this:<br><br>
<tt>\v 2-6a followed by the text for verse 2 through the first half of
verse 6<br>
\v 6b-11 followed by the text for the second half of verse 6 through
verse 11</tt><br><br>
Converting such examples from USFM to OSIS is not so easy - and some
workarounds were usually required until now.<br>
Hopefully, Chris Little's new python script will cover such issues
properly - once it's been fully tested.<br><br>
These issues are unrelated to
<a href="http://crosswire.org/wiki/Alternate_Versification">Alternate
Versification</a>. Default v11n for SWORD modules is the KJV. <br>
Your reference to Num.17 was therefore not relevant - this chapter has 13
verses in both the KJV and the ChiUns Bibles.<br>
Admittedly the WLC module (Hebrew) has 28 verses in Num.17 - but none of
these are a linked verse range in the sense being discussed.<br>
cf. The WLC module is configured with
<tt>Versification=Leningrad</tt><br><br>
<br>
Best regards,<br><br>
David <br><br>
On 2012-11-20 11:54, David Instone-Brewer wrote:<br>
<blockquote type=cite class=cite cite="">Thanks for the warning!<br>
I guess the verse range is in Num.17 where there is a severe mismatch
between the KJV and Hebrew numbering. <br>
But presumably you don't mean that alternate versification makes it fall
over <br>
Could you give me an example of the coding for a verse range so I know
what to look out for? <br><br>
David IB<br><br>
<br><br>
At 10:36 20/11/2012, David F. Haslam wrote:<br>
<blockquote type=cite class=cite cite="">On 2012-11-19 14:47, David
Instone-Brewer wrote:<br>
<blockquote type=cite class=cite cite="">David, <br><br>
This is GREAT. I was concerned about <tt>mod2osis </tt>so this is really
helpful. <br><br>
David IB</blockquote><br>
Hi David,<br><br>
<u>Caveat</u>: Beware of this problem:<br><br>
<a href="http://www.crosswire.org/tracker/browse/MODTOOLS-31">
http://www.crosswire.org/tracker/browse/MODTOOLS-31</a><br><br>
This would affect modules that have linked verse ranges.<br>
Rebuilding using <tt>imp2vs</tt> would thus lead to some duplicated
verses in the module.<br>
One would require a workaround processing step to avoid this
outcome.<br><br>
For ChiUn and ChiUns, probably not a problem, as they follow the KJV
v11n.<br>
Only three KJV verses are not tagged in these 2 modules. See attached
output from <tt>emptyvss</tt>.<br><br>
Most more modern translations frequently have several or even many
Biblical passages tagged to a verse range.<br>
<font size=2>cf. The longest example I've come across to date was one in
which verses 12-83 were given one tag for a passage somewhere in Numbers.
:'( <br>
</font><br>
David</blockquote>
<dl>
<dd><tt>David IB
<dd>Â
<dd>///Â Â <font face="Arial Black, Helvetica">Dr David
Instone-Brewer</font>
<dd>dib  Senior Research Fellow in Rabbinics and the New
Testament
<dd>Â ^Â Â Â Tyndale House, 36 Selwyn Gardens, Cambridge, CB3 9BA,
UK
<dd>\=/Â Â
<a href="mailto:Rabbinics@Tyndale.cam.ac.uk">
Rabbinics@Tyndale.cam.ac.uk</a>Â Â Â Â Â
<a href="http://www.tyndalehouse.com/" eudora="autourl">
www.TyndaleHouse.com</a> </blockquote>
<x-sigsep><p></x-sigsep>
<dd>David IB
<dd>
<dd>/// <font face="Arial Black, Helvetica">Dr David
Instone-Brewer</font>
<dd>dib Senior Research Fellow in Rabbinics and the New
Testament
<dd> ^ Tyndale House, 36 Selwyn Gardens,
Cambridge, CB3 9BA, UK
<dd>\=/
Rabbinics@Tyndale.cam.ac.uk
<a href="http://www.tyndalehouse.com/" eudora="autourl">
www.TyndaleHouse.com</a>
</dl></body>
</html>