Open etale-cohomology opened 2 years ago
The Lexical Index is meant to be an index to the entries in Strong's, as well as Brown, Driver, Briggs and the codes for the Theological Wordbook of the Old Testament. The def element was added just to give w rough ides of what word is being referenced. This is all described in HebrewLexicon.pdf, as well as the readme.md for the lexicon.
On 6/22/2022 5:12 AM, Diego Alonso wrote:
A "vanilla" Strong's number looks something like H430 https://studybible.info/strongs/h6635. But OSHB features "extended" Strong's numbers (eg. |6635 b|), which (as far as I can tell) account for multiple meanings of the same word, and seem related to the |aug| field in the (really cool) |LexicalIndex.xml| https://github.com/openscriptures/HebrewLexicon/blob/master/LexicalIndex.xml. (OSHB also has "extended-extended" Strong's numbers, which look like |c/d/5531 b|, where the actual Strong's number is |5531|, and the the first part |c/d/| seems to only account for extra words within a word (eg. prepositions/articles/conjunctions like "in", "the", "and"), and the latter part |b| is as before).
Where was this extension to Strong's numbers devised, and, more importantly, can it be extended within the OSHB project?
Eg. consider |H430| https://studybible.info/strongs/h430. The |LexicalIndex.xml| |def| says |gods|.
אֱלֹהִים N gods arm But what if I'd like to add another |
| to the |xml|, to account for the meaning |God|? Eg.
אֱלֹהִים N God arm אֱלֹהִים N gods arm Notice that I've also added a corresponding |aug| field to each |
|. Can this be done? Does it make sense?
Of course this would require going to every instance of |H430| and adding an |a| or a |b| postfix (or |c|, |d|, etc.), depending on the meaning (and people sometimes disagree in certain verses, like Psa 50.1 https://biblegateway.com/passage/?search=psa+50.1&version=GNV). (Although you can automate the process if you have, say, a KJV with embedded Strong's numbers.)
But maybe what I want to do is done / can be done in another way, and I'm just speaking nonsense. Or maybe I've understood nothing about the extended Strong's numbers.
I'm also curious, where does the |def| field some from?
— Reply to this email directly, view it on GitHub https://github.com/openscriptures/morphhb/issues/94, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABLABIVR65A75GUUH63HP3VQLKH7ANCNFSM5ZPO6WXQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Okay thank you!
A "vanilla" Strong's number looks something like H430. But OSHB features "extended" Strong's numbers (eg.
6635 b
), which (as far as I can tell) account for multiple meanings of the same word, and seem related to theaug
field in the (really cool)LexicalIndex.xml
. (OSHB also has "extended-extended" Strong's numbers, which look likec/d/5531 b
, where the actual Strong's number is5531
, and the the first partc/d/
seems to only account for extra words within a word (eg. prepositions/articles/conjunctions like "in", "the", "and"), and the latter partb
is as before).Where was this extension to Strong's numbers devised, and, more importantly, can it be extended within the OSHB project?
Eg. consider
H430
. TheLexicalIndex.xml
def
saysgods
.But what if I'd like to add another
<entry>
to thexml
, to account for the meaningGod
?Eg.
Notice that I've also added a corresponding
aug
field to each<entry>
.Can this be done? Does it make sense?
Of course this would require going to every instance of
H430
and adding ana
or ab
postfix (orc
,d
, etc.), depending on the meaning (and people sometimes disagree in certain verses, like Psa 50.1).But maybe what I want to do is done / can be done in another way, and I'm just speaking nonsense. Or maybe I've understood nothing about the extended Strong's numbers.
I'm also curious, where does the
def
field some from?