Iconoclaste Posted February 11, 2021 Share Posted February 11, 2021 (edited) It took me a while to figure this out. If you do a Key Number search for [KEY H1121] in the ESV and then try to link a different tab to this one with the [HITS] command, you will get an error message because there are 14 hits for this key number that are (No inflected form), meaning that this key number is tagged to a period, comma, semi-colon, parenthesis or other such character in the ESV.The solution to this would be to tell the [HITS] command to ignore (No inflected form), or for the ESV's tagging to be revised. Edited February 11, 2021 by Iconoclaste Link to comment Share on other sites More sharing options...
Mark Allison Posted February 11, 2021 Share Posted February 11, 2021 I think this has more to do with errors in the tagging of the NET Bible. We'll look into it. Link to comment Share on other sites More sharing options...
Mark Allison Posted February 11, 2021 Share Posted February 11, 2021 Yep, that was it. We'll have an update for the NET Bible out asap. Link to comment Share on other sites More sharing options...
Iconoclaste Posted February 11, 2021 Author Share Posted February 11, 2021 Whoops. Right! Thanks. 1 Link to comment Share on other sites More sharing options...
Mark Allison Posted February 11, 2021 Share Posted February 11, 2021 You were right in thinking that it had something to do with key numbers attached to punctuation instead of words. 2 Link to comment Share on other sites More sharing options...
Mark Allison Posted February 12, 2021 Share Posted February 12, 2021 We've just released an update to the NET Bible (version 4.5) that resolves this issue. 1 Link to comment Share on other sites More sharing options...
.png.c3123c857d1029f98e39c9394adc358d.png)
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now