BUG - Problem with "Interesting Words" and Exodus 18

Hi,
I was reading Exodus 18 and opened that in the Passage Guide. I was looking at the "Interesting Words" session and saw that "father-in-law" was emphasized right in the middle. So I clicked it to see the references. Below the "map" of words it showed "father-in-law (13)" [I am using the NASB], but no verses. I tried other words and they all shows up just fine, including "Moses" which has 21 references.
I couldn't understand what was wrong until I clicked "father" in the word map (which is small in the map). That showed "father (1)", but a whole bunch of verses shows up! When I looked at them, I could see why. Only one of the verses had "father" by itself (Ex 18-4). All the others had "father-in-law". The problem was, however, that "father-in-law" actually showed as "father -in-law" (note the spaces between "father" and "-in-law").
So it looks to me like clicking "father-in-law" doesn't find anything because it doesn't match "father -in-law" with the extra spaces in it, while "father" shows too many verses because it also matches "father -in-law" when bringing up verses. So when finding the number of references, it is fine (the counts are accurate), but whatever the program does after that, it doesn't bring up verses correctly when clicking words in this situation.
Any comments on this behaviour?
Comments
-
Please edit your post to begin with BUG to make sure Logos sees it. Edit is under the more button at the upper right of your post. You are correct that this is not the desired behavior. Thanks for reporting it.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
I can replicate the issue and will report it to Development.
Thank you for bringing this to our attention.
0 -
I decided to see if this was fixed in Logos 4.3 SR-1. Turns out it is not. Any idea when it might be? I guess it is a low priority bug?
0 -
I don't have any information about the timeline for fixing this issue or its priority.
0