Why the
English Standard Version
(ESV)Should not become the
Standard English Version
How to make a good translation much better
Mark L. StraussBethel Seminary San Diegom-strauss@bethel.edu(this paper may be reproduced and distributed in complete form without written permission from the author)
I need to say first of all that I like the
English Standard Version
(ESV)
.
After all, the ESV is a moderaterevision (about 6% I believe) of the
Revised Standard Version
(RSV, 1952), which itself was done by verycompetent scholars. Like the
New Revised Standard Version
(also a revision of the RSV), the ESV generallymakes good exegetical decisions. Both the ESV and NRSV also significantly improve the gender languageof the RSV.
1
So I like the ESV. I am writing this article, however, because I have heard a number of Christian leadersclaim that the ESV is the “Bible of the future”—ideal for public worship and private reading, appropriate for adults, youth and children. This puzzles me, since the ESV seems to me to be overly literal—full of archaisms, awkward language, obscure idioms, irregular word order, and a great deal of “Biblish.” Biblish is produced when the translator tries to reproduce the
form
of the Greek or Hebrew without due considerationfor how people actually write or speak. The ESV, like other formal equivalent versions (RSV, NASB, NKJV, NRSV), is a good supplement to versions that use normal English, but is not suitable as a standardBible for the church. This is because the ESV too often fails the test of “standard English.”This paper is a constructive critique of the ESV and an encouragement for its committee to make a goodtranslation much better by doing a thorough review and revision of its English style and idiom. Criticalquestions we will ask include: (1) Does this translation make sense? (2) If comprehensible, is it obscure,awkward or non-standard English? Would anyone speaking or writing English actually say this?A few clarifications are in order. First, as a Greek professor and a Bible translator, I am a strong advocate for using multiple Bible versions, especially those from across the translation spectrum. Both functionalequivalent (idiomatic) and formal equivalent (literal) versions have strengths and weaknesses, and both areuseful tools for students of the Word. Functional equivalent versions (NLT, NCV, TEV, CEV, GW, etc.) arehelpful for communicating clearly, naturally and accurately the meaning of the text. Formal equivalentversions (KJV, NKJV, NASB, RSV, ESV, NRSV, etc.) help to reproduce formal features of a language likemetaphors, idioms, word-plays, allusions, ambiguities and structural markers. Mediating versions, which liesomewhere in the middle (NIV, TNIV, HCSB, NET, NAB, NJB, REB, ISV), are a nice balance, retainingmore formal features than functional equivalent versions but with more clarity than literal ones. I haveaddressed these issues in depth elsewhere and will not repeat them here.
2
Concerning my personalexperience, I have served on three translation committees and have consulted for a fourth.
3
My desire is for all English versions to reproduce clearly and accurately the meaning and message of God’s Word.It will become obvious from the examples below that the ESV’s problems with clarity and fluidity are primarily related to its overly literal translation policy. For real-life translators around the world—whether in
1
See discussion below under gender-language.
2
See Gordon D. Fee and Mark L. Strauss,
How to Choose a Translation for All Its Worth
(Grand Rapids: Zondervan,2007),
passim.
3
I served on a revision committee for the
New Century Version
(NCV) and presently serve on the Committee on BibleTranslation (CBT) for the NIV/TNIV, and on an editorial team for a new version—tentatively called the ExpandedBible—to be released by Thomas Nelson next year. I have also done consulting work for the
New Living Translation
(NLT).
Add a Comment