Pope Francis, The Lord’s Prayer, and Bible Translation

Pope Francis recently suggested on Italian television that the petition in the Lord’s Prayer, “Do not lead us into temptation” (Matt 6.13; Luke 11.4), “is not a good translation because it speaks of a God who induces temptation.” He added, “It is Satan who leads us into temptation; that’s his department.” He argued that the verse should be rendered, “Do not let us fall into temptation.”

A myriad of implications arise from the pontiff’s statement. Among them I list just three: (1) Have translations of the Bible gotten this verse wrong for 2000 years, only now to be corrected? (2) What is the nature of translation? (3) Do we have the right to change the wording of the original because it seems to contradict what Scripture says elsewhere?

Screen Shot 2017-12-12 at 7.29.13 AM

Matthew 6 in Codex Sinaiticus

(1)       Have translations of the Bible gotten this verse wrong for 2000 years?

Jerome’s Vulgate—the version that has been the official Bible of the Catholic Church for centuries—reads here ne inducas nos in temptationem: “Do not lead us into temptation.” Perhaps intentionally, but certainly ironically, the pope said in his interview, “ti induce alla tentazione satana è quello ufficio di satana.” That is, Satan is the one who induces or leads us into temptation, not God. He used the Italian equivalent to Jerome’s Latin (‘inducas’ means ‘lead’ or even ‘induce,’ as the English cognate suggests), but seems to deny what the Vulgate plainly says.

In 1979, the Nova Vulgata became the official Catholic translation (after Vatican II, it follows the Greek and Hebrew more closely), yet it too says ne inducas nos. So, the pontiff is not only going against modern translations but even his own Vulgate.

Other translations also read “do not lead us into temptation” or the like (e.g., “lead us not”): KJV, ASV, RSV, NASB, NIV, ESV, HCSB, NET, WEB, Lutherbibel, Nouvelle Edition de Genève, Reina Valera. Others have “do not put us to the test,” “do not bring us into hard testing,” or “do not subject us to the final test” (NJB, TEV, REB, NABR; the NJB and NABR are Catholic translations).

It may be surprising, however, to discover that a few modern translations come close to Pope Francis’s version. The New Living Translation (2nd edition), a Protestant Bible, has “don’t let us yield to temptation.” The Nouvelle Version Segond Révisée, another Protestant translation, has “ne nous laisse pas entrer dans la tentation” (“do not allow us to enter temptation”). The Nuova Riveduta of the Sacra Bibbia, an Italian Protestant work, reads “non ci esporre alla tentazione” (“do not expose us to temptation”). The NLT and SEGR both accent what might be called the passive or permissive will of God (i.e., “don’t let us”) rather than the active (“don’t lead us”); the Nuova Riveduta seems to be halfway between ‘lead’ of the standard translations and ‘let’ of the outliers.

Nevertheless, there seems to be an overwhelming consensus that “do not lead us” or the like is how the text should be rendered. (We will examine the Greek shortly.) But the few that have gone against the grain—and have been on the market for many years—have not created nearly the reaction of Pope Francis’s latest provocation. Perhaps this is due both to the fact that the pontiff said this and that it stands in direct contradiction to the Vulgate and other Catholic versions. But this leads us into the question of translation philosophy.

 

(2)       What is the nature of translation?

There are two broad theories of translation today—formal equivalence and functional equivalence. Formal equivalence means that the translation attempts to retain the wording and syntax of the original language as much as possible. Functional equivalence means that the translation gives a higher priority to the semantics of the original, bringing out the force of original text regardless of how it is worded.

Brief history of English translations

Both of these have pros and cons. On the one hand, it is a myth that a so-called “literal” translation is more accurate. Many believe that the King James Bible is the most literal translation available. But even the original preface of the KJV noted that the translators’ objective was as much literary quality as it was accuracy. The Authorized Version is probably the only literary masterpiece ever produced by a committee—and it’s a translation no less! If it were extremely literal, this accolade would never have been made about the KJV.

