BUG Hebrew Word Order Inconsistent in Factbook
Word order for Hebrew phrases is inconsistent in the "Referred to As" section of Factbook entries.
Note the following examples:
Comments
-
Russ Quinn said:
Word order
Are you referring to (??x)? That is not word ORDER, but word FREQUENCY. Not the order of the lemma within the verse, but the frequency that the word appears in that sense in the Hebrew Scriptures.
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0 -
I believe this is a frequency sorting, and thus is looks to be displayed properly to me.
Myke Harbuck
Lead Pastor, www.ByronCity.Church
Adjunct Professor, Georgia Military College0 -
David Thomas said:Russ Quinn said:
Word order
Are you referring to (??x)? That is not word ORDER, but word FREQUENCY. Not the order of the lemma within the verse, but the frequency that the word appears in that sense in the Hebrew Scriptures.
Oops. Sorry. Looks like you already answered this one. Didnt take the time to read replies. LOL.
Myke Harbuck
Lead Pastor, www.ByronCity.Church
Adjunct Professor, Georgia Military College0 -
I’m referring to the Hebrew word order of ”Bethlehem Ephrathah”, ”har nebo”, and “yam ha arabah”. The word order is left to right instead of right to left which is odd if you can read Hebrew. But it is correct for “bet lechem” and “yam hammelah”. Thus my description for inconsistent.
Frequency obviously determines entry order but I’m talking about word order within the Hebrew phrases for the mentioned entries.
0 -
Russ Quinn said:
the Hebrew word order of ”Bethlehem Ephrathah”,
I see now what you mean. You are correct that a compound name should read right to left (as it does in the Lexham Hebrew Bible where this one occurrence appears in Micah 5:2
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0 -
That's a bug. Reported, thanks!
0