BUG L6.11 B5: "non-bible text" not showing in some bibles in single line display

This bug exists in Logos Bible Software 6.11 Beta 5 - 6.11.0.0017 (32 bit) but in the stable 6.10 version as well. It has been reported in this thread: https://community.logos.com/forums/t/125023.aspx

In affected bibles, when "One verse per line" is selected, only bible text will be displayed, pericope headings etc. will be suppressed regardless of the "Non-Bible text" selection

(EDITED:)

Currently known affected bibles:

probably all PB bibles (regardless of language, such as SENT and ASV; even if freshly compiled with L6.11 beta 5, which I tested with NeÜ),
Authorized Version
Luther 1984 (German language)
NA27 (red LOGOSNA27 Greek NT)

(not affected: NIV 1984, NIV 2011, NRSV, NRSVCE, HCSB, ESV, LEB, NABRE, NASB, NET, KJV 1900, NKJV, The Message, Good News Translation, La Biblia de las Americas [Spanish language], Menge-bible, Schlachter-bible, Einheitsübersetzung [all three in German language], blue NA27GBS w/ apparatus, NA28, NA28GBS w/ apparatus, Byz 2005 [Greek])

As an example, see the following picture of three Greek New Testaments, all set to display "One Verse per line" and including "Non-Bible Text" (i.e. book, chapter, pericope headings as fas as contained in the bible). The latter is broken in the left bible, which means it's affected by the bug.

Another Example: AV (affected by the bug) vs KJV and NKJV (both not affected)

Note that display of "non-bible text" works in all affected bibles as it should when "one verse by line" is deselected.

Toggling display of "Bible text formatting", "Chapter/Verse Numbers" or "Footnote Indicators" where present has no effect on this i.e. is unrelated to the bug.

Find more posts tagged with

Comments

Chris Culy (Logos)

I've created a case to investigate this internally. We will post here when we have an update. Thank you for reporting this!

Vadim

https://community.logos.com/discussion/comment/815678#Comment_815678

Any update on this issues? Should be a quick fix.

NB.Mick

https://community.logos.com/discussion/comment/837075#Comment_837075

Any update on this issues? Should be a quick fix.

The bug still exists in the most-current beta, L6.14 B4:

Philana R. Crouch

https://community.logos.com/discussion/comment/837134#Comment_837134

NB. Mick,

The team has taken a look at this issue with the NA27 and older Bibles, and this feature is not compatible with those resources.

Vadim

https://community.logos.com/discussion/comment/837269#Comment_837269

Is there anything that can be done in tagging personal Bibles to enable this feature?

Perhaps a specific tag must be given to the headings?

NB.Mick

https://community.logos.com/discussion/comment/837269#Comment_837269

NB. Mick,

The team has taken a look at this issue with the NA27 and older Bibles, and this feature is not compatible with those resources.

I don't understand this rationale. We are talking about a bug, not a new feature for new resources. I don't even understand how you accomplish introducing a bug in the bible display that affects a subset of bibles with no shared characteristics. But it's not that they are "old". NA27 is the text basically all contemporary bibles are built on. The NA27 resource is from 2015. Luther 1984 is the top-of-the line German language bible (the only German bible with a RI), last built less than a year ago also in 2015. PB bibles are built all the time, they are not "old" and the PB compiler renders a buggy bible even today in the latest beta. So "older bibles" and "feature is not compatible" doesn't sound like a reasonable explanation, but a sorry excuse. If the PBs were working, and the new Lu84, and you were telling this tale only concerning old resources like the SESB-delivered bibles from Ye Old Libbby Days I'd agree in an instant. But here it's different. "The team" wrote buggy software and now refuses to fix that - which shows contempt for international customers and for those who rely on Bob's promise that PBs are not second-class resources.

The specific bug is nothing I lose sleep over. But the attitude leaves me disappointed. And I fear for the PB compiler in the long run.

Vadim

https://community.logos.com/discussion/comment/837299#Comment_837299

NB. Mick,

Let us remember that

