Undefined morphhologies in the TAGNT and the TOTHT

[Nainoia-Inc-Admin]

TOTHT - Are blank morphhologies allowed? And all of these are Qere entries
Deu.22.26-16q morph=''
Jdg.16.25-02q morph=''
Rut.3.12-05q morph=''
1Sa.9.1-04q morph=''
1Sa.24.8-06q morph=''
2Sa.13.33-15q morph=''
2Ki.5.18-23q morph=''
2Ch.34.6-07q morph=''
Isa.44.24-16q morph=''
Jer.38.16-10q morph=''
Jer.39.12-11q morph=''
Jer.51.3-03q morph=''
Lam.1.6-02q morph=''
Lam.4.3-10q morph=''
Ezk.48.16-12q morph=''

TAGNT
42_Mrk.006.011 / 032 morph='T-ASMG5270'

[DavidIB]

The TAGNT appears to have been fixed already. The empty Hebrew lines are due to Qere readings that are empty where the Ketiv has a word For example in Deu.22.26 the Hebrew text says "a man who murders his neighbour soul". It doesn't say "... his neighbour's soul". The word "soul" (NePheSh, which can also mean 'life') just sits there without purpose. When an obvious scribal error was noticed, scribes didn't correct it because they didn't want to change the text. So they left a note in the margin with the correction - which in this case meant omitting the word "soul/life". The original uncorrected text is called the Ketiv ('Written') and the edited text is called the "Qere" ('Read') - because this is the version that should be translated or read out loud. Most translations, including the KJV, tend to follow the Qere version. Young's Literal Translation tries to include the word, translating: "a man riseth against his neighbour and hath murdered him--the life". *David IB*

…

On Sat, Feb 20, 2021 at 8:50 PM Jeff Martin ***@***.***> wrote: TOTHT - Are blank morphhologies allowed? And all of these are Qere entries Deu.22.26-16q morph='' Jdg.16.25-02q morph='' Rut.3.12-05q morph='' 1Sa.9.1-04q morph='' 1Sa.24.8-06q morph='' 2Sa.13.33-15q morph='' 2Ki.5.18-23q morph='' 2Ch.34.6-07q morph='' Isa.44.24-16q morph='' Jer.38.16-10q morph='' Jer.39.12-11q morph='' Jer.51.3-03q morph='' Lam.1.6-02q morph='' Lam.4.3-10q morph='' Ezk.48.16-12q morph='' TAGNT 42_Mrk.006.011 / 032 morph='T-ASMG5270' — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#39>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAM5BOXGJ62GNQOWD6O5PQLTAAMTJANCNFSM4X6HFQ5A> .