Inaccurate Pericope title references in Bibles context menu

If I right-click on the text of pericope titles in Bibles, the reference that shows available for selection in the context menu is only that of the first verse of the pericope. For instance, Genesis 49:1-33 is titled "Israel’s Prophecy concerning His Sons" in the NASB. When I right click on it, the reference that is available for selection is Genesis 49:1. This is both inaccurate and unhelpful. The title is certainly not part of Genesis 49:1 nor applies to Genesis 49:1 only. It would be also more helpful if the user could select the appropriate verse range from the context menu (in the example above, if it showed Genesis 49:1-33). To the extent that the context menu can be used on such titles, it should be for useful purposes. For instance, one could apply a note to the entire pericope if the correct verse range was indicated. In other words, pericope titles should function the way chapter numbers work (if I select "Chapter 49" in Genesis, the context menu correctly offers "Genesis 49" as reference not 49:1).

This needs to be fixed.

Find more posts tagged with

Comments

Dave Hooton

This needs to be fixed.

The right click reflects a milestone boundary, and is not an attribute of the heading text (think about Personal Books) e.g right click in the space just above, or alongside, the NASB Chapter 49 heading; just below the heading you get the Gen 49:1 milestone. If the pericope were to refelect a <Bible> milestone then bibles could potentially have the same problems as commentaries, and I don't agree that non-bible text should have a <Bible> milestone in Bibles.

Francis

https://community.logos.com/discussion/comment/899943#Comment_899943

If the pericope were to refelect a <Bible> milestone then bibles could potentially have the same problems as commentaries

Can you elaborate?

Dave Hooton

https://community.logos.com/discussion/comment/899962#Comment_899962

Commentaries can have layers of overlapping milestones e.g.

Gen 49:1-28

summary text...

Gen 49:1-18

another summary...

Gen 49:1-2 comment...

Gen 49:3-5 comment...

Gen 49:19-28 ...

Which is the text for the reference <Gen 49:4>? Depending on the commentary, the text at Gen 49:3-5 may be selected.

When you type the reference Gen 49:4 in the commentary's Find box, you will be presented with a choice:

Go to:

Gen 49:1-28

Gen 49:1-18

Gen 49:3-5

Francis

https://community.logos.com/discussion/comment/900097#Comment_900097

I am not sure that I see this as a problem, Dave, as much as a reality of the fact that we have use for both: single verse and section references.

Yet it is true that it would be bothersome if when attempting to navigate to a single reference such as Genesis 49:1 in a Bible, I was given a drop-down list to pick from. For myself and I know it to be true for some others as well, the drop-down is often far from immediate and so it would introduce an unwelcome delay in everyday navigation. I WOULD NOT WANT THAT!

But perhaps a solution to this, in Bibles, commentaries, and guides, would be to require the use of "-" in Bible references to invoke range suggestions. In other words, if I'd type Genesis 49:1 I would go straight to that verse and not be offered a range. But if I type Gen 49:1- this would invoke choices. Regardless of what is thought of the proposal with regard to pericope titles, I think that it would good to have something like that anyway because the drop-down functionality tends to be overzealous and introduces frustrating delays in everyday study and work.

What would you think of that?

Dave Hooton

https://community.logos.com/discussion/comment/900115#Comment_900115

But perhaps a solution to this, in Bibles, commentaries, and guides, would be to require the use of "-" in Bible references to invoke range suggestions.

That has some merit for Find boxes in commentaries but milestones for individual verses may not exist, so you would still receive suggestions for a few ranges. But when a Guide parses a reference for commentaries it already attempts to be as specific as possible.

However, I don't like the suggestion of overlapping ranges for a bible as that implies <Bible> milestones for non-bible text and there would be implications for <Bible> references in resources and {Milestone <Bible>} searches.

Bradley Grainger (Logos)

This needs to be fixed.

We don't currently plan to change how pericopes in Bibles are coded in the system.

Francis

https://community.logos.com/discussion/comment/900303#Comment_900303

That's fine, it was just an idea, but perhaps not a good one. Thanks for the replies and input.