Home » Uncategorized » Is the King James Version Too Hard to Understand? (White 11)

Is the King James Version Too Hard to Understand? (White 11)

The James White / Thomas Ross Preservation / King James Version Only debate examined the topic:

“The Legacy Standard Bible, as a representative of modern English translations based upon the UBS/NA text, is superior to the KJV, as a representative of TR-based Bible translations.”

James White Thomas Ross King James Bible Legacy Standard Bible debate Textus Receptus Nestle Aland

In our debate, James White claimed that the Authorized, King James Version was too hard to understand.  He also made this claim in his book The King James Only Controversy.  Dr. James White’s argument has been employed by others as well, such as the Bob Jones University graduate Mark Ward.  In my eleventh review video of the James White / Thomas Ross debate, I examine the KJV’s “Translators to the Reader” and point out that Dr. White confuses the KJV preface’s claim that their version would be understood by the common man with White’s own claim that the Bible must be in the language of the common man.  To my knowledge, James White never acknowledges this important distinction.

The King James Version is Modern English

I also point out that the King James Bible is not in Old English, nor in Middle English, but in Modern English, and that scholars of the English language have dated the rise of modern English from the translation of the KJV:

Old English or Anglo-Saxon -1100
Transition Old English, or “Semi-Saxon” 1100-1200
Early Middle English, or “Early English” 1200-1300
Late Middle English 1300-1400
Early Modern English, “Tudor English” 1485-1611
Modern English 1611-onward

The English Of the King James Version

Is Easier than the Hebrew and Greek of the Inspired Old and New Testament

I then deal with the crucial question-which I have not seen addressed elsewhere by opponents of perfect preservation and the Textus Receptus, and which I wish defenders of preservation would address more frequently and with more completeness–of the objective standard of what “too hard” is for a translation, namely, the level of difficulty of the original Hebrew and Greek texts themselves. Is the King James Version harder English than the Hebrew of the Old Testament or the Greek of the New Testament?  This crucial question is answered “no!”

The crucial question: Is the English of the King James Version significantly more complex and harder to understand English than the Greek of the New Testament was to the New Testament people of God or the Hebrew of the Old Testament was to Israel? The answer: No! The New Testament contains challenging Greek (Hebrews, Luke, Acts) as well as simple Greek (John, 1-3 John). Sometimes the New Testament contains really long sentences, such as Ephesians 1:3-14, which is all just one sentence in Greek. The Holy Ghost did not just dictate very short Greek sentences like “Jesus wept” (John 11:35) but also very long sentences, like Ephesians 1:3-14. God did not believe such sentences were too hard to understand, and both God and the Apostle Paul were happy for inspired epistles with such complex syntax to be sent to churches like that at Ephesus–congregations that were filled, not with highbrow urban elites, but with slaves, with poorly educated day laborers, with farmers, and with simple peasants who had believed on the Lord Jesus Christ.

 

Similarly, parts of the Hebrew prophetic and poetical books are much more challenging Hebrew than are many of the narrative sections of the Hebrew Bible. The Old Testament also contains some very long sentences. The whole chapter, Proverbs 2, is one sentence in Hebrew, for example.

 

There are also more rare or hard-to-recall words in the original language texts than there are in the English of the KJV.

 

Thus, evaluated by the objective standard of the literary level of the inspired Hebrew and Greek texts of Scripture, the King James Version is NOT too hard to understand.  If you encounter people who argue that the KJV is too hard to understand, I would encourage you to challenge them to consider whether their claim is true based on the linguistic level of the original language texts of the Old and New Testaments.

 

Learn more by watching debate review video #11 at faithsaves.net, or watch the debate review on YouTube or Rumble, or use the embedded link below:

Please also check out the previous debate review blog posts here at What is Truth?

TDR


5 Comments

  1. I come from a family of pirates, matey. We have always found the KJV hard to understand. Thankfully we now have the Pirate Bible, which is the KJV translated into the language that pirates can understand. I got several copies for family members for Christmas. What do you think of this version?

    • Mike,

      I’m glad you could get a Bible in a language you understand. Tyndale would say, that every Pirate or Ploughboy! I don’t know many who speak Pirate anymore, but it is a niche need out there. I feel burdened especially for Klingon too, to get a Bible in the Klingon language or Goblin, a great need. Sometimes out at skateboard parks, a language is spoken not found in any nation, so a skateboarder Bible, that especially takes words that skateboarders do not understand, a kind of dynamic equivalent. The word “rad” for instance would be in there somewhere.

  2. At first glance, I thought that Mike was kidding. He is not. AI has translated the KJV into Pirate Language. While I don’t see a great need for a Pirate Bible, I do understand where Mike is coming from. Instead of Pirate language, I do see a need for a Bible in “Blue Collar” argot. I don’t think that any of us here really know any blue-collar people, so our interaction with them is very limited. I know the pool guy who takes care of our pool and the yard guys who take care of the lawn, but I really only say “hi” to them if I go to the office late and I wave to them over the roar of the leaf blowers. And of course we really don’t have any blue-collar people at our churches. It’s an unreached people group that the vast majority of us will never, ever have any contact with other than the occasional “hello” if we see a plumber, carpenter, or other unskilled laborer at Lowe’s when we are picking up new lightbulbs. But why not a blue-collar Bible for the laborers of the world? It’s about time we had a Bible in the language they can understand.

  3. I visited my sister in Long Beach and went to church with her one time. I had forgotten that her church actually did have some type of ministry to blue-collar folk visa-vis some type of military outreach. Like plumbers, carpenters, and mailmen, none of us know anybody in the military. It’s just an uneducated sub-culture that is completely foreign to us. This was several years ago that I visited my sister at that church, so I don’t know if they had “special needs” Bibles that military people could understand. But I do see this an huge ministry opportunity that 99% will never meet. I see some special interest story in the 6:00 news about veterans once a year or so, but none of us in real life actually know anyone in the military. Perhaps whoever came up with this odd Pirate Bible is actually informing us of a great need in the culture.

    • James,

      I think Mike was kidding, which is why I was kidding back. I thought he was being funny. If he wasn’t, I need to check my ability to comprehend people, let alone the King James Version. I live in hillbilly territory by their own admission. They like the King James Version in hillbilly territory. Almost no one is white collar here.

      I think someone should be able to suggest an update to the King James Version without being trashed and scorched earth. I’ve thought about it, but I wouldn’t participate in it unless there was an uprising in King James churches. I haven’t had that sense at all. Yes, critical text, NA, want an update to a Bible they don’t use. This is a trojan horse for them to usher in the critical text among other problems with modern versions.

Leave a comment

Your email address will not be published. Required fields are marked *

AUTHORS OF THE BLOG

  • Kent Brandenburg
  • Thomas Ross

Archives