In fact, the Revised Version of 1885—the first English translation done by a committee since the KJV (or AV) appeared in 1611—was done by a committee of British and American scholars who wanted to replace the King James with “King Truth.” But the translation was not palatable because it was too stiff, hardly readable, downright ugly. Ironically, the RV was difficult to read not because of archaisms as much as because of slavish literalism. The sales were awful, and the American Standard Version of 1901 was something of a reaction to it by the Americans on the RV committee. This is still wooden English, though an improvement over the RV. (The NASB has followed in the train of the RV and ASV.)

But in 1952, the Revised Standard Version appeared. Its understated elegance and good English made it memorable. It truly was a revision in the line of the King James Bible. The ESV and the NRSV have continued this formal equivalence philosophy with simplicity, understated elegance, memorability, and accuracy. As Bruce Metzger, the chairman of the NRSV translation committee, stated, the objective followed by the NRSV translators was to “be as literal as possible, as free as necessary.”

Other translations have followed a more functional equivalent philosophy. The NIV and New English Bible were the first major English translations in the last three centuries to break completely from the Tyndale-Geneva-King James chain. The New English Bible (now, Revised English Bible [REB]) is much more of a functional equivalent work than the NIV, and it is also much more elegant and memorable than the NIV. But the NIV (and its revision, the NIV 2011) is both very accurate and very readable. It has become the most popular Bible translation in any language in history. And yet, even the NIV reads “do not lead us into temptation” in Matt 6.13.

All translation is interpretation

It is important to recognize, however, that all translation is interpretation. The reason is that the syntax and lexical mapping in one language never match exactly that of another language. The context determines the meaning. A so-called “word-for-word” translation is quite impossible for anything more than a short phrase or sentence. In this passage, for example, the word translated “temptation” is the same word that is elsewhere translated “testing.” Interpretation is required; translators cannot simply leave the word to allow for both meanings since “temptation” has connotations of sin while “testing” does not. However, in this passage there is good reason to see πειρασμός (peirasmos) as bearing the force of temptation, as we will see below. But the point is that an interpretation of the text is already done in even the most formal equivalent translations of this passage. In one sense, the pope’s rendering is an interpretation of an interpretation.

Many on the functional-equivalent side of the translation debate are determined to clear up all ambiguities in the text, to make everything crystal clear. Some of these translators have little training in exegesis. Typically, the less training they have in the original languages and biblical studies, the more they assume that the Bible is perfectly clear everywhere; it just needs to have the proper functional equivalence to bring out its meaning. But this is terribly naïve.

Students in seminary often come into the program thinking that once they get some Greek and Hebrew under their belts the interpretive issues will simply disappear. The reality is that study in the original languages in some places will expand on the interpretive possibilities, in others shrink them. But most importantly, such training will replace a misinformed list of options for one that is better informed and at least has some validity.

Ideally, a translation should give the readers of the Bible in their own language the same interpretive options that a reader of the original will have. And this means that it is important for readers of the Bible to struggle with the same, often intentional, ambiguities found in the original text.

When the NET Bible was in beta-mode, we field-tested it on the Internet. Comments were welcome; hundreds of thousands poured in. Some professional translators committed to functional equivalence argued with our rendering of ἐν Χριστῷ as “in Christ.” They pointed out that this hardly communicated anything in English and that it was difficult to grasp Paul’s meaning of his favorite phrase (he uses it 73 times). They noted correctly that Paul uses ἐν Χριστῷ in a variety of contexts and in a variety of ways. And they wanted us to reflect those nuances in every place. Their view was in line with what Lady Oppenheimer wrote in her book Incarnation and Immanence ([1973], p. 17): “Christians have a great deal to say about the ways in which people can be related to God and to each other, and many of the things they wish to say take for granted the possibility of certain sorts of close relationships which are not on the face of it compatible with common sense.”

We rejected their input on this point and decided to keep the translation “in Christ.” Why? Because we believed that the modern English reader should have the same semantic options as the original reader. Close analogies to this sort of language are not to be found in Greco-Roman literature. This means that Paul’s original readers had to work hard to get at the apostle’s meaning, ultimately coming to see the rich tapestry of “in Christ” as deeper and richer than any functional equivalent could provide. In this instance, we felt that clearing up the ambiguity of the text would rob the modern reader of the joy of discovery and the value of thinking deeply about Scripture.

