DBL Greek lexicon link problems

Page 1 of 1 (9 items)
This post has 8 Replies | 1 Follower

Posts 102
jtondee | Forum Activity | Posted: Fri, Sep 2 2011 3:23 PM

I having a lproblem i cant figure out (its probably a simple fix). In the DBL Greek Lexicon When i mouse over the Link for TDNT with the volume and number it shows the exact same location of DBL that im in (also it won't allow me to click on the TDNT number and open the book). I have TDNT prioritized above the DBL in my library. It also does the same with strongs numbers they show up with the same DBL entry.  The funny thing is that all the LN numbers show the referenced number from LN. Thanks for any help in resolving this problem.

  

Posts 3578
steve clark | Forum Activity | Replied: Fri, Sep 2 2011 3:37 PM

This has to do with your prioritization & how books are indexed. i think this wiki page example will help you get this working. It works correctly for me when using this Advanced Prioritization method

Example 3: using Enhanced Strong’s Lexicon and restoring links to TWOT & TDNT.

QLinks, Bibl2, LLR, Macros
Dell Insp 17-5748, i5, 1.7 GHz, 8G RAM, win 8.1

Posts 102
jtondee | Forum Activity | Replied: Fri, Sep 2 2011 3:56 PM

Thanks steve that did the trick, I knew it had to be a simple fix somewhere I just didnt know where to find it

Posts 26029
Forum MVP
Dave Hooton | Forum Activity | Replied: Fri, Sep 2 2011 4:05 PM

jtondee:
When i mouse over the Link for TDNT with the volume and number it shows the exact same location of DBL that im in (also it won't allow me to click on the TDNT number and open the book). I have TDNT prioritized above the DBL in my library. It also does the same with strongs numbers they show up with the same DBL entry.

DBL Greek is "stealing" these references because it can handle them as well as the TDNT and Strong's resources!  My solution is to restrict DBL Greek to Greek words and  DBL Hebrew to Hebrew words and let the TDNT, TWOT and Strong's links fall to the appropriate prioritised resource (many resources can handle Strong's!). The wiki should show you how to restrict a resource.

Dave
===

Windows 10 & Android 8

Posts 3578
steve clark | Forum Activity | Replied: Fri, Sep 2 2011 4:14 PM

Dave Hooton:
DBL Greek is "stealing" these references because it can handle them as well as the TDNT and Strong's resources!  My solution is to restrict DBL Greek to Greek words and  DBL Hebrew to Hebrew words and let the TDNT, TWOT and Strong's links fall to the appropriate prioritised resource (many resources can handle Strong's!).

i understand your method and am sure that it is working for you. But there doesn't seem to be a simple complete method. i use the ESL which also wants to steal TDNT & TWOT links. So a lot depends on which resources that a person uses and how they want them prioritized.

Dave Hooton:
The wiki should show you how to restrict a resource.

Perhaps. But the Prioritize wiki page is pretty large and has been moved once already. Maybe a new wiki page which would show other examples of using Advanced Prioritization and having a link to it inside the Prioritizing wiki page would be a better solution. ???

EDIT: similar to how the Collections wiki page has links to the wiki page Collection Examples.

i ended up using the method below which works with both ESL & DBL

QLinks, Bibl2, LLR, Macros
Dell Insp 17-5748, i5, 1.7 GHz, 8G RAM, win 8.1

Posts 26029
Forum MVP
Dave Hooton | Forum Activity | Replied: Fri, Sep 2 2011 6:08 PM

steve clark:
So a lot depends on which resources that a person uses and how they want them prioritized.

I agree. Prioritizing is personal and involves compromise. My solution works because DBL is my preferred lexicon(s) and I prioritize the other lexicons below them so that they cannot "steal" Greek/Hebrew/Aramaic words.

steve clark:
i use the ESL which also wants to steal TDNT & TWOT links.

My prioritisation (different rationale!) avoids that as follows

  • DBL Gk    --->restricted to Greek
  • Louw-Nida
  • TDNT
  • other Greek lexicons
  • DBL Aram  --->restricted to Aramaic
  • DBL Heb  --->restricted to Hebrew
  • other Hebrew/Aram lexicons
  • TWOT
  • ESL

Note that I don't care which resources display Strong's numbers, but ESL will pick up the scraps!

steve clark:
Maybe a new wiki page which would show other examples of using Advanced Prioritization

My indirect mention of the wiki  was because your previous link to Example 3 shows how to do it for ESL  i.e. choose Greek for DBL Greek. In isolation I would have been more explicit.

Dave
===

Windows 10 & Android 8

Posts 3578
steve clark | Forum Activity | Replied: Fri, Sep 2 2011 7:06 PM

Dave,

Your design is very cleaver and well thought out (exactly as i would expect from you)!

i smiled pretty widely with your last note:Big Smile

Dave Hooton:
Note that I don't care which resources display Strong's numbers, but ESL will pick up the scraps!

Thank you for your input, as i always enjoy reading your well thought out input.

May our Lord Jesus richly bless you in all that you do!

QLinks, Bibl2, LLR, Macros
Dell Insp 17-5748, i5, 1.7 GHz, 8G RAM, win 8.1

Posts 15805
Forum MVP
Keep Smiling 4 Jesus :) | Forum Activity | Replied: Sat, Sep 3 2011 1:06 AM

Another option is prioritizing resources (primarily lexicons) with language headwords before lexicons with Strong's numbering (e.g. DBL) and using advanced prioritization so links within DBL pop-up to other lexicons.  Also can prioritize Enhanced Strong's Lexicon (ESL) so Strong's numbers within ESL pop-up to ESL while TDNT, TWOT, and GK pop-up to other lexicons:

Note: DBL Aramaic has index for Hebrew Strong Numbers.  Also, Louw-Nida Greek-English Lexicon does not have Strong's numbering, but no other Lexicon has Louw-Nida semantic domain indexing so can be placed at bottom of my lexicon prioritization list (personal choice: just after ESL that ends my lexicons with Strongs numbering).

In resources with lemma's and Strong's numbering, right click menu can have different lexicon choices:

Note: lemma list includes Little Kittel TDNT.

Note: Strong's list includes unabridged Kittel TDNT.

For ESL entry, can open DBL Greek, then hover mouse over Strong's number (or click Strong's number to open ESL).

By the way, personally prefer Lexham Analytical Lexicon to the Greek New Testament for cognate words listed with lemma:

Keep Smiling Smile

Posts 50
Darrell | Forum Activity | Replied: Wed, Apr 4 2012 4:53 PM

 

I realize this is an old thread but I recently took a look at the prioritization issues and I think I have my resources responding the way I want them to. Granted I only have the Scholar’s library and not the higher libraries that have many more resources. But if you will follow this basic scheme then add resources individually and limiting them as you go until you get the desired response I think you’ll be pleased. I like my Lexicon’s prioritized where the DBL opens when clicking the Strong numbers at the bottom of a reverse interlinear pane. I want to be able to hover or click on a Strong’s, TWOT, or Louw-Nida number and have that resource display or open properly.

This is an example of my Prioritization Limits for my preferred Lexicon resources.

Dell Lap Top Win 10_Home,  Logos 7,    

Samsung gs7 phone

Page 1 of 1 (9 items) | RSS