Bug: Problem with links to Louw-Nida Lexicon
Problems using links to Louw-Nida Lexicon online (resource not on my device).
1. Links from BWS
- run BWS on ξύλον (Mt 26.47)
- tap Louw-Nida link
- it goes to ὄψιος, α, ον rather than ξύλον, ου (in Volume 2)
2. Links from its TOC
- go to TOC in the lexicon
- tap the circled arrow icon on 3 Plants (if I tap 3 it goes to 3.2 in resource)
- tap the circled arrow icon on 3B Trees (if I tap B it goes to 3.3 in resource)
- tap 3.4 ξύλον, ου
- it goes to LN 3.5 in the resource
There is no problem when the lexicon is on my device.
Dave
===
Windows 11 & Android 13
Comments
-
I'll confirm the above, and raise you one
...Here's an example of the problem with the lexicon downloaded:
- NKJV, go to any NT verse with "wages", e.g. Mt. 20:8
- Long-tap on "wages" and do the Bible Word Study
- Click on the Louw-Nida link
- It will go to the completely wrong word. Same problem as reported by Dave above.
0 -
Here's an example of the problem with the lexicon downloaded:
Strange, that works for me. NKJV is downloaded as is my ESV that I used for the BWS above.
Dave
===Windows 11 & Android 13
0 -
I have been unable to reproduce that behavior as well.
If you'd like to help us track this down further, navigate to the Android Market and download an app (it's free!) called CatLog. This allows us to pull some log files from the device.
Once CatLog is installed, try to run that lookup again. Once that fails, open CatLog, press the Menu button on your device and then select Send. Email that log as an attachment to yourself.
Please then attach that file to this thread.
Thanks,
0 -
I have been unable to reproduce that behavior as well.
Referring to Pete's problem?
Can you reproduce what I reported?
Dave
===Windows 11 & Android 13
0 -
Referring to Pete's problem?
Can you reproduce what I reported?
Actually, I have been unable to reproduce either of those issues.
That's one of the frustrations of Android, though, as I don't have the exact same devices that you're using (generally) and they are all slightly different in their architecture.
Thanks,
0 -
Referring to Pete's problem?
Can you reproduce what I reported?
Actually, I have been unable to reproduce either of those issues.
That's one of the frustrations of Android, though, as I don't have the exact same devices that you're using (generally) and they are all slightly different in their architecture.
Thanks,
0 -
Referring to Pete's problem?
Can you reproduce what I reported?
Actually, I have been unable to reproduce either of those issues.
Here's the log from the activities in my first post with issue 2. first followed by issue 1.
Dave
===Windows 11 & Android 13
0
