TWOT links in DBL not working
The links for TWOT within the DBL are not functioning. All other links (LN, Strong's, etc.) do. Can anyone help me confirm that this anomaly is a bug in the DBL or may it's just in my copy of the DBL? Thanks
Comments
-
According to the similar thread I had made, it's not a bug, but has to do with (advanced) prioritization.
There's a fix mentioned there. Once I followed that advice, my TWOT links worked as expected.
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
0 -
Neither my TWOT or Strongs hyperlinks are active. But, can open article from context menu. Like you my LN hyperlink is active.
LLS:46.30.10
2014-12-16T21:21:01Z
DBLHEBR.logos4Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
PetahChristian said:
According to the similar thread I had made, it's not a bug, but has to do with (advanced) prioritization.
There's a fix mentioned there. Once I followed that advice, my TWOT links worked as expected.
Thanks for the coffee [C] PC!
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
PetahChristian said:
According to the similar thread I had made, it's not a bug, but has to do with (advanced) prioritization.
There's a fix mentioned there. Once I followed that advice, my TWOT links worked as expected.
Thank you. I'm not as efficient at searching the forums as I am at repairing the machines used to do the searching. [:)]
0 -
Beloved said:PetahChristian said:
According to the similar thread I had made, it's not a bug, but has to do with (advanced) prioritization.
There's a fix mentioned there. Once I followed that advice, my TWOT links worked as expected.
Thanks for the coffee
PC!I echo this. I required 2 cups of coffee in order to locate the fix in the thread. [:)]
.
0 -
Problem solved!
PetahChristian led to a thread (see above post) which contained the fix. Thanks
A summation of the fix for anyone else that come across this issue (and this thread):
The TWOT (and any of the resources linked to) MUST be prioritized, and it must be prioritized ABOVE the DBL. This is not a resource issue directly, but a prioritization issue.
EDIT: Going a little further (I experimented a little). You can also remove the DBL from your prioritization and achieve the same result.
0 -
Erwin Stull, Sr. said:
The TWOT (and any of the resources linked to) MUST be prioritized, and it must be prioritized ABOVE the DBL. This is not a resource issue directly, but a prioritization issue.
Advanced option for TWOT prioritization (above DBL) is specifying TWOT resource for TWOT links in DBL Aramaic and Hebrew
Keep Smiling [:)]
0 -
Erwin Stull, Sr. said:
The TWOT (and any of the resources linked to) MUST be prioritized, and it must be prioritized ABOVE the DBL. This is not a resource issue directly, but a prioritization issue.
Advanced option for TWOT prioritization (above DBL) is specifying TWOT resource for TWOT links in DBL Aramaic and Hebrew
Keep Smiling
Interesting. I've played around with advanced prioritization a little. I'll have to play around with it more. Thank you.
0 -
I wanted to keep the DBL prioritized first. Here's the advanced prioritization that made the links work for me.
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
0 -
PetahChristian said:
I wanted to keep the DBL prioritized first. Here's the advanced prioritization that made the links work for me.
With respect to the advanced DBL (Hebrew) prioritization, that milestone/index is not used by any other resource AFAIK, so is not necessary. What potentially is needed is advanced prioritization for Hebrew GK Number as that is used in Mounce's Dictionary (in your list) and Enhanced Strong's Lexicon (maybe others). It seems that the default prioritization for the DBL resource (for that index) is higher than Mounce and ESL else it would be a problem for you.
My method for handling this, given that I also want DBL Hebrew to be my #1 lexicon, but I don't want it to snatch TWOT and Hebrew Strong's numbers is to prioritize:-
ESL - Hebrew Strong's (Advanced)
TWOT - TWOT number (Advanced)
DBL Hebrew
DBL Aramaic
You can specify TWOT below these if necessary (mainly for Hebrew headwords, but you don't need Advanced prioritization).
I do similarly for DBL Greek:
ESL - Greek Strong's (Advanced)
TDNT - TDNT number (Advanced)
DBL Greek
You can specify TDNT below these if necessary (mainly for Greek headwords, but you don't need Advanced prioritization).
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
I do similarly for DBL Greek:
ESL - Greek Strong's (Advanced)
TDNT - TDNT number (Advanced)
I would add:
LN - Greek (Advanced) So that double click on Greek headword within LN takes you to Volume 2; prioritize first.
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
Beloved said:
I would add:
LN - Greek (Advanced) So that double click on Greek headword within LN takes you to Volume 2;
How does this relate to the OP issue? Vol 2 is Greek headwords. And external Greek headwords will link to Vol 1 rather than Vol 2!
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
How does this relate to the OP issue?
Not to debate, but LN linking was addressed. Having the ability to quickly get from Vol1 to Vol2 is a desirable feature for some of us who use LN.
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
Dave Hooton said:
With respect to the advanced DBL (Hebrew) prioritization, that milestone/index is not used by any other resource AFAIK, so is not necessary. What potentially is needed is advanced prioritization for Hebrew GK Number as that is used in Mounce's Dictionary (in your list) and Enhanced Strong's Lexicon (maybe others). It seems that the default prioritization for the DBL resource (for that index) is higher than Mounce and ESL else it would be a problem for you.
My method for handling this, given that I also want DBL Hebrew to be my #1 lexicon, but I don't want it to snatch TWOT and Hebrew Strong's numbers is to prioritize:-
ESL - Hebrew Strong's (Advanced)
TWOT - TWOT number (Advanced)
DBL Hebrew
DBL Aramaic
You can specify TWOT below these if necessary (mainly for Hebrew headwords, but you don't need Advanced prioritization).
Thanks, Dave, for that explanation! Another light has gone on, with regard to the complex power of the program!
When I set up my advanced prioritization, I didn't know what I was doing, and I didn't understand why it worked. Your advanced prioritization is understandable, and makes more sense.
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
0 -
Beloved said:
Having the ability to quickly get from Vol1 to Vol2 is a desirable feature for some of us who use LN.
OK, but you would also have to prioritize it for external Greek headwords e.g.
ESL - Greek Strong's (Advanced)
TDNT - TDNT number (Advanced)
LN - Greek for LN resource (Advanced) ----> internal Greek (Vol1 to Vol 2)
DBL Greek -----> #1 for external Greek
LN ------> #2 for external Greek
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
you would also have to prioritize it for external Greek headwords e.g.
Yes, that is true if you want LN to appear on your prioritization listing. For the way I use LN, the context menu gets me to Vol1 for external Greek headwords. Is this what you object to?
Edit: A few points. I may not understand what you mean by internal as opposed to external Greek headwords. After playing around with different scenarios I discovered that in the case of LXX Greek the headwords did not populate a LN entry for the context menu. In this case, it would be advantageous to have LN to appear on your prioritization list. So, I concede to your view here. One problem arises and I could find no solution. The headword jumps to Vol2. I imagine this is no issue for those well versed in the language. Furthermore, it is something although unexpected, I can live with.
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
Beloved said:
For the way I use LN, the context menu gets me to Vol1 for external Greek headwords. Is this what you object to?
No objection. Just a clarification that one should prioritise LN for external Greek words if it is prioritised for internal (Vol1 to Vol2) words - so I make sure it is my #2 after DBL Greek rather than relying on default prioritisation.
I think Logos used to go to Vol 2 for external headwords because the main index for Vol1 is LN Number, so Faithlife have keyed external Greek words to Vol 1 for a context sensitive meaning. When you go to Vol 2 you see all possible meanings of the word.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
No objection. Just a clarification
[Y]
Please define internal as opposed to external headword. After extensive experimentation, I found that I do not have to prioritize LN for external Greek headwords as BDAG is my top prioritized lexicon I can reach LN from parallel resources using BDAG. I cannot find an instance where this is not the case (with the minor exception of a word like logographos found in Philo On Creation 4 where LSJ, ILSJ and GLRB are the only parallel resources listed).
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
Beloved said:
Please define internal as opposed to external headword.
Vol 1 is indexed on Louw-Nida Number and also contains (Internal) Greek headwords whilst Vol 2 is indexed on Greek headwords. Your advanced prioritization makes it possible for those internal headwords to link to Vol 2 as opposed to another lexicon that has higher priority e.g. BDAG. External Greek headwords, though, will link to BDAG as it is your #1 lexicon. You should prioritize Louw-Nida for external headwords (non-Advanced prioritization) so it will appear in the Context menu as one of your top 5 lexicons, otherwise you are relying on Logos' default prioritization. So I make it my #2 with other lexicons at #3, #4, #5 and #6. That way I choose which lexicons will capture NT words, Septuagint words and non-bible words like logographos.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
You should prioritize Louw-Nida for external headwords (non-Advanced prioritization) so it will appear in the Context menu as one of your top 5 lexicons, otherwise you are relying on Logos' default prioritization.
Thanks Dave for taking the time to enumerate your adopted practice and reasoning. After carefully considering the impact your recommended actions will have on my customary use of Logos I can find no situation where my present approach results in a negative or inadequate conclusion. As always I have taken away much knowledge from interacting with you. Thanks, again!
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
Dave Hooton said:PetahChristian said:
I wanted to keep the DBL prioritized first. Here's the advanced prioritization that made the links work for me.
With respect to the advanced DBL (Hebrew) prioritization, that milestone/index is not used by any other resource AFAIK, so is not necessary. What potentially is needed is advanced prioritization for Hebrew GK Number as that is used in Mounce's Dictionary (in your list) and Enhanced Strong's Lexicon (maybe others). It seems that the default prioritization for the DBL resource (for that index) is higher than Mounce and ESL else it would be a problem for you.
My method for handling this, given that I also want DBL Hebrew to be my #1 lexicon, but I don't want it to snatch TWOT and Hebrew Strong's numbers is to prioritize:-
ESL - Hebrew Strong's (Advanced)
TWOT - TWOT number (Advanced)
DBL Hebrew
DBL Aramaic
You can specify TWOT below these if necessary (mainly for Hebrew headwords, but you don't need Advanced prioritization).
I do similarly for DBL Greek:
ESL - Greek Strong's (Advanced)
TDNT - TDNT number (Advanced)
DBL Greek
You can specify TDNT below these if necessary (mainly for Greek headwords, but you don't need Advanced prioritization).
Hi Dave; I've been in read-only mode for a couple of days, since my primary dilemma has been solved. If possible, will you post a small listing or screenshot of your prioritization order (with advanced) for your lexicons? I would like to refer to it when I begin working on this further. Thanks
0 -
Erwin Stull, Sr. said:
If possible, will you post a small listing or screenshot of your prioritization order (with advanced) for your lexicons?
The LN Advanced is for Vol1 words to link to Vol2 as discussed above.
Lexham Theol Wordbook is restricted to Greek in my Greek list and restricted to Hebrew in my Hebrew list.
I prioritize LXX lexicons below NT Greek ones, and Theological lexicons below those because they contain selected words.
Dave
===Windows 11 & Android 13
0 -
Thanks Dave. [:)]
0
said:
