Discontinued RickLivermoreOnlineReaderble Study Blog

Discontinued RickLivermoreOnlineReader
(I am a fan of Tubi TV - Faith Copyright © 2019 Tubi, Inc. Tubi is a registered trademark of Tubi, Inc. All rights reserved.)
The new posts that I will be writing will go on another blog I have. There is an rss feed on this blog which you may choose to use to assist you with transitioning over.
There is a better way: just click this link once, save the web page to your bookmarks, and stop reading the blog located at this old url.

Saturday, November 3, 2018

Fwd: Inspiration and Translation (Acts 11:22)

Forwarded message ---------
From: billmounce.com <newsletter@billmounce.net>
Date: Mon, Oct 22, 2018 at 12:33 PM
Subject: Inspiration and Translation (Acts 11:22)



Monday w/ Mounce

Inspiration and Translation (Acts 11:22)

I am delivering a paper at the national ETS meeting in a few weeks, so thought I would get your feedback on a few items.
Verbal plenary inspiration means that all ("plenary") of Scripture is inspired, and the inspiration extends to the words used and not just general ideas ("verbal"). The question is whether or not a formal equivalent type of translation respects verbal inspiration better than a functional equivalent type of translation.
And just to be clear, I believe in verbal, plenary inspiration (and inerrancy).
The question really does not touch on the aspect of "plenary." As I have sat on both the ESV and the NIV translation committees, I have seen first-hand how evangelical translators, regardless of the translation theory adopted, agonize over every Hebrew and Greek word. In both committees, we have spent hours trying to determine the best translation of each word understood in context. The fact that some of the words are rarely read makes no difference; I mean, how often do we read, slowly and devotionally, though Numbers 1–7, apart from the Aaronic Blessing (6:24–26)? Nevertheless, all of Scripture is inspired and needs to be translated carefully.
As to the verbal side of the discussion, one point I want to make is that any connection between verbal inspiration and the words used can only apply to the original Greek and Hebrew. God did not inspire the words, "For God so loved the world." Inspiration extends to οὕτως γὰρ ἠγάπησεν ὁ θεὸς τὸν κόσμον.
In other words, translations are outside the scope of the discussion. No translation is inspired, despite what certain pockets of people think about the KJV. English wasn't a language until centuries into the second millenium, and the KJV translators certainly never claimed that their work was inspired.
So with those facts stated, does one form of translation theory respect "verbal plenary inspiration" more than another?
Take Acts 11:22 as a test case. In reference to the revival in Antioch, Luke writes that "the report of this came to the ears (ἠκούσθη δὲ ὁ λόγος εἰς τὰ ὦτα) of the church in Jerusalem, and they sent Barnabas to Antioch" (ESV). But let's pull this translation apart a little.
  1. It dynamically translates λόγος as "report," not the gloss "word."
  2. "Came" is nowhere in the semantic range of ἀκούω.
  3. "To the ears" is nonsensical English. Yes, you can figure out what it means, but certainly the meaning of God's verbally inspired verse is much closer to the CSB, "News about them reached."
Did God inspire Luke to say, "was heard but the word into the ears," or did God inspire Luke to say that "news of this reached the church in Jerusalem" (NIV)? And does a functional equivalent translation that conveys the meaning accurately in understandable English better respect the doctrine of verbal plenary inspiration than a translation that uses archaic, idiomatic language that makes understanding more difficult? I think so.
What do you think?
This e-mail has been sent to ricklivermore. Click here to unsubscribe.
523 NE Everett St, Camas WA 98607


Brought to you by: Rick Livermore online reader
https://ricklivermoreonlinereader.blogspot.com

Ebates Coupons and Cash Back

I am a fan of
Awaken Church
4132 E Pecos Rd,
Gilbert, Arizona 85295

No comments:

Post a Comment