Whilst this change undoubtedly came from http://community.logos.com/forums/t/21316.aspx it missed the important point that the single reference should be for the nominated translation (AFAT below) - instead it points to my preferred bible with a BHS reference.
There is still a duplicated reference for multiple translations
This is working as I would expect since the NET Bible reference does not match the citation column references. I'd voice a complaint if the NKJV did not repeat the references.
There is still a duplicated reference for multiple translations This is working as I would expect since the NET Bible reference does not match the citation column references. I'd voice a complaint if the NKJV did not repeat the references.
But it is still wrong as I should have shown this:-
and this:-
Either way I don't get to access the original bible (Logos LXX) from which the passages came; even if i do this:-
Here's a further illustration of what is wrong as there is no reference for the NET bible and NKJV:-
PL was nearly right in Beta 8 and now it is virtually useless!
Ah, now I understand what you mean. I was just looking at where the references were printing - not at the accuracy of those references.[:$]
The tooltips that come up when hovering over passage reference links, no matter the panel, will always be from your preferred Bible.
Can I have a considered statement as to why the references in a PL changed so dramatically from B8 to B9 - from being almost right to being almost useless - apparently because someone complained about "duplication" of references, when it was by no means a suggestion that was universally accepted.
The tooltips that come up when hovering over passage reference links, no matter the panel, will always be from your preferred Bible. Can I have a considered statement as to why the references in a PL changed so dramatically from B8 to B9 - from being almost right to being almost useless - apparently because someone complained about "duplication" of references, when it was by no means a suggestion that was universally accepted.
This was new behavior from 4.0d and earlier 4.1 betas, and the bug was actually reported first by a developer. The problem was that it was showing the full reference before the text of the verse even when the versemap of the passage list was exactly the same as the versemap of the Bible being displayed. This was redundant. The bug was associated with the problem you reported here: http://community.logos.com/forums/t/20947.aspx.
My point has always been to have reference to the bible whose text is being displayed, simply because of textual/language differences. The example in this thread shows that i never get to access the LXX bible whose versemap is used in column 1 and which is NOT that of my preferred bible!
The advantage of references to the respective translations is to readily compare/investigate differences not available from the surface text. The preferred bible reference in column 1 does not often relate to the reason for populating the List!
The issue reported on the Passage drop down list relates to an overload of information which does not detract from the functionality of the reference ie. I select it and know what it will do!
In B11 it is still a major functional flaw that i cannot reference the LXX bible in the Passage List I show above when the passages originate from the LXX! Whilst there are aligned references for the Preferred bible I also need access to the Greek in the LXX.
Please!
My deleted response doesn't provide what you're asking, either. Will look into it.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
