Bug [6.7 beta 1]: Louw-Nida gloss missing from BWS when run from an RI lookup

Mark Barnes

The screenshot below shows two Bible Word Study guides for the word δύναμις. The one of the left was run by right-clicking on the word 'power' in Acts 4:33, selecting the lemma and running the BWS. The one on the right was run from the guides menu, and typing g:dunamis into the box.

Notice that the Louw-Nida gloss is present on the right, but missing on the left.

If you want to replicate this yourself, note that Logos will apparently cache the results of the BWS run from the RI lookup. So to replicate this bug run the BWS from the guides menu first, then from the RI.

Rick Brannan (Logos)

Hi Mark.

When we keylink in from the text instance itself, with many target lexicons (LN one of them) we are not using the lemma, but accessing a direct map from a word instance to a specific lexicon article. This is true with Louw-Nida; the LN annotation also allows us to link to a specific lexicon article. This strategy is particularly beneficial in Hebrew, where nobody can agree either how to lemmatize or how to structure lexicon headwords.

On your left image, a specific LN article (76.1) is looked up, it has no glosses, so no text is listed. On your right image, the general back-of-the-lexicon article is what is looked up via default by-lemma keylink because there is no specific mapping override (note each sense gloss is comma'd together).

Louw-Nida is weird; my guess is that to address this issue we need do some work on specifically tagging glosses in ##.## articles in LN. You'd think "hey, glosses are in single quotes" but they are also used for quotations, so single quotes are ambiguous and we can't just automate it blindly.

In other words, I think the software is functioning correctly and this is not a new issue, and the resolution is better gloss tagging in Louw-Nida. I'll file an issue to that end.

Mark Barnes

https://community.logos.com/discussion/comment/769500#Comment_769500

Thanks for the explanation, Rick.