TWOT links in DBL Heb do produce the correct information, but ONLY in the mouseover popup. Clicking the TWOT links does nothing (apart from show the TWOT link in the DBL Hebrew address bar - TWOT does not open.
I have B7 and the links work.
Likewise
Ok ... are you definitely being taken to TWOT though?
I think I know what the problem is in my setup - the links in DBL are not correct. In my copy of DBL Hebrew, the TWOT links (and Strongs) are actually links to DBL Hebrew. When I mouseover the link, the popup contains DBL Hebrew content and not TWOT content.
In other words, the TWOT links, are simply linking to the selfsame DBL Heb article they appear in - see below:
Is anyone else experiencing this behaviour?
Ok ... are you definitely being taken to TWOT though? I think I know what the problem is in my setup - the links in DBL are not correct. In my copy of DBL Hebrew, the TWOT links (and Strongs) are actually links to DBL Hebrew. When I mouseover the link, the popup contains DBL Hebrew content and not TWOT content. In other words, the TWOT links, are simply linking to the selfsame DBL Heb article they appear in - see below: Is anyone else experiencing this behaviour?
I think I misunderstood the first time, Richard. I am experiencing the EXACT behaviour that you are. Just downloaded and am using Beta 8.
Peace and Joy in the Lord to you! ........... Mel
No problem ... I didn't spot right away that the popups contained DBL Heb information and not TWOT information.
The Louw & Nida ones work fine - are yours the same?
Looks like a resource issue here - needs relinking and rebuilding.
ThanksRichard
I agree!
Peace!
Mel
No problem ... I didn't spot right away that the popups contained DBL Heb information and not TWOT information. The Louw & Nida ones work fine - are yours the same? Looks like a resource issue here - needs relinking and rebuilding. ThanksRichard
Good find, Richard (as Melissa would say). I just replicated this and noted that the Strong's numbers popup also replicates the DBL Hebrew entry.
Another thing I noticed is that the TWOT number is picked up at the bottom of the popup window (so it looks like that is the source of the info in the popup), but in DBL 3987 כלה (I can't do pointing with the Logos keyboard - kallah) - the entry says TWOT 986a, but the popup says TWOT 986.1.
Chris
I may have an updated version of the DBL Heb, as the tip window I get at DBL Heb 1854 when I hover over TWOT 401d has the 'TWOT 401d' data, and popup at bottom of window is the 'TWOT 401d'. I do see that DLB Heb 3987 displays 'TWOT 986a' data, but the reference is 'TWOT 986.1'. I'll report that.
edit: Actually I noticed that when I click the TWOT 986a link, the reference box in that resource has 'TWOT Number 986.1'. (I think they combined 986a and 986b into 986.1.)
Thanks,Melissa
I may have an updated version of the DBL Heb, as the tip window I get at DBL Heb 1854 when I hover over TWOT 401d has the 'TWOT 401d' data, and popup at bottom of window is the 'TWOT 401d'. I do see that DLB Heb 3987 displays 'TWOT 986a' data, but the reference is 'TWOT 986.1'. I'll report that. edit: Actually I noticed that when I click the TWOT 986a link, the reference box in that resource has 'TWOT Number 986.1'. (I think they combined 986a and 986b into 986.1.) Thanks,Melissa
Melissa,
This video shows what I get.
Hope this helps show the Bug
6136.2009-10-22_2304.swf
chris,
how do you get your jing movies to embed? I can't figure out how to do that
All these problem are due to Prioritize.
Consider the Index capabilities of DBL Hebrew:
So unless you do something this one resource will attract keylinks for Hebrew Strong's and TWOT, even if the link comes from DBL Hebrew! The LN links go to the Louw-Nida resource because - according to my v3 Keylink Options - it is the only resource with that Index!
According to v3 Keylink Options there are quite a number of resources for Hebrew Strong's, so it looks like most of you have prioritised DBL Hebrew ahead of the others! Ditto for TWOT!
This is what you do to DBL Hebrew so that the other resources get a crack at indexing:
ie. restrict it to Hebrew words.
TWOT numbers can be handled by Enhanced Strong's Lexicon (ESL), but the TWOT resource has the first go because it is ranked higher.
Hebrew Strong's Numbers can be handled by DBL Aramaic, Vine's and TWOT, so ESL is bottom of the food chain!
In the examples cited:
DBL Heb 3987 --> TWOT 986a went to TWOT resource and Str 3618 also went to TWOT!
DBL Heb 1854 --> TWOT 401d went to TWOT resource and Str 1728 went to ESL!
All of this complexity in a list I prioritised for Aramaic & Hebrew lexicons.
The TWOT numbers appear to have been rationalised as 401d = 401.4, 986a = 986.1 because a is first, d is fourth!
chris, how do you get your jing movies to embed? I can't figure out how to do that
I used the "Insert Media" button in the task bar on the Compose page for screenshots and videos: Save the video or screenshot to my desktop, search for it and link to it.
Screenshot:
Dave:
This seems very complicated -- I'm still scratching my head to figure how it would relate or what I have to do in my library to change things.
You seem to be saying that when we use a hot link in the text to a resource, that it doesn't link because we didn't give the resource being linked to high enough priority. Is that right? Isn't a hot link a hot link no matter if I have anything prioritized?? This is not a keylink, but a hot link, right? Or am I mixed up? When I hover over the hot link for TWOT in DBL it shows the DBL text (with the TWOT reference) -- I don't see how changing priorities will change that -- and if I click on the hot link, nothing happens. How does prioritizing affect that??
If prioritizing is so all powerful, then everytime I use a resource I'd have to re-prioritize my library so that the resource I'm in is lower than any one I might possibly find has a hot link in that resource.
Are you thinking we're talking about right clicking or double clicking or something?
This is actually a bug in the book. The numbers should display exactly as written. (If you scroll to 1292 in TWOT and move down through 1292a, 1292.1, 1292.1a, you'll see the need for preserving the numbers exactly, and how the book is incorrectly tagged.) This incorrect tagging is also breaking many of the TWOT links from other resources.
The ones under discussion are not "hot links" tied to a single specific resource. Right click a Strong's number and you will see something similar to this:-
This tells me I will get Str 4041 in TWOT first and ESL second as per my Prioritize list (the other resources are supplied by Logos4)! So if i hover I should expect a definition from TWOT! If I single-click I will be taken to that definition in the TWOT resource (RHS of picture) - note that the TWOT # 361b is the same as that referenced in DBL Hebrew.
If you right click 4475 in DBL Hebrew (same line as "striving?") you will see that it is a "hot" Link to DBL Hebrew only.
If you post a picture of your Prioritize list showing all the Hebrew/Aramaic lexicons, including ESL and TWOT if present, I might be able to make some suggestions.
You're right - that's fixed it.
It seems very unituitive to have to set DBL to only index Hebrew, and also to make sure TWOT is prioritised in order to get TWOT links to index properly in DBL Hebrew though.
IN the old L3 system, this would have been a lot simpler.
Sounds like another call for a rethink of the Data Type\Keylinking system to me.
IN the old L3 system, this would have been a lot simpler. Sounds like another call for a rethink of the Data Type\Keylinking system to me.
Yes! TWOT links would always go to my TWOT resource and Hebrew Strong's links would always go to my Strong's resource. Now, you prioritize lexicons for Hebrew & Greek and have to worry about the side-effects!
Save the video or screenshot to my desktop, search for it and link to it.
Ahh..that's what I was doing wrong...I was uploading it to screencast and then trying to embed it.
thanks for clearing that up
Save the video or screenshot to my desktop, search for it and link to it. Ahh..that's what I was doing wrong...I was uploading it to screencast and then trying to embed it. thanks for clearing that up
No problem. You've helped me in many ways, even when you didn't realize it because of your good posts.