There are times, however, when retaining the original ambiguity does not help the modern reader. In such cases, interpretation is required of the translator. In Rom 3.22 the NET translators felt that translating διὰ πίστεως Ἰησοῦ Χριστοῦ as “by faith of Jesus Christ” was simply too ambiguous. This is exactly what the KJV has here, and it communicates poorly what the meaning of the original is because it does not interpret. Although one or two scholars have suggested that πίστις Χριστοῦ means “faith of Christ”—that is, the faith that Christ himself had—this is not a popular view. The two leading options are either “faith in Christ” or “the faithfulness of Christ.” How could they be so disparate? The reason is due to one lexical and one grammatical problem. πίστις lexically can mean faith or faithfulness. And the genitive Χριστοῦ can be subjective or objective. If objective, Christ is the object of πίστις (and hence, “faith in Christ”); if subjective, Christ is semantically the subject (“the faithfulness of Christ”—that is, that he is faithful). Leaving the text as “faith of Christ” hardly allows for either of these interpretive translations. The ambiguity in English is not the same as it is in Greek. In this case, a more literal translation ends up being the worst translation. The only real choice here is for translators to commit to one interpretation since leaving it neutral actually gives the wrong impression of the meaning to the English reader.

So then, should translation be formally equivalent for functionally equivalent? Neither one is adequate. Faithful equivalence is really required—faithful to the meaning of the original. If this can be accomplished by following a somewhat formal equivalent (since a completely formal equivalent is quite impossible), fine. But Greek and Hebrew are structured so differently that to force both of them into one kind of translation model is a one-size-fits-all mentality that simply won’t work.

On the one hand, there are hundreds of places when formal equivalence simply doesn’t help the English reader understand the interpretive possibilities of the original text. Yet that is the goal of formal equivalence. As we have said, the reality is that every translation is an interpretation. The question is how much we should try to interpret in any given place.

On the other hand, functional equivalence translations often take liberties with the text by offering a less-likely or even an illegitimate rendering, and they frequently make the text clear for a reader who could, in their own native language, figure out what the author is talking about. Some of the most stunning prose in the Bible is full of figurative language that to reduce it to its referential meaning is to destroy its beauty, thought-provoking nature, connotative force, and lingering memorability.

The Lord’s Prayer and translation

The pope’s rendering certainly is on the functional-equivalent side rather than the formal-equivalent side. But does that make it illegitimate?

In this instance, the bishop of Rome has taken many liberties with the text, both linguistically and contextually, thereby robbing the modern reader of seeing the connections that Matthew himself has laid out.

Not only is the Greek in both Matt 6.13 and Luke 11.4 textually certain (variants for “do not lead us into temptation” are trivial amounting to minor spelling differences), but the syntax is clear. The verb in the petition “lead” is an aorist active subjunctive (εἰσενέγκῃς); with the negative particle, “do not lead” is the idea. The pope wants it to mean “allow” which speaks instead of God not permitting something rather than him actively leading us. And the pontiff seems to have assumed that the Greek “lead into temptation” means “permit to fall into temptation.” Several lexical, syntactical, and interpretive shifts are seen here.

The broader context of Matthew’s Gospel may give us a clue as to why the Lord said, “Do not lead us into temptation.” Immediately after Jesus’ baptism, we are told that he “was led up into the wilderness by the Spirit to be tempted by the devil” (Matthew 4.1). The Greek text indicates that the purpose of the Spirit’s leading Jesus into the wilderness was so that he would be tempted by the devil (“to be tempted” [πειρασθῆναι] is an infinitive of purpose, giving the purpose of the Spirit’s leading). Mark words this even more starkly: “Immediately the Spirit drove him into the wilderness” (Mark 1.13).

