<div dir="ltr">
<div>Hi all,</div><div><br></div><div>David, the OSIS ID "!" extensions that
you mention are not really a good way to handle this in theory, as they
are "work-specific" and they are ways to reference portions of verses :
by nature, they might be used for internal references (a note text
referencing a subverse in the same document) but they will completely
break the verse mapping features across bibles.<br></div><div><br></div><div>Usually,
when you have lettered verse numbers in a text, these denote actual
verses that were included from a different text source. They should
still have a unique OSIS ID, and be mappable individually.</div><div>The
typical use case I reported a while ago is the deuterocanonical
contents in Daniel and Esther : in pretty much all french catholic
bibles, the verses that are present in LXX but not in the hebrew sources
are using lettered verse numbers (eg. Esth 3:13a to 13g containing the
text of the letter, etc.)</div><div><br></div><div>There are two possible ways of handling it :</div><div><br></div><div>1/
The sword-compatible hack : Ignore the lettered verse numbers, and
consider the text of all these verses as suffix of the previous verse.</div><div>(eg. Esth 3:13 becomes one very long verse).</div><div>Then, this huge verse is a mess, but the mapping of the rest of the text keeps working.</div><div>I
think that's what Cyrille has been using in the past, and according to
Troy's answer above, this is what osis2mod might generate if you do use
work-specific suffixes in your source OSIS.</div><div><br></div><div>2/ The correct OSIS way, unsupported by sword : Declare all verses individually in sequence.</div><div>(eg. Esth 3:13a gets the OSIS ID Esth.3.14, etc.).</div><div>Then,
your chapter will have many more verses than what the sword
versifications allow, therefore osis2mod will merge all the end of the
book into the last verse.<br></div><div>This is what Pierre's example shows : the end of the 1Kgs 2 has been merged into the last verse 46.</div><div><br></div><div>The good solution would be for Sword to provide a correct versification for this bible.<br></div><div><br></div><div>Given
that here we're talking about the official LXX module, which contains
one of the most well-known and influential versions of the bible, for
sure we
should have a versification defined that exactly matches this base text.<br>Either
updating the LXX versification, or defining a new one if we're worried
about breaking other existing modules that might use the current LXX
versification.</div><div><br></div><div>(and
for lesser known bibles where we don't want to maintain a hardcoded
versification in sword, I've already proposed a strategy to allow
dynamic and modular versifications, but I'll sound like a broken record
if I keep mentioning it again - if you are interested we have a private
mail thread with DM Smith and a few other people to discuss the
necessary changes.)</div><div><br></div><div>Cheers,</div><div><br></div><div>Arnaud</div><div><br></div><div>PS : On an unrelated note, would it be possible to configure the DNS blacklist of this mailing list to be a bit less agressive ? Every time I write to this mailing list, I have to retry 2, 3, 4 times or more until it goes through, because "droneBL" seems to have blacklisted 70% of GMail's SMTP servers...</div><div><br></div>
</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Le jeu. 20 févr. 2025 à 13:57, Troy A. Griffitts <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Just a quick note:<br>
<br>
The engine parser has a 'suffix' concept so it understand John 3:16a -> <br>
John 3:16 (suffix a)<br>
<br>
I don't remember what osis2mod does, but I think it (or another of our <br>
tools, e.g., imp2vs) may join all the suffix parts of a verse together <br>
and place a literal (a), (b), (c)... at the start of the section. This <br>
is only for the benefit of the user and not anything which is separate <br>
in the engine. None of this is ideal, but just an small effort to meet <br>
these exceptions with some kind of reasoning (even if not ideal).<br>
<br>
On 2/20/25 12:28 PM, pierre amadio wrote:<br>
> Hi there.<br>
><br>
> Cyrille informed me about this issue:<br>
> <a href="https://github.com/crosswire/xiphos/issues/1172" rel="noreferrer" target="_blank">https://github.com/crosswire/xiphos/issues/1172</a><br>
><br>
> According to Karl,<br>
> """<br>
> The deeper problem causing this mess is that LXX 1Kings 2 is pretty<br>
> braindamaged. Do mod2imp LXX > /tmp/lxx.imp and look at 1Kings 2. The<br>
> markup ends with a ridiculously long single verse 2:46, with nothing<br>
> thereafter intervening from vv. 47-71 and 3:1, then picks up normally<br>
> again at 3:2. Somebody botched this one pretty badly.<br>
> """<br>
><br>
> In the source file used to build the module, 1Kings ends with some<br>
> verse that have a funny index: it contain alphanumeric entry:<br>
><br>
> 2:46<br>
> 2:46a<br>
> 2:46b<br>
> 2:46c<br>
> ... and so on until the end of the chapter.<br>
><br>
> And chapter 3 starts directly with verse 2<br>
> <a href="http://ccat.sas.upenn.edu/gopher/text/religion/biblical/lxxmorph/14.1Kings.mlxx" rel="noreferrer" target="_blank">http://ccat.sas.upenn.edu/gopher/text/religion/biblical/lxxmorph/14.1Kings.mlxx</a><br>
><br>
> It is the same on a paper version (Septuaginta, A Reader's Edition),<br>
> so I am assuming it is not a mistake.<br>
><br>
> I can rebuild a LXX module with empty verses where there are missing<br>
> ones such as in 1Kings 3:1 (that is already the case for Odes which is<br>
> dealt with already. I plan to make a global check for all books and<br>
> chapters, just to be safe).<br>
><br>
> What about the alphanumerical verse numbering ?<br>
> Right now, i simply ignore any alphabetical character when switching<br>
> from the imp format to the xml one:<br>
><br>
> <a href="https://github.com/pierre-amadio/LXX/blob/main/bin/imp2xml.py#L48" rel="noreferrer" target="_blank">https://github.com/pierre-amadio/LXX/blob/main/bin/imp2xml.py#L48</a><br>
><br>
> This ends up with several verse nodes having the same osisID in the<br>
> final xml file.<br>
><br>
> What should be the ideal way to deal with those ?<br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
> <a href="http://crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" target="_blank">http://crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" target="_blank">http://crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote></div>