"the fruit of the Spirit is love, joy, peace, patience, kindness, goodness, faithfulness,

gentleness, self-control; against such things there is no law." - Gal. 5:22-23

I trust that the Logos team will get this fixed.

Blessings!

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/837299#Comment_837299

In order for the VF to display both "Non-Bible text" and "One verse per line", the display has to hide the regular chapter and verse numbers encoded in the text, so it can display the verse numbers in the margin. This requires the chapter and verse numbers to be tagged so they can be hidden independently of the other non-Bible text.

If the Bible doesn't contain that tagging, the two options are incompatible, and turning on "One verse per line" has the side effect of hiding all non-Bible text, regardless of that VF setting. (The other way of implementing it would have been to duplicate the chapter and verse numbers in the one-verse-per-line display; I assume the person who wrote the feature thought that would be a worse outcome.)

I think Philana was trying to summarise the current state of the program, not justify it.

When this bug was written up in our internal system, three action items were proposed:

Fix the VF UI so that these mutually exclusive options aren't shown for resources that can't support them
Rebuild the resources that lack the chapter and verse number tagging so that all the VF options can be used
Provide instructions for users on how to tag their PB Bibles so that they can use these VF options

However, it appears that all three fell through the cracks. I have created new cases for these tasks, which hopefully will allow them to get some attention.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/837270#Comment_837270

Is there anything that can be done in tagging personal Bibles to enable this feature?

Perhaps a specific tag must be given to the headings?

If you add the "chapternum" field around chapter numbers, and the "versenum" field to verse numbers, then your PB Bibles may start working. I think the syntax would be something like:

[[@Bible:Ge 1:1]]{{field-on:chapternum}}1. {{field-off:chapternum}}{{field-on:bible}}In the beginning, God created the heavens and the earth.{{field-off:bible}}
[[@Bible:Ge 1:2]]{{field-on:versenum}}2 {{field-off:versenum}}{{field-on:bible}}And the earth was without form and void.{{field-off:bible}}

(I haven't tested this, it would probably be worthwhile to test this with a small example before reformatting your entire PB source.)

I think using the "chapternum" field is optional; it's intended for the case where Bibles omit the verse number "1" at the beginning of a chapter and use just the chapter number (often in a larger or bold font) instead. If you always show verse "1" at the beginning of each chapter, you could use "versenum" everywhere.

These fields should be used for just the chapter/verse number (not pericope headings, translators notes, or other text), but should include trailing/medial punctuation/spaces, e.g., "1. ", "2 ", "3:16 ", etc. Including the spaces in the field should allow the Bible Text Only to hide them appropriately when "One verse per line" is turned on or "Chapter/Verse numbers" is turned off.

NB.Mick

https://community.logos.com/discussion/comment/837406#Comment_837406

In order for the VF to display both "Non-Bible text" and "One verse per line", the display has to hide the regular chapter and verse numbers encoded in the text, so it can display the verse numbers in the margin. This requires the chapter and verse numbers to be tagged so they can be hidden independently of the other non-Bible text.

If the Bible doesn't contain that tagging, the two options are incompatible, and turning on "One verse per line" has the side effect of hiding all non-Bible text, regardless of that VF setting. (The other way of implementing it would have been to duplicate the chapter and verse numbers in the one-verse-per-line display; I assume the person who wrote the feature thought that would be a worse outcome.)

I think Philana was trying to summarise the current state of the program, not justify it.

When this bug was written up in our internal system, three action items were proposed:

Fix the VF UI so that these mutually exclusive options aren't shown for resources that can't support them

Rebuild the resources that lack the chapter and verse number tagging so that all the VF options can be used

Provide instructions for users on how to tag their PB Bibles so that they can use these VF options

However, it appears that all three fell through the cracks. I have created new cases for these tasks, which hopefully will allow them to get some attention.

Thanks Bradley,

your explanation makes a lot of sense to me, and the three action items seem to be exactly what's needed. Sorry (also @Philana) if my post above sounded a bit cranky.

Mick