Unexpected behavior when double clicking words in KJV

David Novick
David Novick Member Posts: 43
edited November 20 in English Forum

Description

Double clicking on words in KJV causes different resources to open up to unexpected places. It seems somewhat random.

Repro

  1. Open KJV to Matt 16:3
  2. Double click on "morning" - Enhanced BDB opens up to boker (morning)
  3. Double click on "foul" - BDAG opens up to miaros (with abominable in the edit control) - BTW miaros is not the Greek word used in this verse
  4. Double click on "weather" - Anchor Yale opens to weather

Actual Result

  • Various resources open up - some of which don't make sense

Expected Result

  • I imagine that this would be a configurable option, similar to LDS 3

System Specs

  • Laptop
  • Vista 64 Bit
  • 6 GB RAM

Comments

  • Logos was reindexing resources at the time.
Tagged:

Comments

  • Bob Pritchett
    Bob Pritchett Member, Logos Employee Posts: 2,280

    Sounds like it's using Hebrew lexicons as preferred resources for looking up KeyLinks.

    Try going to the Library icon in the upper left, clicking "Prioritize" in the upper right of that drop-down, and dragging your favorite dictionaries/lexicons/Bibles over to the right.

  • David Novick
    David Novick Member Posts: 43
    https://community.logos.com/discussion/comment/6682#Comment_6682

    So...I checked my "priortize" tab, and the only thing in there was ESV.

    I removed that, added BDAG, BDB, and KJV, and tried again.

    I get the same unexpected behavior which goes beyond just opening a Hebrew lexicon when double clicking a NT word.

    Looking at it a bit more, I notice the following:

    • Morning - opens BDB to boker which has "morning" as its first gloss
    • Foul - opens BDAG to miaros which has "foul" as part of its first set of glosses
    • Weather - opens ABD to "weather" - I suspect it didn't find any entries in the lexicons with the gloss "weather"

    It appears that the default behavior is to look in these "non-English" reosurces and match glosses in them, if it can find them - even if they really aren't relevant. To use Logos 3-speak, it would seem that the datatype associations for "english" are messed up.

  • Bob Pritchett
    Bob Pritchett Member, Logos Employee Posts: 2,280
    https://community.logos.com/discussion/comment/6699#Comment_6699
    It's finding English words in your Greek and Hebrew lexicons, it looks like. Try adding the Merriam Webster dictionary (or an English Bible dictionary) to your priority list.
  • David Novick
    David Novick Member Posts: 43
    https://community.logos.com/discussion/comment/6715#Comment_6715

    Yep...that's what I figured. So, if I add webster's to the top of my priority list, then it looks there and opens it first.

     

Categories