Jump to content

Links to homonyms in lexicon


Susan

Recommended Posts

This issue is only problematic for me on iOS, but it seems not to be specific to it, nor to a specific module, so I’m posting here. I had requested in the past that frequency counts be added to instant details and was given the helpful advice that if I switched my default lexicon to KM Hebrew this would show up. I’m not willing to switch from HALOT on my computer but did switch on my iPad. This has been great - the frequency counts show up when I tap a word. However, the entry linked is often wrong.

 

 post-33003-0-91326300-1438619233_thumb.png

 

This is the most usual case, where it’s showing me the entry for a homonymous (much less common) word in the lexicon although the instant details above are for the correct word. This appears to occur every time the word is not on the top in a list of homonyms. 

 

On my computer, I am also directed to the wrong entry in HALOT on triple click in these cases, but it doesn’t really matter because it’s just a matter of scrolling a bit. However, having the wrong entry in the iPad pop-up (where I rarely amplify and would like to see the frequency count for the correct word) is problematic.

 

Because the instant details are correct, I know that Accordance “knows” which entry I need. Is there a way to make it so that I somehow use that information to link it to the right lexicon entry?

 

Thanks!

Edited by Susan
Link to comment
Share on other sites

Hi Susan,

 

The issue has been brought up before. It was/still is one of the most important issues for me. Go to http://www.accordancebible.com/forums/topic/13494-thread-on-logos-forum/page-3 and scroll down to my post, "Regarding #2, 'Lexicons do not always find the text you are looking for,'" and the ensuing discussion.

 

Then, see my post at http://www.accordancebible.com/forums/topic/13540-dch/?hl=homonym&do=findComment&comment=64208 and following, including a fix by Accordance. Also, http://www.accordancebible.com/forums/topic/14566-triple-click-leads-to-2nd-homonym/?hl=homonym for how Accordance addressed the issue.

In case you missed it, for best results you should turn on Preferences >Amplify > Include reference when amplifying from text to tool, which matches a homograph and its verse reference. Otherwise, in the absence of an explicit reference, Acc still defaults to the first homograph (or sometimes, even worse, to the first occurrence of the desired "lemma" in a name, etc.).

 

Btw, did you ever experience the iOS app with the ID box anchored to the word? They changed it in 2.0, but it was wonderful for rapid reading while it lasted. See http://www.accordancebible.com/forums/topic/15623-anchoring-id-to-highlighted-word-the-way-it-used-to-be/?hl=anchoring if you're interested.

 

Regards,

 

Michel

Link to comment
Share on other sites

Thanks Michel, and I apologize for bringing up something that had already been hashed out. I guess I’m still a little confused about how to make it work correctly on iOS, though. The discussions there (I think) indicate that this problem was fixed in the more recent updates, but I’m still having the problem. (Just updated to be sure.)

Link to comment
Share on other sites

No need to apologize; just trying to help.

 

Rick said that iOS shared the code for the fix. It is much better than before, but if a homograph doesn't list all occurrences, and it isn't the default one, you won't get the correct one in iOS.

 

I'm glad someone else noticed it and brought it up.

 

Regards

Link to comment
Share on other sites

Any Accordance people with an idea about how to fix this on my iPad? It's a fairly pervasive problem. I can't imagine I'm the only one noticing. It seemed like people were finding it resolved with an update last fall. I'm not sure why it's still happening for me.

Link to comment
Share on other sites

Any Accordance people with an idea about how to fix this on my iPad? It's a fairly pervasive problem. I can't imagine I'm the only one noticing. It seemed like people were finding it resolved with an update last fall. I'm not sure why it's still happening for me.

 

It was more pervasive before the fix. I sent you a pm about it.

 

Regards,

 

Michel

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...