Evidently, there is a sense in which Jesus was delivered into the hands of the evil one, by the Holy Spirit himself, to be tempted. But the Greek here makes an interesting point about who is responsible for what. Two passive verbs are used in Matt 4.1— ἀνήχθη (“he was led”) and πειρασθῆναι (“to be tempted”). The agents are listed with identical prepositions: ὑπό. This is the preposition used especially for ultimate agent. It is rare to see ὑπό followed by πνεύματος (“Spirit”) in the NT (only five passages). Doing so here, Matthew shows that the Spirit is not subordinate to the devil but is the agent ultimately responsible for leading Jesus into the wilderness, while the devil is the ultimate agent of the temptation. The Spirit is not responsible for that. The Spirit did not tempt Jesus, but he did lead him to be tempted. The balance is intentional: leading into temptation is not the same as tempting. God the Holy Spirit led Jesus into temptation, but he did not tempt him. Wrestling with the implications of this requires more than a little reflection.

Although Satan’s purpose was to destroy Jesus before he ever went to the cross, God’s purpose in using Satan was painted on a broader canvas. God tests; Satan tempts. The Son of God went through similar testing as the children of Israel in the wilderness. They were there for forty years; he was there for forty days. Where they failed he succeeded.

Further, the temptation that the Lord faced was the ultimate temptation—the offer of the entire world on a platter. Jesus can ask the disciples to pray that the Father would not lead them into temptation and that God would deliver them from the evil one precisely because Jesus himself faced the ultimate temptation by the evil one. Whereas the Spirit led Jesus to be tempted, Jesus asks the Father not to lead his disciples into temptation; whereas Jesus was delivered over to Satan for tempting (testing from the Father’s perspective), Jesus prays that his followers will be delivered from the evil one. It is precisely because of Jesus’ substitutionary death and life that this prayer can be recited today by Christians with the full assurance that God will answer us.

Pope Francis’s translation, however, subverts all this: “do not let us fall into temptation.” The original text speaks clearly of God leading, not permitting. To tamper with the wording misses the connection with the Lord’s temptation.

 

(3)     What does the original text really mean and do we have the right to change it in translation?

 The pope makes a good point that our heavenly Father does not tempt us. And yet, he argues that point from a theological construct derived elsewhere in the Bible (see James 1.13). “Do not lead us into temptation” does not mean that God tempts us; the petition is for God’s protection from the evil one, as the rest of Matt 6.13 says.

 Further, the notion that we can change the wording to fit the meaning that we find somewhere else might actually be doing a disservice to the biblical authors’ intentions. The Bible is full of paradoxes, figurative language, jolting imagery. To simplify and pacify such language cuts off the legs of its literary and even spiritual power.

At bottom, what the pontiff is doing is interpretation—but interpretation that removes the tension and paradox from the text, is not true to the force of the original, and buries the connection to Jesus’ temptation. Better to leave the text alone and allow God’s people to experience the joy of discovery of the meaning of Holy Writ.

