Open GoogleCodeExporter opened 9 years ago
I see the same behaviour.
The point in this issue is that a commentary (JFB) only displays at verse level
for the single verse currently selected.
And for many verses, there is no entry anyway, such is the nature of some
commentaries.
Original comment by DFH...@gmail.com
on 13 Feb 2013 at 7:52
JFB Mat 21:23 does display some content. Verses 1-22 don't.
Original comment by DFH...@gmail.com
on 13 Feb 2013 at 7:55
IMHO, viewing commentaries at chapter level should be a Settings option. This
would help especially for [parts of commentaries] where the entries are
sparsely populated.
Original comment by DFH...@gmail.com
on 13 Feb 2013 at 7:58
This may be a limitation in the way JSword handles pre-chapter (introductions)
content. Can you check what Bible Desktop does.
Original comment by mjden...@gmail.com
on 13 Feb 2013 at 8:11
Adding to comment #2, the commentary for verses 1-22 is contained in the
chapter commentary rather than being at the verse level.
Re: comment #4, Bible Desktop appears to handle the commentary data the same
way as And Bible. I haven't used Bible Desktop before but couldn't find a way
of viewing commentary at the book or chapter level.
I know nothing about programming but some other approaches to being able to
view the data would be to associate book or chapter commentary with the next
verse, or to be able to view a commentary as a book (to see the overall text
flow) rather than linked to a bible.
Original comment by gazn...@gmail.com
on 13 Feb 2013 at 8:47
I think the JSword & Bible Desktop developer has already addressed this in the
next version of JSword, but it might be a while before I can upgrade to that
because there are a lot of other changes in it.
Original comment by mjden...@gmail.com
on 13 Feb 2013 at 9:02
There appears to be a thread on the jsword-devel list about this issue at
http://www.crosswire.org/pipermail/jsword-devel/2012-January/003918.html
The issue does appear to be particular to jsword and its offshots.
Original comment by gazn...@gmail.com
on 13 Feb 2013 at 9:03
Re comment #6. OK, thanks.
Original comment by gazn...@gmail.com
on 13 Feb 2013 at 9:04
Original issue reported on code.google.com by
gazn...@gmail.com
on 13 Feb 2013 at 12:53