Posting Errors

How does one go about posting what I think may be an error? I am using the CSB as my primary. I was reading in Psalm 94 and in verse 5 and in this verse the word "oppress" appears. Since I DO NOT possess original language skills I rely heavily on the ESL (Expanded Strongs Lexicon) which works well with the CSB (or any other text for that matter). However, when I click on the word "oppress" in verse 5 the ESL goes to Strong's number 5772 instead of 6031. The little pop up box at the bottom of the screen lists the Strong's number as 6031 but the ESL goes to 5772. Not sure where or how to report this.

Find more posts tagged with

Comments

Graham Criddle

Not sure where or how to report this.

This is a totally fine place to report it.

However, when I click on the word "oppress" in verse 5 the ESL goes to Strong's number 5772 instead of 6031

I assume you have ESL as your highest prioritized lexicon

If you right-click the word, select the Strong's item on the right and then open ESL you will get to the entry for 6031

However, if you right-click, select the lemma and run a Bible Word Study Guide the resulting entry for the lemma is for Strongs #5772. As double-clicking a word works on the lemma, this explains why you get the results you describe.

So it seems like some form of lemma / Strong number tagging issue - hopefully someone (maybe from Faithlife) will be able to comment further.

rcdeacon

https://community.logos.com/discussion/comment/1046344#Comment_1046344

Graham, thanks for the reply. Mine works as you have pictured, however, the ESL and any given translation are linked. What I mean is, if I click on the word "oppress" in the CSB which is in the left pane and in the right pane I have the ESL open, when I click on the word "oppress" the ESL goes to 5772 instead of 6031. It works great if I RIGHT CLICK on the word!

Graham Criddle

https://community.logos.com/discussion/comment/1046345#Comment_1046345

What I mean is, if I click on the word "oppress" in the CSB which is in the left pane and in the right pane I have the ESL open, when I click on the word "oppress" the ESL goes to 5772 instead of 6031.

Yes - this is because you have the ESL prioritised as your highest (matching) lexicon and it is navigating based on the lemma as opposed to the Strongs Number.

rcdeacon

https://community.logos.com/discussion/comment/1046348#Comment_1046348

Got it! Thanks. So obviously it NOT a REAL problem after all. Thank you Graham.

Graham Criddle

https://community.logos.com/discussion/comment/1046355#Comment_1046355

So obviously it NOT a REAL problem after all

I actually think it is a real problem - in the tagging between the lemma and the Strongs number - but beyond my ability to actually determine!

rcdeacon

https://community.logos.com/discussion/comment/1046358#Comment_1046358

Should I report it and if so where?

Graham Criddle

https://community.logos.com/discussion/comment/1046361#Comment_1046361

Should I report it and if so where?

Lets leave it here for now and, hopefully, someone from Faithlife will see it and comment on it

rcdeacon

https://community.logos.com/discussion/comment/1046363#Comment_1046363

Great! Thanks again my friend.

Philana R. Crouch

How does one go about posting what I think may be an error? I am using the CSB as my primary. I was reading in Psalm 94 and in verse 5 and in this verse the word "oppress" appears. Since I DO NOT possess original language skills I rely heavily on the ESL (Expanded Strongs Lexicon) which works well with the CSB (or any other text for that matter). However, when I click on the word "oppress" in verse 5 the ESL goes to Strong's number 5772 instead of 6031. The little pop up box at the bottom of the screen lists the Strong's number as 6031 but the ESL goes to 5772. Not sure where or how to report this.

I've filed a bug report with our Content Team to look into improving this.

Graham Criddle

https://community.logos.com/discussion/comment/1046533#Comment_1046533

Thanks Philana

Appreciated, Graham

rcdeacon

https://community.logos.com/discussion/comment/1046533#Comment_1046533

Thank you Philana