BUG: Passage List has different verse count to Search

Bible Search on happened in Lexham LXX Interlinear (by verse) and the associated PL gave a different "passage" count. The count was different no matter what search options I tried e.g. Match all word forms, All Text, lexval, literal.
Got agreement when I searched on saved (by verse)
Searches in LGNTI or ESV with those words gave the same verse counts.
I noticed that the PL count was equal to a Search by Grid - so that may put the problem elsewhere. But it's an issue that PL cannot reproduce the Search count!
Also note that Versification differences similar to above occurred throughout the PL.
Why are LXX-R Genesis 35:16 & LXX-R 3 Kingdoms 11:43 at the end of the PL, even after Sorting?
Dave
===
Windows 11 & Android 13
Comments
-
BUMP.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Bible Search on happened in Lexham LXX Interlinear (by verse) and the associated PL gave a different "passage" count. The count was different no matter what search options I tried e.g. Match all word forms, All Text, lexval, literal.
I can reproduce this problem and have filed a bug.
0 -
Can anyone account for the versification/verse map differences?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Can anyone account for the versification/verse map differences?
From a quick look, it appears to be due to the Letter of Jeremiah; Grid displays it as one verse, but Verses as multiple rows. The resource itself doesn't show the verse numbers when scrolling through LXX, so it may be a tagging error in the resource.
0 -
The Lexham LXX Interlinear resource is still in beta; there is a Known Issues section in the front matter that covers the places where the resource is incomplete. It also hasn't been updated to use the new verse maps supported by Logos 4 (which explains why the versification is inaccurate); this will be addressed once the translation is complete.
We'll check if the logic in the Grid and Verses searches can be unified to give the same verse counts, but the real answer may be just to wait until that resource is finished.
0 -
Thanks for the explanation Bradley.
Dave
===Windows 11 & Android 13
0