In discussing a new UnSpun ranking of Bible translations, Steve Cook mentions that he was unfamiliar with the English Standard Version. I first heard about this translation at the November 2005 SBL meeting. I did a bit of work on it and posted a blog about the ESV on my old blog, Karamat. Since I have more readers now than when I first posted on the ESV, I thought I would repost what I had to say then.

— Beginning of original post —

I ran the ESV through the Logos Bible program using the Bible analysis tool. I compared the ESV against the King James (KJV), American Standard (ASV), New American Standard (NASB), New International (NIV), Revised Standard (RSV), and New Revised Standard (NRSV).

The graph on the right shows the results of the analysis on Logos Bible Software. It analyses the versions on a word for word basis. The more words the version has in common with another, the closer together the dots are plotted.

It is not surprising that the ESV is close to the RSV, because the translators use the RSV as the basic translation when they did their work. Although it is a new translation, the translation team used the RSV as a guide and updated the language. What is surprising, however, is that the ESV is closest to the NRSV, another update of the RSV. The literature on the ESV states that they wanted an updated RSV but without the inclusive language and other problems that they saw with the NRSV. Despite this, they seem to have produced a translation that is almost the same as the NRSV.

Interestingly, the ESV does not have a lot in common with the NIV, even though both were produced by conservative, evangelical scholars. This is due to the different translational philosophies. The ESV (along with the RSV and NRSV) employ a word for word translational approach (although not as strictly as the ASV and NASB). The NIV on the other hand uses a phrase by phrase approach (usually called a ‘dynamic’ approach).

This analysis confirms my first impression, which is that the ESV is a good translation that is very readable. It will be interesting to work with this translation for a while and see if this conclusion holds up.

— End of original post —

A few months ago, I had another experience with the ESV that was not as positive.  I had written a plugin for WordPress that would allow ESV text to be automatically inserted into blog posts via their XML service.  Unfortunately, I found I couldn’t use the plugin once I had written it, because the ESV publishers require you to subscribe to the idea of inerrancy in order to use their service.  For the details, you can read the post on my ESV plugin.