Talk:Bible (King James)

Add topic
Active discussions
Information about this edition
Edition: Benjamin Blayney, ed., Holy Bible: Standard Text, Oxford University Press, 1769. Printed by T. Wright and W. Gill, printers to the University.
Source: The 1769 King James Bible – Benjamin Blayney Edition – only Gen-Jer available. See page comments section.
Level of progress:
Notes: The King James Bible was first published in 1611, as a standard English Bible to be used in the services of the Church of England according to the Book of Common Prayer. It gradually supplanted all other English Bible versions, to become by the 19th century, the standard Bible text for English-speaking Protestants whether inside or outside the Anglican tradition. Almost all printings since the late 18th century have used this Oxford Standard text of 1769, which updates and standardises the spelling and printing of the original edition.

The Inter-Testament books are not now recognized as canonical by many Protestant and Para-Protestant Christian religious groups, which consider and call them "the Apocrypha". Nevertheless, they are recognized as a constituent part of the Biblical canon by the Roman Catholic Church, the Orthodox Christian Churches, and the Oriental Christian Churches, which consider and call most of them "the deuterocanonical books"; meaning "the books from the second canon". (The Catholic definition of deuterocanonical books excludes the two books of Esdras and the Prayer of Manasses.) The Church of England and other churches in the Anglican tradition continue to specify readings from the Inter-Testament books in their lectionaries; and hence bibles printed for use during worship in these churches must necessarily include these books.

These books came from the Greek version of the Old Testament called the Septuagint, the sacred text collection used by Greek-speaking Jewish communities, and by most of early and historical Christianity. They are included in the King James Bible, and all other vernacular versions of the Reformation era, but in a separate section, and clearly marked as not having canonical status. Since the early-19th century, the Inter-Testament books have tended to be rejected by Protestant churches, and most editions of the King James bible printed for personal use since then have omitted them. Israelite communities used the Greek Septuagint until about the 2nd century AD, but Orthodox Judaism does not recognize either the Inter-Testament books or the entire New Testament as part of its own sacred text collection, which is known as the Tanakh (what Christians call the Old Testament).


The King James Version is also known as the Authorized Version. In the United Kingdom it is still copyrighted and is subject to an eternal Crown copyright. Permission to publish in England and Wales can be obtained by following the guidance in A Brief Guide to Liturgical Copyright, third edition (RTF file); permission to publish in Scotland requires contacting the Scottish Bible Board. All signatories to the International Copyright Treaty are obliged to recognize each other's copyrights, so, technically speaking, the KJV is copyrighted throughout the world. However, it is unlikely that any prosecution under copyright law would succeed outside the UK.



Appointed by whom to be read in churches of what denomination?

That bit in the front matter is from when it was originally published in England. --Pmsyyz 02:03, 17 October 2005 (UTC)
Now, I can't say for sure whether this is absolutely true, but I have heard that in the era of King James, "appointed" meant "designed", so all they are saying is that this version is "designed" to be read in churches.Fontwords 16:39, 17 May 2008 (UTC)


How about moving this to Bible, King James or King James Bible? --Pmsyyz 02:03, 17 October 2005 (UTC)

