Update (20 November 2020): I’ve posted my initial observations of the LSB Gospel of Mark here.
If you haven’t seen the news by means of a video update from John MacArthur for his church (skip to 7:20 in the video above), there’s a new translation in the works called the Legacy Standard Bible. It promises being based on the well-loved NASB 1995 translation, translating YHWH as Yahweh instead of LORD in all capitals, and translating doulos as ‘slave’ instead of ‘servant’ as it appears in other translations. It sounds good so far. And hopefully they have better business acumen than the Lockman Foundation, which once stated that this updated version would be ready in the spring of 2018 and is notorious for failing to produce nice paper Bibles, forcing other publishers to license the text and save NASB fans from going to church with mangled trade paperbacks.
Too many bytes have been spilled concerning how we have “too many English translations,” so I need not pile on top of that. I do, however, have some observations and questions.
Death of a Version
Readers who became believers prior to 2011 will probably remember the NIV 1984 as the NIV with which they are most familiar, and it was indeed popular. Perhaps others may still be unaware in the first place that the NIV came out with a new edition in 2011. The NIV 1984 is out of print, and the NIV 2011 update is substantial. But it’s not like Zondervan sat on their laurels with the massive success of the 1984 and released nothing until 2011. Do you remember the TNIV—the Today’s New International Version?
For one, the TNIV was a terribly redundant illustration of why Bible publishers should stop putting time references like “today’s” and “new” in their translation names. Here’s looking at you, Modern English Version.
The TNIV was also a commercial flop. Both the SBC and PCA condemned it by resolution at their respective 1997 annual conferences. Together with over 100 stalwarts of Reformed evangelicalism like Paige Patterson, Ronnie Floyd, James MacDonald, Pat Robertson, and Joshua Harris, the CBMW published a Statement of Concern in protest of its many poor translation choices.
Okay, I was half-joking in the above paragraph, but those men did sign the statement alongside names whom you would have expected in 2002: R. C. Sproul, John MacArthur, D. James Kennedy, C. J. Mahaney, and Joshua Harris (welp). And rather than stuffing examples into this post, reading the Statement of Concern should suffice if you’re curious.
But in 2009, USA Today wrote:
The scholars and publishers behind the world’s leading English language evangelical Bible announced Tuesday that they would publish a updated translation in 2011.
“And we’ll make sure we get it right this time,” says Keith Danby, president and chief executive officer of Biblica, once known as the International Bible Society.
[…]
Tuesday, Danby said they erred in presenting past updates, failed to convince people revisions were needed and “underestimated” readers’ loyalty to the 1984 NIV.
Maureen Girkins, president of Zondervan, says the “divisive” TNIV and “cherished” 1984 NIV will not be published after the newest NIV comes out. “We need to undo the damage,” she adds.
So Zondervan relented and published an update of the NIV 1984.
Haha, just kidding. They published an update of the TNIV and gave it the NIV name. That’s right. The NIV 2011 is an update of the TNIV, not an update of the NIV 1984. And while there were some improvements between the TNIV and NIV 1984, CBMW’s analysis found that “75% of inaccurate gender language translations from the TNIV
are retained in the 2011 NIV.” Another analyst found that among all verses in the NIV 2011, 60.7% had no changes among all three versions, 31.3% used the TNIV text instead of the NIV 1984, 7.5% had new text that was different than both, and just 0.6% reverted back to the NIV 1984.
But hey, it’s the NIV, and most people walking into LifeWay…er…browsing Amazon for Bibles won’t know that. According to the ECPA, the NIV 2011 was the bestselling English Bible of 2019. Go figure.
Any day now.
Today’s New American Standard Bible?
Despite that the Lockman Foundation has business acumen comparable to that of a food truck that sells ham sandwiches outside synagogues (too harsh?), they apparently are not calling the update “Today’s New American Standard Bible.” While the full text of the update is not yet public, if the translation even has a complete draft at this point, we do have various Facebook posts where Lockman features translation changes. One blogger has taken to documenting these updates, and the news may not be good.
For example, we have the following in 1 Thess 5:14—
We urge you, brethren, admonish the unruly, encourage the fainthearted, help the weak, be patient with everyone. NASB 1995
We urge you, brothers and sisters, admonish the unruly, encourage the fainthearted, help the weak, be patient with everyone. NASB 2020
(source)
This is just my opinion, but I think it’s too late and too difficult now for Lockman to pull off what Zondervan accomplished with the 2011 update. The readership who have stuck with the NASB 1995 seem to be a more discerning bunch. NASB 1995 will die a lonely death like the NIV 1984, but I just don’t think the NASB 2020 is going to have any success on its current course.
Actual conversation with my 5-year-old daughter—
Aletheia: “Who is that?” (points)
Dad: “Francis Chan.”
Aletheia: “He looks like you but with no hair.”
Marketing
Did anyone actually buy the ESV because he was thinking, “Wow, I’ve been looking for a revised Revised Standard Version that isn’t the New Revised Standard Version for ages, and it’s finally here!” I doubt it. It was their marketing, and lots of it.
One result of that marketing, intentional or not, is that the ESV is probably seen as a translation mostly popular in Reformed circles. At least that’s my personal perception, especially when jokes like “Elect Standard Version” come around. And for sure, it is a formal translation that retains the word “propitiation” as it should. Nowadays, the ESV is the fourth most popular English Bible, only behind the NIV, KJV, and NLT.
If my perception is right here, then we are presently seeing a trend where new translation names become popular in specific circles where they are marketed. Consider the NET Bible, which you might not have even heard of. Because it was largely done by Dallas Seminary professors, I find it’s only popular in non-Calvinist dispensational circles and among those with a strong interest in textual criticism due to its many notes. In fact, it seems to be most popular as a text-critical reference work rather than a Bible one actually sits down with for reading paragraphs, chapters, and books. Some of this is due to what I find to be an unbearable translation style. The NET is also a “fresh” translation with no previous English version on which it was based. It didn’t even make ECPA’s top-10 list in 2019.
But the New King James Version also had strong Dallas Seminary influence from Zane Hodges and Arthur Farstad, both Majority Text advocates. The NKJV enjoyed widespread popularity even among those who have no idea about text-critical issues such as longer ending of Mark, and even now it’s still in print. That “King James Version” part had to be the key, even though the NKJV is by no means “the King James with all the thees and thous taken out.” Even now, the NKJV ranks #5 in sales. Four hundred years of “King James Version” marketing will do that for you. And despite strong Dallas Seminary influence, the NKJV is hardly considered “that dispy translation.”
The Update We Want?
Most reaction on Twitter to the Legacy Standard Bible news is positive, but there are some negatives in terms of whether the translation will be successful commercially. First, John MacArthur and The Master’s Seminary have plenty of haters from different angles. No social media egalitarian is going to be caught dead with this thing. Some Reformed camps will struggle with whether this belongs on the same shelf as their Scofield Reference Bibles. The distinctives that MacArthur highlights in the video look good so far, but the danger of the LSB becoming “that Calvinist dispy translation” is very real.
But I have to ask: if Lockman is taking so long with this update, should the LSB just be named NASB 2020 or whichever year it’s published? The LSB translation group almost certainly is going to do a better job retaining the spirit of the NASB, and it might make more business sense for the Lockman Foundation as well. But of course, the Lockman Foundation doesn’t have any business sense, so don’t hold your breath. Hey, maybe it will be Today’s New American Standard Bible, and we’ll have a good, dark-humored chuckle.
Formal translation style. YHWH is Yahweh. Supplied words in italics. But this is not the Legacy Standard Bible.This has been done already. Kind of.
In the some-200-year history of modern English Bibles, you would think someone would have come up with something like the LSB, right? I just have to wonder how close this is going to be to the English Bible I most often read for long-form study.
You might not have heard of this one. The translation style is beautifully formal. YHWH is Yahweh. Supplied words are in italics. Doulos is “slave,” not “servant.” Adelphos is “brother,” not “brothers and sisters.” Uniquely, idioms are marked with corner brackets, which is spectacular. What’s the problem?
For one, actually being printed on paper would be nice. This translation is the Lexham English Bible, and it’s published electronically by Faithlife, the company behind Logos Bible Software. This is a company that obviously does have business acumen, and I can only assume they have made a sound business decision not to have printed the LEB on paper for anyone to buy…yet. The license page on their website says there is a print edition in the works, and despite my Logos hate, it has become my primary translation for long-form reading.
I found another problem after having written the bulk of this post: the LEB translates the Hebrew adam with terms like “humankind,” “human,” and “human beings” when used in a generic sense, whereas others like the NASB and ESV stick with the more traditional “man.” I would imagine this has something to do with a difference of opinion between the Old Testament and New Testament translation committees, but I’ll have to get back to you on this one. Although MacArthur doesn’t mention adam in the above video, I think we already know his opinion on this.
It will be interesting to see how the LSB compares to the LEB and whether the former might have to undergo an early name change. In fact, there kind of already is an “LSB”: the Legacy Study Bible, and it’s the kind of study Bible you’ll judge by its cover when you see it. Prove me wrong. 🙂
More posts on published Bible versions
• [field title-link]• [field title-link]
• [field title-link]
• [field title-link]
• [field title-link]
• [field title-link]
• [field title-link]
• [field title-link]
• [field title-link]
• [field title-link]
• [field title-link]
• [field title-link]
I enjoyed that commentary, Garrett. I do enjoy sharing that I was saved reading the TNIV. I didn’t know the difference and it’s what I was given. I’m not defending that translation. My only point it to exalt God’s power in reaching sinners through even weak and fallible human means.
Great review. Thanks for your work in this. And the stinger at the end was perfect.
Thank you, Dave!
I am any looking forward to the LSB and hope the change “tongues” to “languages” where appropriate.
The HCSB did a fresh bold translation that did a lot of what they are trying to with the LSB, but sadly stepped backwards with their updated CSB.
Good question on “tongues” vs. “languages,” Jim. I imagine that would ignite some ire and accusations over being selectively interpretative. Concerning the CSB, I share your lament, though I appreciate that they didn’t just name the CSB “HCSB” and act like nothing was different. 🙂
The name of God in the Old Testament properly translated LORD Ex3:15 NASB. In the New Testament properly translated Jesus, Jude 5 ESV. The mistake of the ASB was to make a proper name form YHWH, Jehovah. The WEB and the LEX made the same mistake by using Yahweh, a made up name God never told anyone was His name. My payer is that the Lockman Foundation will not allow the Legacy Standard Bible to make the a mistake by using Yahweh.
Hi Clayton,
How are you arriving at translating LORD instead of YHWH in Exodus 3:15? The Hebrew clearly says יהוה.
As for Jude 5, I lean towards the “Jesus” reading rather than Lord. However, that only goes to show that Jesus *is* YHWH. It doesn’t invalidate having YHWH in Exodus 3:15.
Yod He Waw He is a verb Hayah, to be. The Hebrew Old Testament reader would use Adonai. The LXX is Kyrios. The NASB, ESV,NIV,NKJV use LORD. God told Moses who He was, is and will be LORD. The tetragrammaton is an unspoken revelation that Jesus is LORD. Yahweh is a modern guess on how to pronounce Hashem.
I’m not sure that I understand how you’re arriving at insisting upon LORD only. Would you oppose “YHWH” in a translation?
Good morning everyone, since I gave my life to Christ, I have always used the KJV and was told that is the only Bible to use but was never told anything else. I purchased the LSB from 316 Publishing, I have read some of it but found John1;18 changed and Luke 4;4 missing part of the verse. John 1; 18 reads begotten God and Luke 4; 4 reads man shall not live by bread alone (missing but by every word that proceeds out of the mouth of God). This is different from the KJV. Which is the most accurate translation?
Hi Terence. I will hope Garrett will respond, but I do know that there are some verses translated differently or appear to have parts missing because the translators used different versions of the “original” Greek. Since we don’t have the actual original letters written by Paul and John, for example, we have to use copies, and those copies are not always identical. Textual critics do their best to determine what the original must have been. I’m sure we fail sometimes. Thankfully, most people agree that no essential doctrines are broken by these inconsistencies in the copies we use for translation.
Hi Terence. Some differences among translations aren’t merely translation issues but text-critical issues where manuscripts differ. In the case of the KJV, the translators had access to fewer manuscripts than translators of modern versions do. Now that we do have more of these manuscripts and modern versions, there’s controversy on how to go about determining what the original said when manuscripts differ.
In the case of John 1:18, earlier manuscripts read “God,” but a later majority of manuscripts read “man.” Luke 4:4 appears to be a later scribal harmonization with Matthew 4:4. Both of these in particular are clear cut cases where the modern versions are more accurate.
The go-to work on this is Philip W. Comfort’s _New Testament Text and Translation Commentary_, which I reviewed here: https://thingsabove.us/bridging-the-knowledge-gap-in-new-testament-textual-criticism/
Thank you Gentlemen for your response, I am finding it hard to switch over to the LSB, so been used to the KJV and the way it reads, I will probably be staying with it also because the KJV is tried and tested through 4 centuries.
Terence.
YHWH is an attempt to transliterate Hebrew letters to English consonants then add vowels to pronounce a word like Yahweh. The tetragrammaton is a compound unpronounceable term to describe who God is; the Triune God with us our LORD and Savior Jesus. Jude 24,25 John 17:11,23
Most obnoxious, abrasive review I have ever read.
Thanks for this review. I wanted to know. Personally, I’d never use an LSB because it is connected with Master’s, about which I’ve read some very bad stuff, and Master’s with John MacArthur. I’ve never heard a preacher who is so arrogant and misogynist, e.g., “Close your mouth and listen to me” in response to a woman on Youtube who rejects Calvinism.
That aside, I looked at the statement of concern. The ESV and such do a very good job of translating masculine words, including pronouns, as masculine only, except when it doesn’t. Matthew 16:24 clearly says in Greek, “If any male.” So, the ESV is not even following its own stated approach. If translations refuse to translae adelphoi in many contexts as “brothers and sisters,” they are being deliberately inaccurate. All one has to do is look at BDAG. If I take all the gender language seriously, then the LSB, ESV, do the very thing that the TNIV was trying to avoid: exclude women from Christian faith. If Paul says, in Rom 12:1, “I exhort you brothers,” then quite naturally this passage does not apply to women. When the ESV was new, I heard a presentation at an SBL meeting about it. They defended their approach by saying that Reader’s Digest uses “he” generically. Even if that were true–and they only asserted, rather than proved, it, this is totally out of touch with English usage in the 21st century. How many girls will know that “he” and “man” and “brothers” in many contexts are actually inclusive? Zero, I’d guess.
I was also interested to see the Statement of Concern signatories. Most of them were pastors, and most of them wouldn’t know what to do with a Hebrew or Greek word. Plus, at the risk of causing offense, I’m an Evangelical but do not accept the Reformed version of theology. So, a translation by Reformed folk is not of much interest to me.
One of my tests of a translation is what it does with 1 Cor 11:10. If it says a woman should have covering over her head, i.e., a man to boss her around, as the ESV does, it’s false to the Greek totally. That translation is eisegesis of the highest order.
These are reasons I don’t use the ESV and won’t use the LSB. Obviously, you don’t share my view, and that’s okay. We’re still brothers in Christ. For full disclosure, I’m on the translation committee for the New Tyndale Version and our approach to gender-accurate language is similar to the TNIV. I translated Romans, for example, and am translating Luke right now. You’ll get to review that some time in the future. One of the translators for the NTV is a lifelong Southern Baptist. I don’t know what approach he is taking. We’ll have to read the book of Revelation to find out.
Ken