Notes not appearing
1 Samuel 10:8 ESV.
I have made a note on 'Gilgal':
- in ESV right clicked on 'Gilgal'
- in the right menu I selected the Hebrew lemma for Gilgal
- in the left menu I clicked 'Add a Note to "Notes on Bible Reading"
- I wrote the note, assigned a yellow note indicator that shows up next to the lemma in the "Notes on Bible Reading"
By doing this, I expect this note to appear in the ESV and the Hebrew text wherever the lemma Gilgal occurs.
However, the note indicator doesn't appear in either text.
The note indicator will appear when I write a note to the 'Reference' instead of to the lemma, using the same Notes. But of course I also want to see the note indicators for lemma notes.
To anticipate a question: 'Notes on Bible Reading' is ticked in the visual filters for ESV and the Hebrew.
Any help would be appreciated.
Dell XPS 17 9700, W11, 32GB, 1TB SSD, NVIDIA GeForce RTX 2060
L5+L9+L10 Portfolio | Logos Max | Translator's Workplace
Comments
-
Lemma-linked notes only currently appear in Original Language texts not English translations.
So I wouldn't have expected it to appear in the ESV but would have expected it in the Hebrew text.
What Hebrew text are you using?
0 -
Okay, I didn't realize that.
But then still, it also doesn't appear in the Hebrew. I'm using BHS/WIVU
Dell XPS 17 9700, W11, 32GB, 1TB SSD, NVIDIA GeForce RTX 2060
L5+L9+L10 Portfolio | Logos Max | Translator's Workplace0 -
Michel Pauw said:
But then still, it also doesn't appear in the Hebrew. I'm using BHS/WIVU
For some reason the ESV and BHS/WIVU tag the word as different hononyms.
ESV has it as "2" while BHS has it as "4" so the lemmas don't match
The LHB tags it as "2" and so the note indicator appears there.
I don't know why they have been tagged differently - hopefully someone else will be able to comment on that.
0 -
Compare BHS/WIVU and BHS/SESB
Where do we go to address this mismatch?
Dell XPS 17 9700, W11, 32GB, 1TB SSD, NVIDIA GeForce RTX 2060
L5+L9+L10 Portfolio | Logos Max | Translator's Workplace0 -
Michel Pauw said:
Where do we go to address this mismatch?
Hopefully someone from Faithlife will see this thread after the weekend and comment
To increase the chances of that I'll create a new thread in the Logos 7 beta forum and link to this one
EDIT: Cross-posted at https://community.logos.com/forums/t/133457.aspx
0 -
Graham Criddle said:Michel Pauw said:
But then still, it also doesn't appear in the Hebrew. I'm using BHS/WIVU
For some reason the ESV and BHS/WIVU tag the word as different hononyms.
ESV has it as "2" while BHS has it as "4" so the lemmas don't match
The LHB tags it as "2" and so the note indicator appears there.
I don't know why they have been tagged differently - hopefully someone else will be able to comment on that.
This is because various resources use difference systems for analyzing lemmas (in the same way that they use different systems for analyzing morphology). If you right click on a word in the resource, select the lemma, and do a search, you can see the analysis as part of the search string. BHS/WIVU uses the WIVU analysis. ESV uses the LBS analysis (Faithlife's). BHS/SESB uses (I believe, I don't have the resource available to verify right now) the SESB analysis. Different analysis systems have different mechanisms for labeling homographs, which leads leads to different classifications of some words.
Generally the application takes care of converting between analyses for you (for example, both homographs will lead to the same entry in you lexicon, even though the lexicon likely shows it as homograph number 2). It may be a bug that the note marker is not properly converting to the correct analysis. I'll check on Monday.
Andrew Batishko | Logos software developer
0 -
Thanks Andrew - for the explanation and following up
Graham
0 -
Michel Pauw said:
Compare BHS/WIVU and BHS/SESB
Where do we go to address this mismatch?
You are using a version of SESB that is missing a lot of tagging information. It is recommended that you hide the LLS:BHSSESB2 resource in favor of LLS:1.0.204, which is an updated version of the other resource.
Andrew Batishko | Logos software developer
0 -
The problem with the note visual filter not marking lemmas in different resources is caused by a failure to convert lemmas to the native analysis of the current resource. We've got a fix for this which will be made available in an upcoming beta.
For now, you will just need to be aware that the lemma indicator will only be available in original language resources with a lemma analysis that matches the lemma analysis of the original lemma that the note was attached to.
The easiest way to determine the analysis of a lemma is probably to right click on a word in the resource, select the lemma on the right side, and do a search on the lemma. This will construct a search on the lemma that will look something like: <Lemma = sesb/he/שָׁנָה> The analysis is the first string before the slashes, "sesb" in the example above.
Andrew Batishko | Logos software developer
0 -
You are using a version of SESB that is missing a lot of tagging information. It is recommended that you hide the LLS:BHSSESB2 resource in favor of LLS:1.0.204, which is an updated version of the other resource.
I'm using exactly that version:
LLS:1.0.204
2016-10-10T18:06:32Z
BHSSESB.logos4Dell XPS 17 9700, W11, 32GB, 1TB SSD, NVIDIA GeForce RTX 2060
L5+L9+L10 Portfolio | Logos Max | Translator's Workplace0 -
The problem with the note visual filter not marking lemmas in different resources is caused by a failure to convert lemmas to the native analysis of the current resource. We've got a fix for this which will be made available in an upcoming beta.
That would be great.
Dell XPS 17 9700, W11, 32GB, 1TB SSD, NVIDIA GeForce RTX 2060
L5+L9+L10 Portfolio | Logos Max | Translator's Workplace0 -
Michel Pauw said:
The problem with the note visual filter not marking lemmas in different resources is caused by a failure to convert lemmas to the native analysis of the current resource. We've got a fix for this which will be made available in an upcoming beta.
That would be great.
And it is available in the current beta
0 -
Michel Pauw said:
Any help would be appreciated.
Michel,
This should now be fixed in
7.3 (7.3.0.0031)
0
