User:Dmsmith/KJV2011

Reporting and planning page for minor text and markup issues to improve the KJV module. This is a continuation of the work done by DM Smith in Project KJV2006.

Detection method

The issues reported here by David Haslam were detected by a detailed comparison with the text extracted from the independently created KJV1769 e-Sword module provided by Art Dunham, as once hosted on the Spanish Reina-Valera-Gomez website and downloaded before that site was redesigned. That e-Sword module was not completely without minor errors, but the comparison proved fruitful in identifying some minor issues with both works.

Text and markup issues

Translators' added words currently not displayed as italics

Due to the use of alternative transChange markup

I found 17 instances where <seg subType="x-added" type="x-transChange">...</seg> was used to mark added words. The SWORD engine does not assign italics for words marked like this.

Translators' added words that incorrectly include a punctuation mark

I found 20 instances where the transChange markers for an added word also included the punctuation mark at the end of the sentence. Admittedly, displaying a full-stop or a comma in italics is of minor cosmetic significance, yet nonetheless this is structurally incorrect.

Minor typographical errors

• In Exodus 32:32, there are two hyphens after the word sin. In printed editions there is a horizontal line (or an mdash?).
• In Romans 4:18, the word nations is followed by a semicolon. In printed editions there is a comma.
• In the colophon after Philemon 1:25 there is a comma after the word Onesmus which is not present in printed editions of the KJV.

Spelling differences

• In Acts 3:7 the KJV module has the spelling ancle. The comparison text has the spelling ankle. Both spellings are found in different printed editions of the KJV.