Please Fix Louw-Nida
In 4.0 when I run the Exegetical Guide and click on the Greek-English Lexicon of the New Testament Based on Semantic Domains it jumps to the index instead of the appropriate word in the lexicon. In the Lexham Greek English Interlinear New Testament all Greek words have been tagged with an appropriate Lowe-Nida number. This should be available in the Exegetical Guide. This works in 3.0. I remember downloading a fix for this in 3.0 last fall. Does anyone know if a fix is available yet in 4.0?
Comments
-
JohnBrumett said:
Does anyone know if a fix is available yet in 4.0?
Good point. I don't recall it having been brought up before so I'll create a wiki report to make sure it gets noticed (if you could fix your post to ensure that Louw is spelled properly!).
Dave
===Windows 11 & Android 13
0 -
Thanks Dave!
0 -
Darn!
When did that break? it used to work correctly didn't it?
Robert Pavich
For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__
0 -
Can't remember because I usually use the LN number when present in a resource - it is not my favourite lexicon for Greek words.
Dave
===Windows 11 & Android 13
0 -
I've tested this in a post 4.0c SR-1 build and a 4.0d Beta 2 build, and I'm finding that clicking on the 'Louw-Nida' link in the Word by Word section opens the "Greek-English Lexicon of the New Testament Based on Semantic Domains" to the correct word.
Once 4.0c SR-2 is released (possibly this week) and installed on your system, try the Exeg Guide again and let us know if it's still not working correctly.
0 -
Melissa Snyder said:
Once 4.0c SR-2 is released (possibly this week) and installed on your system, try the Exeg Guide again and let us know if it's still not working correctly.
4.0d B2 gets the word from the Greek-English index (Volume 2) - still requires a second click to get to a detailed definition.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
4.0d B2 gets the word from the Greek-English index (Volume 2) - still requires a second click to get to a detailed definition.
I see that now and will report it, thanks.
0
