Unexpected: Keylinking from English Bibles Wildly Unpredictable

Currently if I'm reading my NRSV and double click on the english word sinner it brings the Enhanced BDB with the Hebrew entry for the word I'm clicking on. 1) I'm not sure why it would bring up the Hebrew, since I'm in the New Testament if any thing it should bring up the Greek, or, since I am double clicking on an English word, my english dictionary. 2) I'm not sure why it would bring up the Enhanced BDB for a Hebrew word, I have HALOT prioritized for my Hebrew keylinks.

Doing a little more exploration I notice I get wildly inconsistent results based on which word I double click on. "Sinner" brings up BDB. "Blaspheming brings" up Websters dictionary, and "forgiven" brings up the Dictionary of the Later New Testament and its Development.

Find more posts tagged with

Performance

Comments

Bradley Grainger (Logos)

This is a known issue (http://community.logos.com/forums/t/1679.aspx):

Many resources have not yet been rebuilt to work optimally with Logos 4. Some problems this can cause are:

English KeyLinks going to Greek or Hebrew lexicons.

Craig Downey

https://community.logos.com/discussion/comment/14111#Comment_14111

Thanks Bradley, I should have consulted the known issue page before reporting.

Todd Phillips

and "forgiven" brings up the Dictionary of the Later New Testament and its Development.

This last one is a problem with the resource. It seems to be over-indexed. Every section and subsection has too many headwords associated with it. I had to put it last in my Preferred resources, since it was always getting hits on words that really didn't have anything to do with the entry it had.

Here's an example, and this is a subsection, mind you...right-clicking on the beginning of the Food entry didn't show as many headwords:

Any of those words in the Headword list will generate a hit when keylinking, and that list is about twice as long as is visible (notice the scrollbar). I'm not even sure the subsections should have "headwords".

I'm guessing this was a problem in v3 as well, but because people don't have the preferred resources set up in v4, this one will get a lot of hits since its title comes early in the alphabet.

Dave Hooton

https://community.logos.com/discussion/comment/14111#Comment_14111

Many resources have not yet been rebuilt to work optimally with Logos 4. Some problems this can cause are:

English KeyLinks going to Greek or Hebrew lexicons.

Not sure that is strictly true. I had the problem of English going to BDB, but that was a problem with my Prioritize list. If the English resources are inadequate, or none are listed before your original language resources BDB will be the target because it has an English index; likewise Louw-Nida Greek-English Lexicon! Once I listed some comprehensive English resources (Harper's, NAS Exhaustive Concordance, Vine's Complete Dictionary of OT & NT words) it solved that problem. I tried all the above examples and more, and ended up in Harper's or NAS Concordance!

But it introduced another problem - Greek words started going to Vine's as my #1 lexicon! So right click Vine's in the list and select English. Now I could have fixed the BDB problem by selecting Hebrew, but how about Aramaic words!?

You can chase your tail with this Prioritize list as it has been the root of all my keylink problems, NOT the resource.