Does ὑποτασσω mean ‘respect’ in Ephesians 5?

It’s not often that a political event provides fodder for a BBB post. But I’m going to take fodder from Iowa (a lot of fodder is harvested there) where the Republican candidates for President of the U.S. debated each other last night and turn it into grist for this BBB post.

Michelle Bachman, an evangelical Christian and the only Republican woman candidate, was reminded by co-moderator Byron York:

about her 2006 remark that her “husband said you should study for a degree in tax law. You said you hated the idea. And then you explained, ‘But the Lord said, ‘Be submissive. Wives, you are to be submissive to your husbands.’”

Then York asked Bachmann:

As president, would you be submissive to your husband?”

Bachmann answered:

“Marcus and I will be married for 33 years this September 10. I’m in love with him. I’m so proud of him. What submission means to us, it means respect. I respect my husband. He’s a wonderful godly man and great father.

“He respects me as his wife; that’s how we operate our marriage,” she continued. “We respect each other; we love each other. I’ve been so grateful we’ve been able to build a home together. We have wonderful children and 20 foster children. We’ve built a business and life together, and I’m very proud of him.”

News commentators, and news and religious bloggers have been having a hayday (hay is also grown in Iowa) commenting on this exchange.

And now we at BBB get our chance to weigh in on the translation question which is related to that exchange:

Does the Greek word ὑποτασσω in Ephesians 5:21–and assumed by almost all Bible translators to be implied in the next verse–mean ‘respect’ or something else?

Last night Bachmann did not quote from Ephesians 5 as she did in 2006. Instead she said that submission means ‘respect’ within her marriage to Marcus Bachmann.

Will Bachmann’s definition of submission be satisfactory to those who emphasize wives submitting to their husbands today? Does it bring home the bacon (a lot of hogs are raised in Iowa) for you, as you understand the meaning of ὑποτασσω?

All comments on this post will be moderated. Only those which address the meaning of the Greek word ὑποτασσω will be approved for posting. No comments will be permitted which address any other gender questions in Bible translation, unless they directly relate to the translation of ὑποτασσω. This is not an attempt to censor BBB comments, but, rather, to keep the comments from flaming or attacking any Bible translators or anyone else. Some got the mistaken notion from a recent BBB prohibition on discussion of gender on the WELS post on the NIV2011 that gender issues in Bible translation could not be discussed on BBB. We BBB bloggers did not intend any such prohibition. Gender is a topic critical to current English Bible translation and must be discussed. But there must be boundaries on how we discuss it and what is discussed at any one time, so that comments can stay on-topic for each post.

—-

UPDATE (Aug. 15): Comments which are non-translational but otherwise pass BBB gudelines now appear on a spillover blog:

BBB-extra

Additional details about this new blog appear as a comment from me today on this post.

a translation opening

For my real job I am currently checking a translation of Psalms in a tribal language of South America. Last December I asked the translation team a question about Psalm 18.9:

wl-12/13/10: How natural is it for [the X speakers] to refer to the sky “opening up”

Yesterday I read the team’s response:

One [translator] says that it is natural to say: ‘The sky is open this morning’, meaning that there are no clouds, just a big expanse. The other [Mother Tongue Translator] says that they use this expression when after it rains, the sun comes out or when after there are a lot of clouds the sky clears.

After this response, in terms of the CANA parameters described in my preceding post, I now believe that the translation for this verse is natural. The translators appear to have an important spiritual leadership role in their tribe, so the translation seems to be acceptable. The translation seems to be understood readily, so it seems to be clear.

But is it accurate? If you question its accuracy, what do you suggest might be inaccurate about it?

CANA translation

Remember the first recorded miracle of Jesus? That’s right. He turned water into wine when the wine ran out at a wedding feast.

Good Bible translation is like that miracle wine. Such translation can take words that are like water, good for you, adequate for understanding, but without much flavor, and make a miracle out of them, impacting you, leaving you with a taste in your mouth that you cannot forget.

CAN has been a traditional acronym among missionary Bible translators. It stands for Clear, Accurate, Natural. Those are the qualities that our Bible translation courses have taught that a good Bible translation should have. Such a translation should be as Clear as the original (but no clearer and certainly not more obscure). Above all, it must be Accurate. And it should follow the Natural patterns of the target language, at least as much as the original biblical texts followed the natural patterns of their languages. (And, yes, there were times when for poetic effect or authorial lapses, natural patterns were not followed but they are in the minority not the majority of biblical text passages.)

