BUG: Inappropriate Bible searches from a word in a lexicon
1. If a word is selected in a lexicon and Headword is selected in the Context menu, it offers a Bible search for headword:word, which is guaranteed to fail.
2. If a word is selected in a lexicon, the Context menu Selection offers a Bible search of the word but:
- the current selection for resource is used instead of preferred language bible
- it is a manuscript search when a lemma search should be offered (perhaps as a different selection on the LHS of context menu).
Dave
===
Windows 11 & Android 13
Comments
-
1. If a word is selected in a lexicon and Headword is selected in the Context menu, it offers a Bible search for headword:word, which is guaranteed to fail.
Thanks. I've written up a case to fix this.
the current selection for resource is used instead of preferred language bible
That's certainly an interesting idea. We generally prefer not to make changes to the Bible that the user has selected, since that can be disruptive with the "send searches here" option. This seems like something that would be appropriate for adding to https://feedback.faithlife.com/boards/logos-desktop-app
it is a manuscript search when a lemma search should be offered
Turn on the Factbook Tags visual filter. Then when you right click there will be a lemma option which you can use to do anything you would normally do with a lemma.
Blindly using surface text as a lemma would lead to incorrect search results (consider things like homonyms or the fact that the application can't know whether the selected text is the lemma form of a word or not).
Andrew Batishko | Logos software developer
0 -
the current selection for resource is used instead of preferred language bible
That's certainly an interesting idea. We generally prefer not to make changes to the Bible that the user has selected, since that can be disruptive with the "send searches here" option.
"Send searches here" was active. If Books Search for a Commentary is selected, the Bible Search used is Scrivener 1881 for a Hebrew word, and that selection remains for a subsequent Hebrew word search. And that is a problem when a Bible search was not the last search.
it is a manuscript search when a lemma search should be offered
Turn on the Factbook Tags visual filter. Then when you right click there will be a lemma option which you can use to do anything you would normally do with a lemma.
That is useful to know. I would like the preferred bible to be selected for the Search, though.
Blindly using surface text as a lemma would lead to incorrect search results (consider things like homonyms or the fact that the application can't know whether the selected text is the lemma form of a word or not).
That wasn't my thought/intention as I regarded it as a lemma and expected a Lemma search to be offered automatically.
Looking at DBL Hebrew entry "DBL Hebrew 2859", I'm thinking that the definition is incorrect based solely on the LN numbers as opposed to the other references?
Dave
===Windows 11 & Android 13
0 -
Looking at DBL Hebrew entry "DBL Hebrew 2859", I'm thinking that the definition is incorrect based solely on the LN numbers as opposed to the other references?
Yes, the automated Factbook tagging did not have access to context beyond just the original language word itself, so it was forced to take its best guess about which homograph to use. You can use the right click menu to delete the incorrect tagging and apply the correct lemma if you spot these.
Andrew Batishko | Logos software developer
0 -
You can use the right click menu to delete the incorrect tagging and apply the correct lemma if you spot these.
DBL Hebrew 2865 - 2868 are particularly difficult and I don't know which is right...
Dave
===Windows 11 & Android 13
0
