Home > Crossway Blog > Archive for August, 2005

Archive for August, 2005

New ESV Buttons

James Coleman was kind enough to create five web buttons for your site if you want to show your support for the ESV in that way.

You can copy/paste them below, or you can visit our Web Buttons page for more instructions and other designs.

Thanks a lot, James.

Visit www.esv.org to learn about the ESV Bible Visit www.esv.org to learn about the ESV Bible Visit www.esv.org to learn about the ESV Bible Visit www.esv.org to learn about the ESV Bible Visit www.esv.org to learn about the ESV Bible

August 5, 2005 | Posted in: ESV,General | Author: Crossway Staff @ 9:47 am | 1 Comment »

Scripturizer for Javascript

Scott Yang has written an innovative and useful script for website owners: Scripturizer for Javascript. It scans the text of a webpage and automatically finds and links Scripture references to the ESV. But it also goes a step further–clicking a link makes the text of the ESV for the linked passage appear in a popup frame:

Revelation 4:11 in a popup that appeared after clicking a link put there by Scripturizer

The beauty of this script is that it’s all client-side: you upload it to your web server, link to it from your webpages, and you never have to think about linking Scripture references again. The script also works for other Bible versions, but only the ESV will give you a popup. Learn more about the script at Scott’s site.

August 3, 2005 | Posted in: Digital,ESV | Author: Crossway Staff @ 9:17 am | 1 Comment »

Tim Challies: Using Scripture in Books

Tim Challies, who frequently writes about the state of the Christian bookselling industry, talks about how to use Scripture in books:

The goal in prooftexting or quoting from the Bible is to accurately represent and interpret God’s Word. We do not use the Bible to prove what we want it to say. Rather, we turn to the Bible to learn from God Himself, and then share what we have learned with others. We must have our priorities straight.

He then goes on to define an “essentially literal” translation.

Formal Equivalence (also known as Word for Word, Literal Translation or Essentially Literal) – Formal equivalence attempts to represent each word of the original language with a corresponding word in the English language. This allows the reader to know, as closely as possible, what God actually spoke through the authors of the Bible. The merit of this method is that it allows intimate access to the originally inspired words for those who do not speak the languages the Bible was written in. The downside is that it is possible for these translations to be awkwardly worded and follow difficult sentence structures. Examples are the New American Standard Bible and the English Standard Version.

Finally, he lists four guidelines that apply just as much to preaching sermons as they do to writing books. Here are two of them. To learn the rest, you’ll have to read his post.

  • Use a default translation that is essentially literal
  • Use translations that are familiar to readers

Several of Tim’s points (coincidentally) dovetail nicely with our recent video.

Full disclosure: Crossway regularly provides free review copies to Tim for one of his other sites.

August 1, 2005 | Posted in: ESV,General | Author: Crossway Staff @ 10:12 am | Comments Off »