41 thoughts on “Pope Francis, The Lord’s Prayer, and Bible Translation

  1. Thank you for this enlightenment about the text and translations.

    I think you would be interested in these facts: In Brazil, the most common version of “Our Father” prayer says “não nos deixe cair em tentação” (do not let us fall into temptation). But the written text of most translations says “não nos induzas à tentação” (do not lead us into temptation).

    In the spoken language the change that the Pope proposes is already common here in Brazil. Once the Pope comes from Argentina, I searched for the “Oir Father” version most common in Argentina. It also states “No nos dejes caer en la tentación” (Do not let us fall into temptation).

    For most Latin-American people, this change wouldn’t be really a change, but a confirmation of what they already pray.

    Like

  2. Bob

    Very helpful article Dr. Wallace. Not only do you articulate well the intention of the text, buy you provide a great refresher on translation and textual criticism. I fully concur that all translation involves interpretation despite some who want to deny that.

    Like

  3. Pingback: The Pope is Pope-ing with Translation – Theology and Apologetics. The Topics, The Problems, The Glories.

  4. Joyce Rebecca Nichols

    Interesting is it just to conform to the South American version or is it because the Pope now wants to start changing the meaning of scripture and see how people will react. Which most won’t so one thing can lead to the next. We will have to wait and see.

    Like

  5. Pingback: Is the Pope right about the Lord’s Prayer? | Denny Burk

  6. Pingback: Linkathon! - PhoenixPreacher

  7. Pingback: Dan Wallace Corrects Popes Francis – beliefspeak2

  8. Pingback: Change The Lord’s Prayer? | The Watchman

  9. Pingback: Pope Francis, The Lord’s Prayer, and Bible Translation | A disciple's study

  10. Shirley Landmesser

    I thoroughly enjoyed reading this article. Thank You!

    The Roman bishop’s thoughts on the wording of the Lord’s Prayer may come out of the Roman Catholic view of authority: the Roman Catholic Church having equal or more authority than Scripture. Something I do not ascribe to.

    Like

  11. Pingback: The Pope and “Lead us not Into Temptation” Interpretati | The Domain for Truth

  12. Pingback: Should the Lord’s Prayer Be Changed? -

  13. Sadly the Portuguese translation, of a Dutch Calvinist minister called JOAO FERREIRA DE ALMEIDA, – yes, probably a distant relative; I am Almeida too – renders in all Portuguese translations, revised, corrected, and original, “…do not let us fall into temptation…” – Terrible! I think this is attempt to eliminate the perceived contradiction with the statement by James, who in his book states in chapter 1 vs 13 “Let no man say when he is tempted: I am tempted of God for God cannot be tempted with evil, NEITHER TEMPTETH HE ANY MAN” (no wonder Luther had no love for James… the papist favorite book!)
    So, if Jesus asks God “do not lead us into temptation”, how can James state that “…God doesn’t tempt any man…”? Well…

    Like

  14. Pingback: To Translate or Interpret? | Epistles of Thomas

  15. Pingback: The Lord’s Prayer kerfuffle, from a Hebraist’s perspective | Ancient Hebrew Grammar

  16. Mark Maund

    Thank you for your kind and honest assessment of the truth. I pray those who seek to know the truth will follow the example of the Bereans: “Now the Bereans were of more noble character than the Thessalonians, for they received the message with great eagerness and examined the Scriptures every day to see if what Paul said was true” (Acts 17:11).

    Like

  17. While the word “peirasmon” could mean “temptation”, it also means “test”, or “trial”. This double beaning is present in the Lord’s prayer. It is not wise to reduce its meaning only to half of its original intent. Leave it alone!

    Like

  18. Pingback: Links to Begin the Week - RobertKrupp.com

  19. Felmar Roel Rap. Singco

    Thanks for this great article, just read this here.

    Thanks for putting clarity in these things.

    It only shows that Christian exegesis and theology are so full and alive and well!

    Like

  20. wloescher

    Thanks for the article. You have a typo, “for” should be “or” in the phrase: “So then, should translation be formally equivalent for functionally equivalent?”

    Like

  21. Apparently, the Pope would like to change the translation in order to harmonize the passage theologically with other verses. However, perhaps the somewhat ambiguous, thought-provoking nature of this verse should lend ourselves to deeper study in keeping with the perspicuity of scripture.

    Like

  22. It may make a change for those who like to pontificate and be called Popes , to show an interest in the Scriptures , which is the word of God . For 1500 years previous Popes may not have shown much interest in scripture it seems ,other than to supress its general use even to the extent of forbidding its use when they had much more world power than now .
    I wonder if this present Pope is a linguist and expert in the biblical languages and able to comment on the passage which aroused his interest ?. Look up Faraboveall.com . Thank you .

    Like

  23. Pingback: POPE FRANCIS GAINS ALOT OF CRITICISM ON WORKS TO RE-WORD THE LORDS PRAYER – KENYA YOUTHS RESCUE TEAM

  24. Pingback: “Theistic Evolution:” Was Everything Perfectly Good Before the Fall? | Veracity

  25. Pingback: Open-Mindedness: II. Authority and Freedom – Books On Trial

  26. Pingback: Pope! |

  27. George

    My only complain of his statements is that his preference is not something that is sudden, nor unheard, in Catholicism; specifically, in Chinese.

    * The classical chinese version by Matteo Ricci: 又不我許陷於誘感。
    * Chiense CCC, 2759 / Dun Scotus Translation: 不要讓我們陷於誘惑,

    Both of them translate to “do not let us fall into temptation”

    Like

  28. Pingback: Is the Pope a Biblical Expert? – The Two Cities

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s