For years missionary Bible translators were taught the CAN approach. It was good. It produced translations which were of high quality. But sometimes the translations were not used much. Sometimes they languished in warehouses. Reasons for the lack of use have been numerous, including people’s feeling of inferiority about their own language in contrast to a higher prestige LWC (language of wider communication), such as Spanish, English, or French.

But in more recent decades, those who care about unused translations have noted another important reason why translations are not used, Acceptability. No matter how Clear, Accurate, and Natural a Bible translation might be, if church gatekeepers and parishioners do not like a translation it will not be used.

There are many reasons why a translation may not be liked. The reasons are often discussed on this blog. One that is very important to many Bible users is that a Bible translation may not sound the way people think a Bible should sound. If there has been one or more Bible translations already in the language which have gained a prestige status, they will not be displaced by a newer Bible translation unless the newer translation also has the traditional sound. For such Bible users, for any new translation to replace an older one, the new one has to be “traditioned” (a verb used by John Hobbins).

Bible version acceptance is a point that John Hobbins keeps repeating in his posts and comments and it is a point which can make or break a new translation. Hobbins, like other ministers, may personally prefer some other Bible translation(s), but he knows that if the Lord’s Prayer doesn’t sound like the Lord’s Prayer to his congregation, he might just as well leave the prayer out of the liturgy than to try to have it prayed in clearer, more accurate, or more natural English. [John, I hope I'm not putting words in your mouth here. If I am, we can change your name to Pastor John Doe since the principle remains: people don't want anyone to "mess" (another of John's terms about Bible versions!!) with their Bible.]

I don’t have a favorite English Bible version. Instead, I have several favorites which serve me well, often for different purposes.

I can’t say which is the most accurate English Bible versions. A few days ago I was again asked by someone which is the most accurate English Bible version. I answered honestly, “It is not possible to say. There are many accurate English Bible versions. Almost every English Bible translation team has attempted to make translation accuracy their highest goal.”

I can tell you which Bible versions impact me the most spiritually. I hope that is one of the criteria that pastors and congregations use to evaluate which version to use as pulpit and pew Bibles. But I don’t know that it is.

I do know that people want their Bible to sound like a Bible. If we honestly believe that people would get a more accurate, clearer understanding of the Bible through some non-traditional sounding Bible, we have to be willing to set an example to others of the benefits that can come from CAN Bible translations. If we do, and if some people gain spiritually, emotionally, and intellectually from a Bible version outside a traditional mold, it requires a miracle that helps people Accept the newer version.

Such acceptance is a CANA miracle. The miracle at Cana was only one of Jesus’ miracles. And Bible miracles still take place through traditional sounding Bible versions. But there is something special about “the taste of new wine” (that would make a good book title, eh?!!) that satisfies the celebrants at CANA.

Breaking things apart

Translation has two separate steps. One: interpretation, i.e. studying the original text in its linguistic and cultural context. Two: translation, i.e. choose words in another language and put those words together in a certain order with the intention of communicating as clearly and accurately as possible the assumed intended meaning to a new audience.

The interpretation process requires a good understanding of the source language, but also of the cultural and religious context of the writer as well as the originally intended audience. The translation process requires that assumptions are made about the expectations and Biblical knowledge of the new audience. It is because of those varying expectations (and varying interpretations) that different translations are made of the same original text.

In this post I want to limit myself to how one breaks things apart. In the early Greek manuscripts words were not separated by spaces, and sentences were not marked by punctuation. Paragraph breaks were not indicated. An extreme postion of “translating without interpretation” would be to NOT usewordbreaksin English and never use any punctuationbutwhatwou ldpeoplesaytothat. We are so used to such breaks as well as punctuation, that such a translation would be considered unreadable. No translation has gone to that extreme, so every translator MUST interpret how to break up the original text before a translation can be attempted.

There are many examples where it is a matter of interpretation whether a sentence is to be interpreted as a statement or a question. It is also a matter of interpretation where a speech quotation ends. I won’t mention them here.

Sometimes it is not clear whether there should be one or two sentences. For instance, John 14:1b could be one sentence: Trust in God and trust also in me. Or it could be two sentences: You are trusting in God. Trust also in me. Apart from lack of punctuation, the Greek language does not differentiate between the present command form “Trust” and the indicative present “You are trusting”. NIV said: “Trust in God; trust also in me.” This was changed in NIV2011 to: “You believe in God; believe also in me.” The change is reasonable, since it would be a given that the disciples already believed in God. But at the same time it is a choice whether to say “trust” or “believe” in English. When the belief is directed towards a person rather than a statement or doctrine, the sense is more of trust than simply believe. The Greek text has an emphasis on also in me in the second part. Because of that it is more likely that the first part is a given and the second part is an addition to the first part, i.e. you already trust in God. Since you do that, (and since I have come from God,) you should also put the same trust in me. A third option, then, which is neither the old or new NIV could be: “You have already put your trust in God. Trust me, too.” Translation involves many choices. In many cases it is not simply a matter of right or wrong, but a relative degree of clarity and accuracy.

A different issue is found in Rom 7:14. There is a Greek word here which could be οἴδαμεν, meaning “we know”. However, it is quite possible that it should be broken apart into two words: οἴδα μὲν, which means “while I know”. Both options fit the context, and both options have been employed in translation. Which is correct? I don’t know. We don’t know. I lean towards “I know”, but the tradition leans towards “we know”.

The Greek text had no paragraph breaks, so again it is a matter of interpretation. As an illustration, let me discuss 1 Cor 14:33-36. The NET, RSV and others chose to have a paragraph from 33b-36. The old NIV had a paragraph from 33b-35. The new NIV and NLT have a paragraph from 34-35. So, it is a matter of interpretation both where to begin and where to end this paragraph. Most of the arguments for one or the other are underlyingly theological, although the translators and commentators usually deny that. I’ll try to steer clear of theology.

First, a few manuscripts in the Western tradition do not even have verses 34-35, but put them after v. 40, where they do not fit very well. G. Fee is one of the very few who argue that these verses were not original at this place. The manuscript data is stongly in favour of these verses being at this place.

Second, is the phrase “As in all the congregations of the saints” to be attached to the preceding sentence: “After all, God is not a God of anarchy, but of peace.” This last sentence explains and gives background for v. 32 where Paul said that “the spirits of prophets are subordinated to prophets.” The IVP Bible Background Commentary has a useful note about this: “In most contemporary Jewish teaching, prophecy involved complete possession by the Spirit; one dare not seek to control one’s utterance. For Paul, however, inspiration can be regulated, and regulating the timing and manner of one’s utterance is not the same as quenching it altogether. On regulating one’s spirit, cf. Proverbs 16:32 and 25:28.” Some Corinthians may also have been comparing with ecstatic spiritual activity in contemporary pagan culture, but a true Christian prophet decides when and where to bring the word he or she has received. There is no force or ecstacy involved, although it does feel like a burden to share. Our God is a God of peace, not of anarchy, insurrection, rebellion and confusion (Greek: ἀκαταστασία). It would be very strange to add “as in all the churches” to this final statement as if God was only a God of peace in the churches. Verses 32 ands 33a are general statements. Both the NA and UBS Greek texts introduce a paragraph break before 33b. If this comparative phrase is moved away from 34, we lose the introductory background to and logical basis for 34. Paul is correcting a misbehavior in Corinthian congregations that did not take place in other church congregations in other cities. It was apparently caused by Greek culture and tradition. So, Paul appeals to the Corinthians to follow the practice that is found in all the other churches. This ties in well with the final sentence in the paragraph, namely v. 36: “Or did the word of God originate from YOU? Or are YOU the only ones who have received it?” These final rhetorical questions indicate a rebuke and also an admonition to the Corinthians to not think that they are unique and different from all other churches in other places. I won’t discuss the controversial verses 34-35 except to quote from the IVP Background Commentary: “Informed listeners customarily asked questions during lectures, but it was considered rude for the ignorant to do so. Although by modern standards literacy was generally low in antiquity (less so in the cities), women were far less trained in the Scriptures and public reasoning than men were. Paul does not expect these uneducated women to refrain from learning (indeed, that most of their culture had kept them from learning was the problem). Instead he provides the most progressive model of his day: their husbands are to respect their intellectual capabilities and give them private instruction. He wants them to stop interrupting the teaching period of the church service, however, because until they know more, they are distracting everyone and disrupting church order.”

Wallace completes NIV 2011 review

Dan Wallace has completed his blog series, reviewing NIV 2011. You can read part three here and the final part here.

Wallace: Literal translations “inevitably inaccurate”

Dan Wallace has now posted the second part of his review of NIV 2011. This is a follow-up to part 1 which I posted about yesterday.

A large proportion of part 2 is in fact an excursus, which might have been better published as a separate essay, “What Makes for an Accurate Translation?” He writes that, in the light of possible misunderstandings of part 1, he needs to “correct the frequent perception that literal = accurate, and not-so-literal = inaccurate.” And he does so in remarkably strong terms, stating that (with his own emphasis)

a formally equivalent, or ‘literal,’ translation of the Bible will inevitably be uneven and inaccurate.

He justifies this statement by discussing various renderings of Matthew 1:18, Luke 20:16 and Romans 7:7, and concludes that

At bottom, the best translation is one that is faithful to the meaning of the original text. That does not always, nor even usually, mean a literal translation.

Then Wallace turns to NIV 2011, and gives what appears to be a remarkably positive but brief review. He praises several text critical decisions and some changes of wording from NIV 1984. Then he draws the apparent conclusion that

All in all, this is a fine translation and is the culmination of the efforts of many decades, scholars, countries, denominations, and ideologies. Yet everyone associated with the NIV is unswervingly committed to the Bible as the word of God written. Their joyous wonder at the beauty and majesty of the scriptures comes through loud and clear in this superb version.

But is this really all he has to say? The only specific clue that there is more to come is in the post title, “Part 2 of 4″. But I suspect that Wallace will have some more negative things to say about NIV 2011 in part 3, before coming to his final conclusions in part 4.

Dan Wallace on NIV 2011 and the history of the English Bible

At Reclaiming the Mind Dan Wallace offers part 1 of a review of NIV 2011. This first part is in fact a review of the history of English Bible translations, mostly from 1885 to the present day. Although there are some small points which I could take issue with, in general this is the kind of excellent work one would expect from Wallace. I look forward to the other three parts of the review, which will presumably appear soon at the same place.

Aural/oral qualities of the KJV/AV

Tim Bulkeley is looking for some help in studying the aural/oral qualities of the KJV/AV:

“My thought is to address the well-known aural/oral qualities of the KJV/AV and relate that to the possibilities of various oralities/new oralities introduced by the move to electronically mediated communications.”

I’ve attempted to look at the problem based on the concept of “chunking.” When we grow familiar with a passage we tend to run ahead and not actually read every word. This allows us to read more quickly even in the case of a seemingly “less natural” translation.

You can look at my comparison of reading fluency rates for CEV, NIV and ESV here: Reading speed of Scripture

If you’ve got some pointers for Tim on how to approach his topic, please visit his post and leave a comment: Aural/oral qualities of the KJV/AV

 

Slander: a mistranslation?

In a post on my own blog, I argue that The devil isn’t a slanderer, because the Greek word diaballo often translated “slander” doesn’t mean that. Specifically, in English “slander” implies a false accusation, but the Greek word refers to an accusation “without any insinuation of falsehood”. More to the point for better Bible translations, this means that where diabolos is often translated not “devil” but “slanderer”, i.e. 1 Timothy 3:11, 2 Timothy 3:3 and Titus 2:3, a rendering like “malicious talker”, as in 1 Timothy 3:11 NIV, would be more appropriate.

My observations on standing up to bullying behaviour might also be of interest to BBB readers.

What is Your Translation Metaphor?

A classic article in communication studies is “The Conduit Metaphor: A Case of Frame Conflict in our Language about Language” by Michael J. Reddy (1979). In our way of thinking about language, we seem to have an image in mind of packaging our thoughts into words and then sending those words across to someone else who unpacks them to get the meaning. Reddy shows how pervasive this conduit metaphor is in our speaking and thinking about language. He is shocked (shocked!) that we so easily give ourselves over so completely to something so insubstantial and illogical as a metaphor to shape how we conceive of linguistic communication. If we really understood the nature of meaning and language better, we wouldn’t say things like “He can’t get across very well what he is thinking,” or “Let me give you an idea of what I have in mind,” or “I can’t find anything of significance in this essay,” or “Why don’t you put your thoughts down on paper?” George Lakoff adds an interesting commentary in his own article in the same volume (Metaphor and Thought, Second edition, edited by Andrew Ortony): “Reddy showed… that the locus of metaphor is thought, not language, that metaphor is a major and indispensable part of our ordinary, conventional way of conceptualizing the world, and that our everyday behavior reflects our metaphorical understanding of experience.” Shortly thereafter (1980) Lakoff, along with Mark Johnson, more completely described the significance of conceptual metaphors in Metaphors We Live By. [I’m probably using the conduit metaphor all over the place here without even realizing it.]

I think this is a fair way of putting this conceptual metaphor concept: In the way we think, the analogical is just as important as—if not more important than—the logical. Well, it’s probably WAY more important, actually. But for those of us who are more analytical, it is good to be aware of our metaphors. Which brings us to metaphors for translation. What is translation? Etymologically-speaking, it is “carrying across.” Isn’t that a metaphor? [Come to think of it, what is metaphor? At its etymological core, isn’t “metaphor” a metaphor as well? How can we escape this!?]

I like how the King James translation says, “Giving thanks unto the Father, which hath made us meet to be partakers of the inheritance of the saints in light: Who hath delivered us from the power of darkness, and hath translated us into the kingdom of his dear Son” (Col. 1:12-13), and, “By faith Enoch was translated that he should not see death; and was not found, because God had translated him: for before his translation he had this testimony, that he pleased God” (Hebrews 11:5). Which use of “translate/translation” is metaphor here, and which literal?

I was once privileged to hear the Translation Studies scholar Andrew Chesterman give a presentation on metaphors used to conceptualize translation, and to have a chance to discuss it with him afterwards. He invited his listeners to analyze and tell what metaphors they use in thinking about translation. As I recall, there was not any one answer that was supposed to be correct, nor did Chesterman sniff at the whole idea of conceptualizing metaphorically. He just wanted to get us to think—and I’m trying to get you to think. What about an image of translation as someone carrying something across to someone else, as the Latin suggests? What about translation as giving someone a gift? What about translation as bridge building? That’s cool. See this picture I took of a poster that says, Chi traduce costruisce ponti,” or, “Who translates builds bridges.”

A well known metaphor associated with translation is to think about the language you are translating into as the “target” language. I suppose if you translate well, that means you have hit the bullseye. If we talk about a “receptor audience,” I guess we’re using that conduit metaphor that Reddy wrote about. I have to confess that I use this kind of language all the time. J.K. Gayle outed me in his comment when I wrote in my last blog post about “pinpointing” a target audience. That probably was a poor choice of words. I think I was trying to avoid using a word as ordinary as “determining.” And thanks to Gayle at the same time for pointing out (not pinpointing) that from a Chinese perspective, translation involves “host” and “guest” languages. Another metaphor.

I see interpretation and the reading of a text as having an important connection with translation. In Truth and Method (1975) Hans-Georg Gadamer described the reading of a text in terms of a widening of horizons, and a fusion of horizons between author and reader: “Gadamer said that a text has its own horizon, or vantage point and all that can be seen from that vantage point, and a reader brings his own horizon to the text. Meaning is the result of the reader’s horizon being altered or widened by exposure to the horizon of the text.” This image of horizons coverging brings to my mind the horizon controls I have seen in small airplanes. Paul Ricoeur uses the image of musical compositions and their performance: “Another metaphor Ricoeur uses is that a text is like a musical score that only provides for the potential for music—or meaning—until it is performed—or read. You can either analyze a text (like analyzing a musical composition), or you can try to absorb what the text has to say (like performing a musical piece). A reading of a text is a performance of it, and not all performances will be the same.” (Note that both of these quotes are my own words and interpretation, from an unpublished paper presented at a conference in 2009.)

Back to Italian, we’re all familiar with the saying, based on a play on words in Italian, that “The translator is a traitor.” There seems to be a widespread sentiment among some people in relation to Bible translation to the effect that thinking about what the source text means and expressing those ideas in the garb of another language amounts to betraying the text, and the least offensive solution is to give a word for word literal translation and force the reader to try to see the text from the viewpoint of the speakers of the original language. Maybe the idea here is of someone from one culture, while in another country, dressing himself as a member of the host culture and illegitimately passing himself off as one of them, perhaps for subversive reasons. If you are in another country, maybe the only honest thing to do is to stand out as a foreigner. Or what about the metaphor that a language or a text “resists” translation? I get the picture of the French underground resisting the Nazi occupation. Or a body at rest resisting being put into motion. If resistance is variable, perhaps it can be measured, as in an electrical circuit.

As I understand it, developments in the European Union challenge the basic ideas of source language and target language in translation. In European Union legislature, there is not supposed to be any primary or privileged language, and so when a law appears, it is supposed to show up in all the different languages simultaneously, without there being any particular source language. I get the picture of scattered seeds all growing into plants simultaneously.

When it comes to Bible translation, my guiding metaphor is that of the incarnation: The Word became flesh. I see the Word becoming flesh and dwelling among us in a lot of different shades of flesh and a lot of different sounding languages, to speak to, and act on behalf of, a lot of different people.

Well, this essay is too long. I should have packaged my thoughts into fewer words.