I would prefer Oxford Standard King James Bible, as I dont like disambiguation being used in titles when a more explicit title could be used. There are template issues which would need to be sorted out before this could be renamed. John Vandenberg (chat) 06:34, 9 March 2008 (UTC)
I noticed that at the top of the page, the title is Bible (King James). I was just thinking that it would be even more appropriate for the title to be The Holy Bible (King James Version).--TheThinkingRealist (talk) 14:56, 16 August 2010 (UTC)
Atheists such as myself (who read the Bible to know what we don't believe) would probably describe the Bible better as holey [having holes] than Holy. What is Holy depends on one's point of view and although this isn't Wikipedia, where Neutral Point Of View is an actual policy, I think it's probably not a good idea for the name of the webpage to assert one group's point of view; this is a scholarly project after all. I like Oxford Standard King James Bible. 12:45, 20 May 2011 (UTC)

This EditionEdit

Does this edition of the King James Bible use italics to show words not found in the original languages? And does this edition conform its spelling to the 1611 edition or some later edition? Fontwords 16:08, 30 January 2008 (UTC)

It says it is the Oxford standard. John Vandenberg (chat) 07:42, 27 February 2008 (UTC)
The intention is to markup all the words that are in italics. It's a huge task! Best not one to perform manually. There are other related tasks that could be implemented at the same time. As and when the margin notes are added, as these are styled in italics, one should bear in mind that added words and normal words within the notes are in normal text. This is known as the italics inversion rule. David Haslam (talk) 18:55, 19 March 2017 (UTC)
A tip: italics inversion can most easily be accomplished with the {{normal}} template. —Beleg Tâl (talk) 18:58, 19 March 2017 (UTC)

page scansEdit

1611 edition (high res), and 1881 new testament (djvu). John Vandenberg (chat) 08:24, 27 February 2008 (UTC)

That second link isn't the KJV alone; instead it's a parallel of the KJV with the w:Revised Version of 1881. Note how the link says that the text is the "the official text of the New version revised 1881". I'm seen bibles like this for year; see [1] for an example. Hoshie 08:31, 22 June 2008 (UTC)

The description of the edition for this transcription of the Bible is that it is the 1769 edition as edited by Benjamin Blayney and published by the Oxford University Press. I have found this offered for sale at one location, but I have as yet to find a source for a facsimile, which is what I think we need. Perhaps we will have to settle for something similar, like a pre-1923 reprint. I saw a modern reprint published by Oxford on Google, but this would not be suitable since it is not in the public domain. Library Guy (talk) 18:22, 30 June 2015 (UTC)

link to versesEdit

I do not see it explicitly noted anywhere else, so I thought it might be helpful to note here that a link such as Bible (King James)/Matthew#3:16 links directly to the verse. I spent a few days thinking about it until I found a note somewhere in one of the other scriptural talk pages that showed how to do this. --Mkoyle 04:32, 9 March 2008 (UTC)

This is because many pages use the {{verse}} template, but it isnt always used. We do need to improve how we promote the features of wikisource texts. I doubt we want annoying banners on every page, but I think it would be appropriate to put a "this work supports verse linking" notice on the TOC of each work which has full support for verse linking. John Vandenberg (chat) 06:30, 9 March 2008 (UTC)
Bible (King_James)/Numbers#35:33 works from within Wikisource but it does not seem to work from Wikipeida. I tried to link to it from w:Charles Stuart, that man of blood and it failed only linking to the start of Bible (King_James)/Numbers. I have put in a temporary fix by inserted {{section|35:33}} so that a link from wikipedia works the same way as it does from the search box on wikisource. --Philip Baird Shearer (talk) 10:29, 23 May 2009 (UTC) works fine, at least in my browser. I'm not sure why there would be any problems with it. How are you trying to link to from Wikipedia? Are you using the sourcetext template that I create, or a direct link? I was pretty sure that everything was working perfectly a few years back... Jude (talk) 12:28, 23 May 2009 (UTC)
Because on Wikipedia the usual way to link is [[s:page-name#section]] not with a URL link You can see how I am linking this page by going to w:Charles Stuart, that man of blood and editing it. --Philip Baird Shearer (talk) 20:26, 23 May 2009 (UTC)
It works ok for me using IEv6. —Mike 20:52, 11 June 2009 (UTC)
Syntactically, there is utterly no difference between {{verse}} and {{section}}. I'm still not sure what the problem is here? Jude (talk) 11:02, 13 June 2009 (UTC)

I have now liked to another verse from the same Wikipedia article and the link worked without a problem, so no need to change anything -- not sure why it did not work before. -- Philip Baird Shearer (talk) 10:56, 20 December 2009 (UTC)


This may seem to be a bit of a trifle, but, I believe that the italics serve a unique purpose in the King James translation -- something that this transcription is wholly devoid of. Nevertheless, I certainly understand that this would be a most laborious interpolation. -- Grammaticus 20:56, 15 May 2008 (UTC)

I agree heartily. If no-one objects, maybe we could start adding them. This would make this copy a better one of the King James Version text.Fontwords 16:38, 19 May 2008 (UTC)
I agree, I'm adding one now I just noticed. WilliamKF (talk) 15:41, 10 July 2014 (UTC)
The KJV and KJVA SWORD modules available through the CrossWire Bible Society make use of the OSIS XML transChange element to mark words that were added by the translators, and which are generally styled as italics in modern printed editions. David Haslam (talk) 21:36, 14 March 2017 (UTC)
Italics is a presentational format. The focus in OSIS XML is on semantic markup. David Haslam (talk) 07:23, 15 March 2017 (UTC)
Adding the wiki markup for italics manually would be a huge task, as would adding the small caps markup for the divine name (q.v.). Ditto for the pilcrows ¶ (q.v.). No doubt there are other features that might lend themselves to some form of semi-automation operations done off-line, with the resulting files uploaded to replace each page. David Haslam (talk) 19:00, 19 March 2017 (UTC)

Links to Wikipedia articlesEdit

I'm a complete noob to Wikisource, so I don't know much about policy, but I always thought that a KJV version with links to wikipedia articles embedded in the text would freakin' rock. Example from 2 Chronicles:

4 Thus saith the Lord, Ye shall not go up, nor fight against your brethren: return every man to his house: for this thing is done of me. And they obeyed the words of the LORD, and returned from going against Jeroboam.

5 And Rehoboam dwelt in Jerusalem, and built cities for defence in Judah.

6 He built even Bethlehem, and Etam, and Tekoa,

7 And Bethzur, and Shoco, and Adullam,

I would love to see the entire Wikisoure KJV converted to this format, what do you say? Abyssal leviathin 23:39, 5 July 2008 (UTC)

Yes, please feel free to "value add" by adding links to Wikipedia for any topic which isnt obvious. John Vandenberg (chat) 00:26, 7 July 2008 (UTC)
An update to this discussion for any newcomers: this sort of linking is covered by our WS:Annotations policy. Essentially, the topic is controversial, but links to Wikipedia and other annotations are generally okay provided that a copy of the text without these annotations is also provided. —Beleg Tâl (talk) 19:00, 18 March 2017 (UTC)
I agree. Any such annotations should be left to the province of a derivative work, not the principal text. David Haslam (talk) 18:50, 19 March 2017 (UTC)
How can the annotations in the Preface possibly match WS policy ? David Haslam (talk) 19:26, 19 March 2017 (UTC)


Hello. After a while of searching the Internet for the actual text of the King James Bible, including the Apocrypha, I finally found this digital version on Wikisource, and I'm very glad that I did! I am indefinitely grateful for all of the hard work that has gone into this.

I have an idea. I think that it would be appropriate to insert the Apocrypha along with all of the other books of the Bible. Whenever there are additions to certain books, they would simply be inserted where they belong in the corresponding book. I think that this would feel even more complete. --TheThinkingRealist (talk) 16:00, 16 August 2010 (UTC)

Hi, thanks for making a comment. I have made quite a few links to the text here, quotes and so on, and I had been intending to set up a version that uses a page scan of a published print edition. The arrangement of the books could be linked by the cross referencing of a later 'critical edition' (in the public domain), how things like the Apocrypha are arranged becomes a matter of presenting it as given. Do you, or anyone else, have opinion on which edition would be good to work on? cygnis insignis 17:14, 16 August 2010 (UTC)
Yes, I have a suggestion. Maybe you could use the King James pew Bible from Hendrickson Publishers.--TheThinkingRealist (talk) 15:06, 17 August 2010 (UTC)

Original (1611) King James VersionEdit

As there are plenty of KJVs available on the web, wouldn't it be nice to have, somewhere, an unaltered original first edition somewhere available. Same spellings, same use of italics, mistakes and all? This is a landmark of the English language and deserves to be accessible in a non-Bowlerized form. TomS TDotO (talk) 23:32, 16 September 2014 (UTC)

This is being worked on at Bible (Authorized Version). Beeswaxcandle (talk) 23:43, 16 September 2014 (UTC)
Thank you. TomS TDotO (talk) 18:56, 17 September 2014 (UTC)


Since this is no longer the only King James translation on Wikisource, it is necessary to further disambiguate. I suggest that the page be moved to Bible (King James, 1769), but I am open to other suggestions as well. —Beleg Tâl (talk) 14:32, 12 February 2016 (UTC)

Not supported (at present). Given that this is the only complete version and is extensively used for wikilinking (down to verse level), I'm reluctant to see it move at all. Before deciding on a move it must be established whether links of the format [[Bible (King James)/Matthew#5:7|Mt. v. 7]] would continue to work via the redirects. Yes, a Bot can be used to deal with all the links that are currently in place, but more will be created and therefore need to be planned around. Beeswaxcandle (talk) 18:40, 12 February 2016 (UTC)
I can understand your reluctance to see it moved, but I think that proper disambiguation is important and I am willing to ensure it gets done thoroughly. I've tested the bibleverse redirects and they work correctly: see User:Beleg Tâl/Sandbox/Bible/section-linker#8:23 as an example. —Beleg Tâl (talk) 19:06, 12 February 2016 (UTC)
Not supported (at present). This Bible is apparently based on "Benjamin Blayney, ed., Holy Bible: Standard Text, Oxford University Press, 1769. Printed by T. Wright and W. Gill, printers to the University." Can anyone find a scan for this text? My IA search skills are very limited. If this text is highly linked, I think we should make sure we have a scan we're working on to back it up. We've got quite a few Bible translations/versions with no backing scan listed in Portal:The Bible. I think we should hold off on moving things around until we have reliable scans for the Bible texts we're currently presenting to the public. Outlier59 (talk) 00:20, 2 July 2016 (UTC)
Bible translations without scans are not a problem. I am slowly going through them to add scans, but scans are not required for texts to be hosted here. Having a scan backing the text has nothing to do with the fact that the work title is shared with other texts also hosted on WS. In fact, this is the only KJV on Wikisource that isn't scan-backed. Adding a scan or leaving it unbacked will not change the fact that Bible (King James) is only one of three King James Bibles here. —Beleg Tâl (talk) 15:52, 2 July 2016 (UTC)
I didn't realize that there are scans for The Holy Bible, containing the Old & New Testament & the Apocrypha. Sorry, I just looked for a source tab, and it's not there of course, since the page lists three volumes. I'll work on proofing that one. Outlier59 (talk) 23:02, 2 July 2016 (UTC)


Seeing as that this document is heavily linked to from Wikipedia, yet it has no source for verification, would it be a good idea to semi-protect it (to keep people from making random changes that can't be verified one way or another)? Kaldari (talk) 23:55, 4 November 2016 (UTC)

The first half of the work has a source now. David Haslam (talk) 21:29, 14 March 2017 (UTC)
Just reverted one such unwarranted change in Matthew 12. I support the proposal for semiprotection if that's an option in wikisource. David Haslam (talk) 14:24, 16 March 2017 (UTC)

Ongoing activities connected to this workEdit

As a volunteer for the CrossWire Bible Society, along with others, I'm involved in activities related to this work. SWORD module KJV is ostensibly based on using the Blayney 1769 edition as the source text. For further details, please visit User:David Haslam/Benjamin Blayney's 1769 KJV on the SWORD developers' wiki. David Haslam (talk) 21:01, 14 March 2017 (UTC)

A few systematic spelling differencesEdit

Some words in this project are currently spelled differently to those in the source.

The partial list below should enable other editors to make suitable corrections.
Blayney WikiSource References
ax axe Deuteronomy 19:5, 20:19, Judges 9:48, 1 Samuel 13:20, 1 Kings 6:7, 2 Kings 6:5, Isaiah 10:15, Jeremiah 10:3, 51:20, Matthew 3:10
Counseller Counsellor Isaiah 9:6
counseller counsellor 2 Samuel 15:12, 1 Chronicles 26:14, 27:32,33, 2 Chronicles 22:3, Isaiah 3:3, 40:13, 41:28, Micah 4:9, Nahum 1:11, Wisdom 8:9, Sirach 6:6, 37:7-8 & 42:21, Mark 15:43, Luke 23:50, Romans 11:34
counsellers counsellors 2 Chronicles 22:4 Ezra 4:5, 7:14, 7:15, 7:28, 8:25, Job 3:14, 12:17, Psalms 119:24, Proverbs 11:14, 12:20, 15:22, 24:6, Isaiah 1:26, 19:11, Daniel 3:2, 3:3, 3:24, 3:27, 4:36, 6:7, 1 Esdras 8:11,26, (the rest of) Esther 13:3

The word 'ax' occurs just once in Baruch 6:15. David Haslam (talk) 17:15, 16 March 2017 (UTC)
The word 'axe' occurs just once in Luke 3:9 and should not be changed to 'ax'. David Haslam (talk) 18:11, 17 March 2017 (UTC)

The corrections to the listed verses have now been completed, along with several particilar locations where there were minor spelling discrepancies wrt the source text. David Haslam (talk) 19:20, 17 March 2017 (UTC)

Canonical Psalm titlesEdit

The work currently omits the Canonical Psalm title for 116 of the 150 Psalms. David Haslam (talk) 21:28, 14 March 2017 (UTC)

The 22 acrostic stanza titles for Psalm 119 are also missing. This long Psalm should be divided into 22 subsections. David Haslam (talk) 19:24, 17 March 2017 (UTC)
Also Psalms should be divided into the five books as the major section divisions that we see in the KJV.
  1. Book I (Psalms 1-41)
  2. Book II (Psalms 42-72)
  3. Book III (Psalms 73-89)
  4. Book IV (Psalms 90-106)
  5. Book V (Psalms 107-150)
David Haslam (talk) 08:26, 18 March 2017 (UTC)

Made a note over at Talk:Bible (King James)/Psalms#Missing parts giving an example where the lack of titles impedes research/understanding. Shenme (talk) 01:59, 4 June 2020 (UTC)

Source for the documentEdit

Currently, there is an online source for roughly half the document: OT books Genesis–Jeremiah. It's in the form of PDF files, one file per page, with a drop-down page selector. Finding the right page for a particular reference is currently a matter of using the successive approximation method, as there's no page index.

Anyone spending a while browsing those pages will learn that the source is far richer in terms of published features than has been digitised here in WikiSource.

We still need a suitable source for OT books Lamentations–Malachi, and for the Apocrypha and NT books. David Haslam (talk) 21:47, 14 March 2017 (UTC)

A table of contents for the online source would help anyone to find the right page for the start of each book. While we only have a partial source, this would only need to have 24 entries. David Haslam (talk) 07:21, 15 March 2017 (UTC)
I've uploaded Index:KJV 1769 Oxford Edition, vol. 1.djvu from the source you linked to, so proofreading can proceed from there. However, since it's not complete, I'd suggest considering it a separate version of the Oxford KJV, and see whether any simpler, completed scans or PDF reprints of the Oxford KJV exist that we can use to back this particular version. —Beleg Tâl (talk) 16:03, 15 March 2017 (UTC)
Table of contents is at Page:KJV 1769 Oxford Edition, vol. 1.djvu/21. —Beleg Tâl (talk) 16:25, 15 March 2017 (UTC)
The ToC link is a redlink, so that doesn't get us any further. David Haslam (talk) 19:43, 15 March 2017 (UTC)
It's a red link currently, but that's where the TOC is, it's just a matter of proofreading it. —Beleg Tâl (talk) 19:46, 16 March 2017 (UTC)
@David Haslam: Could CrossWire/SWORD be considered a verifiable publication source for the 1769 KJV? I see that it can support PDF export so we may even be able to use that project as a (much easier) basis for our hosted text. —Beleg Tâl (talk) 16:51, 15 March 2017 (UTC)
@Beleg Tâl: No - the CrossWire Bible Society does not consider itself to be a primary publication source for any of the content it distributes. Apart from the Bible modules KJV & KJVA, none of the SWORD modules are maintained as an in-house edited (OSIS XML) source text files subject to in-house revision control. The source for each of our modules is recorded in the module configuration file. If the third party source is changed, then subject to the normal constraints of available effort, we would simply rebuild the module from the updated source supplied by or obtained from the designated source. In some cases, we would change a source as and when a better one becomes available. The build process often includes one or more file format conversion stages prior to finally building the module using one of our Sword utilities. The fact that this Wikisource document exists actually helps the other way round. It's a further secondary means to check the SWORD module for any minor textual inaccuracies compared to the 1769 Blayney Edition. Even so, there are features in the SWORD module that would assist in improving the Wikisource document once we have reached a stage where the textual differences are reduced to zero or thereabouts. In this respect, I'm thinking more about how (e.g.) the italics markup for added words could be implemented with computer assistance and ingenious scripting. FIO. One CrossWire volunteer owns a copy of a modern reprint of the 1769 Blayney edition. We would normally check that before making any proposed textual changes to improve accuracy. For any changes in the first 24 books, then both he and I can also look at the PDF files at the Original Bibles site. btw. Should you wish to become involved as a CrossWire volunteer, you would be most welcome. David Haslam (talk) 19:43, 15 March 2017 (UTC)
It doesn't need to be a "primary" publication source, but I see what you mean.
Here are some other FULL, simply formatted KJV sources of the correct revision that I have found: [2], [3]Beleg Tâl (talk) 15:06, 16 March 2017 (UTC)
Where is the evidence that these are digitised copies (text only) of the Blayney 1769 Oxford Edition? They're interesting finds, but I don't see how they help to authenticate the document as a suitable source text. David Haslam (talk) 19:39, 17 March 2017 (UTC)
Well, they claim to be digitized copies of that version, which is no worse than what we have here. —Beleg Tâl (talk) 16:21, 18 March 2017 (UTC)
This is labelled as Volume II of the Oxford edition, but it seems to contain the Apocrypha and New Testament only, so I don't know where Lamentations through the minor prophets are. Volume 3 maybe? —Beleg Tâl (talk) 19:48, 16 March 2017 (UTC)
And Index:KJV 1769 Oxford Edition, vol. 2.djvu is now up. —Beleg Tâl (talk) 18:39, 17 March 2017 (UTC)
One CrossWire volunteer has written a Python script to convert the Wikisource text from the Wycliffe Bible to ParaTExt/USFM format. I'm sure this script could be readily adapted for use with this and other Wikisource Bibles. One advantage of doing so would be to facilitate getting the current text into a format whereby direct comparison with non-Wikisource digital editions of the KJV could be made with a view to detecting potential errors in this project. USFM files can be readily converted to OSIS XML and thence to a SWORD module. Text can be exported from a SWORD module using one of the command line Sword utilities from CrossWire. David Haslam (talk) 21:10, 19 March 2017 (UTC)

Check this out as a possible source... David Haslam (talk) 09:04, 28 March 2017 (UTC)

Nicely found! Most of them appear to be links to subscription-only databases, but McGill links directly and openly to copies on HathiTrust... and this one appears to have the full contents and a good quality scan! If you agree that this is a suitable source for proofreading, I'll start reconstructing a DJVU file from it that we can use. —Beleg Tâl (talk) 13:26, 28 March 2017 (UTC)

Pilcrow symbolsEdit

Currently, the document omits the pilcrow symbols ¶ used by the KJV as paragraph markers. These need to be added. David Haslam (talk) 07:16, 15 March 2017 (UTC)

The order of books in the KJV ApocryphaEdit

The order of books in the KJV Apocrypha is normally as follows:

• 1Esd • 2Esd • Tob • Jdt • AddEsth • Wis • Sir • Bar • PrAzar • Sus • Bel • PrMan • 1Macc • 2Macc

Currently, this Wikisource document has them in this order:

• 1Esd • 2Esd • Tob • Jdt • AddEsth • PrMan • Wis • Sir • Bar • PrAzar • Sus • Bel • 1Macc • 2Macc

PrMan needs to be moved to its rightful position after Bel. For brevity, I am using the OSIS book abbreviations. See KJV Apocrypha.

NB. This move will require edits to six pages of the document. David Haslam (talk) 19:21, 15 March 2017 (UTC)
Done! David Haslam (talk) 20:22, 15 March 2017 (UTC)

Partial source template?Edit

Is there any suitable Wikisource template for a document (like this one) where only part of the source is available? David Haslam (talk) 19:51, 15 March 2017 (UTC)

Not really, no. It could be worth putting a {{migrate to djvu}} tag on it linking to the two source volumes we have, and make a note in the header that the source scan is incomplete. {{incomplete}} also comes to mind but it's not really appropriate here since we do have a full text. —Beleg Tâl (talk) 16:23, 18 March 2017 (UTC)

A snippet of OSIS XML from the KJV SWORD module (FIO)Edit

Here's one verse from the KJV module OSIS XML source text:

<verse sID="Gen.1.1" osisID="Gen.1.1"/><w lemma="strong:H07225">In the beginning</w> <w lemma="strong:H0430">God</w> <w lemma="strong:H0853 strong:H01254" morph="strongMorph:TH8804">created</w> <w lemma="strong:H08064">the heaven</w> <w lemma="strong:H0853">and</w> <w lemma="strong:H0776">the earth</w>.<verse eID="Gen.1.1"/>

There are many verses that are much more complicated. David Haslam (talk) 19:56, 15 March 2017 (UTC)

Placement of the Table of ContentsEdit

A few books already have the ToC to the right. This is preferred as it enables the text to flow next to it. All the books with ordinary ToC placement should be similarly updated to use the right hand placement. David Haslam (talk) 19:22, 17 March 2017 (UTC)

Either way is acceptable, but if you want to put it on the right on all pages go ahead. Once the text is moved to scan though, there won't be an auto-generated TOC either way. —Beleg Tâl (talk) 16:24, 18 March 2017 (UTC)
Done for all books that previously lacked the floating TOC on the right, or lacked one completely. Please explain "scan through". David Haslam (talk) 18:42, 19 March 2017 (UTC)
scan though, as in "however, once the text is moved to scan, there won't be an auto-generated TOC." —Beleg Tâl (talk) 18:51, 19 March 2017 (UTC)
Ignore my typo, (sorry), but what does the "move to scan" entail? David Haslam (talk) 19:04, 19 March 2017 (UTC)
"Move to scan", or more accurately "migration to scan", refers to replacing the content of Bible (King James) and its subpages with the directly proofread text from the source you provided, Index:KJV 1769 Oxford Edition, vol. 1.djvu and its related volumes. If you're not familiar with the process, please see Help:Beginner's guide to proofreading. Once done, it will look more or less like Bible (Webster's)/Job (same idea, different version), where the TOC is created manually for the convenience of readers, but isn't automatically generated from Wikimarkup headers. —Beleg Tâl (talk) 19:25, 19 March 2017 (UTC)
Thanks! That explanation and the link to Webster's helps a lot. Yes – that's an eminently desirable aim for the project long term. It's notable that Webster made us of chapter descriptions. Blayney did too! It's a long term aim for the KJV SWORD modules to add these eventually. David Haslam (talk) 20:55, 19 March 2017 (UTC)
TOC on the right interferes with marginNotes/sidenotes and also dropped initials. When the TOC is expanded it forces all marginal notes much farther down, disconnecting them from their associated text. Forcing marginNotes lower also then interferes with placement of {{Dropinitial}} aka {{di}} misplacing the dropped initials at start of each psalm, for example. (I haven't yet found why the notes float right sections interfere with the dropped initial float *left* sections; perhaps the 'clear' instruction?)
TOC on the right is bad. I'll be switching TOC for Psalms to 'notes section'of the header, as seen for Bible (King James)/Genesis Shenme (talk) 20:32, 17 June 2020 (UTC)

Rendering the divine name with small capsEdit

Currently, the document has the divine name (usually LORD, corresponding to the Tetragrammaton) rendered all in capitals. In the source text, the word was printed with small caps except for the first letter. i.e. as Lord. The document requires this systematic improvement. David Haslam (talk) 08:46, 18 March 2017 (UTC)

For the possessive form of the divine name, the correct method is Lord’s not Lord’s. David Haslam (talk) 10:07, 18 March 2017 (UTC)
The first instance is in Exodus 9:29. Even so, with the typography of the Blayney edition, the sizes of the lowercase letter 's' and the small caps letter 's' are identical, so this is actually a difficult choice to make. The problem is that in modern digital fonts, the size of small caps letters are intermediate in height between lowercase letters and uppercase letters. I think it's for this reason that we see differences between modern KJV printed editions in this matter. Semantically, it makes more sense for the whole of the possessive form to be within the same markup element, rather than for the apostrophe and letter s to be outside the element. David Haslam (talk) 10:26, 18 March 2017 (UTC)
I agree, put the final 's inside the template unless the source explicitly indicates otherwise. —Beleg Tâl (talk) 16:36, 18 March 2017 (UTC)
In theory at least, it ought to be feasible to write a bot to search the document for all instances of LORD's and LORD and replace each by the proper small caps markup. This would leave those rarer instances of transliterated words such as JAH, JEHOVAH, etc., that should also be rendered with small caps, with maybe some notable exceptions. The divine name markup should not be applied to any words in the NT nor those parts of the Apocrypha that come from the Greek LXX. David Haslam (talk) 20:27, 19 March 2017 (UTC)
WS:Bot requests would be the place to make that request. —Beleg Tâl (talk) 20:56, 19 March 2017 (UTC)


Typography in the KJV is important:

  • The proper character to use in the hyphenated names in the OT is the EN DASH (U+2013)
  • The proper character to use as the apostrophe for possessives is the RIGHT SINGLE QUOTATION MARK (u+2019)

These systematic changes are required to make the document more accurately reflect the source text. David Haslam (talk) 08:54, 18 March 2017 (UTC)

Why would you use an endash? Shouldn't a hyphen be transcluded as a hyphen character? Or do you have evidence of the original type set used in 1769 that indicates otherwise?
Also: on English Wikisource current consensus is that straight quotation marks are usually (though not always) preferred over curly ones; any apostrophe would thus be rendered as ' rather than ’ or ’. That being said, these sorts of decisions are usually made by the person doing the proofreading, so if you want to undertake to replace ' with ’ go for it. But don't be surprised if a bot reverts your changes afterwards. —Beleg Tâl (talk) 16:34, 18 March 2017 (UTC)
An en-dash is not the right character to use for a hyphen. In the typography of the period hyphens were of varied length and replicating that here is almost impossible; and would make the text harder to read off the screen. Beeswaxcandle (talk) 18:13, 18 March 2017 (UTC)
The single right qm as the typographical apostrophe is part of modern English typography, not merely a reflection of 18th century printing. David Haslam (talk) 20:30, 19 March 2017 (UTC)
Discussion of the hyphen character is a moot point at present, as I've just discovered that the document doesn't contain any of the hyphens in the hyphenated words in the KJV OT. The digital text used for the initial upload must have been seriously defective in this regard. David Haslam (talk) 20:44, 19 March 2017 (UTC)

Ligatures, etcEdit

There are many instances of typographic ligatures in the 1769 edition. In modern typography, the only ligatures generally still found in the KJV are those used in some proper names such as Æneas and Cæsar. Some such names also appear in the soure text with "ae" instead of "æ". David Haslam (talk) 09:44, 18 March 2017 (UTC)

WS:MOS states that "special characters such as accents and ligatures should be used wherever they appear in the original document, if reasonably easy to accomplish." So, if you see 'æ' in the source, type 'æ', but if you see 'ae' in the source, type 'ae'. The only ligature that is explicitly not replicated (to my recollection) is the 'ct' ligature, which was deliberately excluded from Unicode as a font variant. —Beleg Tâl (talk) 16:34, 18 March 2017 (UTC)
It would also be preferable to avoid explicitly using the "ff", "fl", and "fi" ligatures. The fonts used here automatically kern these and the full version remains searchable. Beeswaxcandle (talk) 18:07, 18 March 2017 (UTC)

Here's a counted list of words with the Ææ ligature from the KJV excluding the Apocrypha: (source = SWORD module v2.9)

000002	Æneas
000001	Ænon
000002	Alphæus
000002	Arimathæa
000001	Bartimæus
000020	Cæsar
000008	Cæsar’s
000016	Cæsarea
000001	Chaldæans
000002	Galilæan
000005	Galilæans
000031	Judæa
000001	Prætorium
000001	Timæus
000003	Zacchæus

David Haslam (talk) 20:38, 19 March 2017 (UTC)

Roman numeralsEdit

The book names and chapter numbers in the 1769 Blayney Edition used Roman numerals. If we are to be a faithful representation of the source text, we should use Roman numerals in the same places as the source text. David Haslam (talk) 19:12, 19 March 2017 (UTC)

I've noticed that the pages for I Esdras and II Esdras already use Roman numerals in the page filenames, and that a click to 1 Esdras or 2 Esdras involves a redirect. The other books with numerically prefixed names are not like this. David Haslam (talk) 19:13, 19 March 2017 (UTC)
It doesn't technically matter. Generally, using the format used in the text is preferred. However, this format is built in to some templates, including {{biblecontents}} and {{bibleversions}}, so it would be a big job. Furthermore, the books in this version are heavily linked to by other works and other sites. My last suggestion to move pages around was shot down pretty fast. —Beleg Tâl (talk) 19:30, 19 March 2017 (UTC)

Spaced letters template?Edit

Does Wikisource have a template for spaced letters? The Blayney 1769 edition of the KJV uses spaced lettering in most if not all book titles and in other headings. David Haslam (talk) 19:16, 19 March 2017 (UTC)

You're looking for {{sp}}. —Beleg Tâl (talk) 19:26, 19 March 2017 (UTC)
At this response, I feel like I'm missing a Like button that we see in Facebook. David Haslam (talk) 10:35, 20 March 2017 (UTC)

Why are there no style guidelines here, or at source discussion?Edit

I detest the long-s w:Long s and the other long-s w:Esh (letter) and so sought information on what to do here. I peeked at first page of Genesis and no nasty characters. I peeked at scan of first page of Genesis and there's nasty s'es. So I looked at the current source page and scan has nasty s'es but not in transcription.

What're the rules here? How did they progress from scan to transcribed text? Shenme (talk) 05:01, 4 June 2020 (UTC)

Shenme I take it you've found out the answer to your question about the title of Psalm 84 asked at Psalm 8 of An_Exposition_of_the_Old_and_New_Testament_(1828).
I like the long esses but don't think one should attempt to transcribe them - they are just esses as printed before approx. 1800 when they disappeared at most printers almost overnight (I exaggerate slightly, but as a second-hand bookseller I note they did indeed disappear very suddenly in most areas of the UK) - in my opinion they are not a different letter, just a printing style. BTW I can't work out what's going on here with the relationship between Bible (King James) and the more detailed Index:KJV 1769 Oxford Edition, vol. 1.djvu, but I've not been involved - evidently my online friend David Haslam has. PeterR2 (talk) 09:17, 22 June 2020 (UTC)
PeterR2, I did end up starting a guide at Talk:Bible_(King_James)/Psalms#Styling for Psalms, it is somewhat retrospective, so that others will know what and why, without requiring agreement. It ends up being the several ways that matching the source was achieved. (The untried earlier style was 'refined' later?) It is a few of Haslam's ancient suggestions that I'm trying to accomplish.
As soon as I'm 'happy' with all the Psalms pages /523 thru /589 I will update the Bible (King James)/Psalms page to replace the contained text with instead transcluded pages from the newly created source. (see experiments that page by clicking 'Edit') Then we'll be realer?
And I'm stymied by some technical bugs, that I'll have to ask about at Scriptorium - droppedinitial's are mashed by numerous marginNote's, see Page:KJV 1769 Oxford Edition, vol. 1.djvu/556 for one. Shenme (talk) 02:18, 24 June 2020 (UTC)