What September 11 Might Have in Common with Translating the Trinity
I imagine a novel written in a remote location, far from western culture. It’s about the last ten days of summer and the nearing autumn. So they call the book the equivalent of “What Happened on September 11″ in their local language.
My question is this. Should the American version of the book be called, What Happened on September 11?
I don’t think so, because even though September 11 is ten days before the end of summer in English, too, the phrase “September 11″ has local overtones — the terrorist attacks, the wars that followed, etc. — that override the simple meaning of the phrase.
This is one way that a good translation of the words can be a bad translation of the text.
What this has to do with the Trinity is that the claim has surfaced that in Arabic, “father” and “son” wrongly imply sex, so they’re not good translations for what we know in English as the Father and the Son.
Facts to support this claim about Arabic (and other languages of the Middle East) have been frustratingly difficult to come by, but even the theoretical issue, it seems to me, has been misunderstood.
Some people have claimed that getting rid of “Son” in Arabic is pandering, or wrongly changing the Bible to placate an audience, or giving up on theology, etc. Maybe. But maybe not. Maybe “son” in Arabic is like “September 11″ in English. It has a plain meaning, but it also has overtones that destroy the original point of the text.
Other people have claimed simply that the job of the translator is to translate the words. In spite of the hugely intuitive appeal of such an approach, it doesn’t work very well, because sometimes the words convey the wrong thing.
So even before we get a good factual answer about Arabic, I think it’s important to understand the fundamental point that it’s certainly possible for the literal equivalent of “son” and “father” to be the wrong way to translate the Trinity.
What percentage of your Bible translation is accurate? (Trying again.)
My last attempt to see how people understand the accuracy of their Bible translations didn’t work. I got a lot of responses, but not one answer to the basic question.
So I’m trying again, with a poll:
Please feel free to comment after you’ve answered the poll.
What percentage of your Bible translation is accurate?
I’ve just returned from a three-day festival of learning in Kerhonkson, NY, where I spoke about, among other things, Bible translation.
Right at the end I was asked a great question, which I repeating here: What percentage of your Bible translation is accurate?
We all know that there is no Bible translation that’s 100% accurate. So:
1. Which Bible translation do you prefer?
2. How much of it do you think is accurate?
3. Why?
I’m looking forward to reading your responses.
How Words Work Together in the Bible
There is something intuitively appealing about a translation that takes the Hebrew and Greek words in the Bible and translates each one into English. But the premise behind such an approach is flawed, because words work together differently in different languages.
Here’s a simple example from Genesis 29:19: vayomer lavan tov titi ota lach mititi ota l’ish acher.
The Hebrew starts off vayomer lavan, which is quite clearly, “Laban said.” What did Laban say?
The next word in Hebrew is also easy: tov means “good.” What is good?
The next word is a bit more complicated, but still uncontroversial. The Hebrew titi is from the verb stem tet (“give”), and it means “my giving.” Then the Hebrew gets easy again: ota is “her” and lach is “to you.” So far we have, “my giving her to you is good” — a translation that is simple and straightforward, but wrong.
Even though that’s what the words mean, it’s not what the phrase means.
What’s going on is, also, uncontroversial. The next phrase in Hebrew is mititi ota l’ish acher, literally “from my giving her to another man.” The key factor here is knowing that Hebrew uses “from” to indicate comparison, or what is technically called “degree.” In English, we usually do this by changing the adjective, either with “more” and “most” or with the suffixes “-er” and “-est.”
For example, in the English “he is happier (than her)” the adjective “happier” expresses a comparison of happiness. Interestingly, it’s possible that “he is not happy,” but he’s still “happier than her.” That’s how degree works.
In Hebrew, the word would be just “happy” in both cases.
English indicates degree by changing the adjective. Hebrew uses “from” elsewhere in the sentence.
When we see mititi (“from my giving”) in the second part of the Hebrew sentence, that’s our clue that this sentence is a comparison. The way we indicate this comparison in English is with “better.” And, of course, that’s what every translation has: “it’s better that I give her to you than to some other man” (NIV).
The point is that Hebrew has one way of indicating degree and English has another. It’s a mistake to translate the words of Hebrew into English. Rather, the goal of the translator, in this case, is to translate the comparison. More generally, the goal of the translator is to figure out what the original words do, and then find a way of doing the same thing in English.
Some people think that the goal of “adding words in English” is just to make what would otherwise be nonsensical (“it is good, my giving her to you, from my giving her to another man”) into something that makes sense. But that’s not quite right. Rather, the goal is to make the English mean the same thing as the Hebrew.
Similarly, some people think that the “from” in the second part of the Hebrew sentence means that “we should translate tov as ‘better.’ ” But, again, that’s not quite right. We’re not translating tov. We’re translating the phrase.
We find another case of the same grammatical issue (degree) in Genesis 4:13: gadol avoni minso, literally, “big my crime from-bear,” with the obvious translation “my crime is too great to bear.” Again, we add the words “too” and “to” not just to make a coherent English sentence, but to make the right coherent English sentence, one that matches the Hebrew.
Changing the Son of God for Muslims
An article in World Magazine discusses Wycliffe‘s recent debate about how to translate “Son of God” and “God the Father” into Arabic for Muslim audiences, noting that “in Muslim contexts,” a literal translation “implies that God had sexual relations with Mary” — at least according to some translators.
Therefore, Wycliffe’s translations have at times resorted to alternative wordings, causing more than a little debate.
It seems to me that there are two factual questions here.
Read more »
Accuracy versus Personal Preference: a hidden choice in Bible translation
The latest round of reporting on the LifeWay Bible-preference poll addresses the theme of gender-neutral translations, with headlines like, “Study: Bible readers oppose gender-inclusive translations” (from the Associated Baptist Press).
What I find interesting here is that the poll specifically explained that some Greek and Hebrew terms refer to “people in general,” and the question was whether these inclusive terms should be translated as “man” or as “humankind” etc.:
“Bible translators have to make choices regarding gender issues. For example, the original Greek and Hebrew often uses masculine words such as those literally meaning ‘man’ to describe people in general. Some translators think these should be translated literally as ‘man’ while others think they should be translated into gender-inclusive terms such as ‘humankind,’ ‘human being,’ ‘person’ or ‘one.’ Which do you prefer?”
The question was, in my opinion, biased, but not terribly so. Describing the translation of “man” as “literal” but not describing the other terms with any potentially positive attribute seems unbalanced; also, the question suggests that the original can be translated “as `man,’” but “into gender-inclusive terms.” Even so, the question specifically told respondents that the point was to convey “people in general.” And only 12 percent wanted the more accurate choice.
Another way to phrase the poll question, it seems to me, would have been: “Some translators try to tell you what the text of the Bible means while others try to give you a text that you will like. Which do you prefer?” Of course, I have no way of knowing for sure what the results of asking such a question would be, but I find it hard to believe that the same 82 percent that opted for “man” would choose translations that are tailored to personal preference.
So why did so many people prefer the word “man” to express “people in general”?
As with the accuracy versus readability, I think these poll results have more to do with culture than with translation, linguistics, or Bible studies.
Accuracy versus Readability: another false choice in Bible translation
According to a recent report by Lifeway Research, described by David Roach in the Baptist Press, “most American Bible readers … value accuracy over readability,” which is why they “prefer word-for-word translations of the original Greek and Hebrew over thought-for-thought translations.”
There is overwhelming evidence and near universal agreement among linguists that word-for-word translations are less accurate than other approaches.* Equally, translators generally agree that, when the original is readable (as much of the Bible is), accuracy and readability go hand in hand. That is, valuing accuracy is often the same as valuing readability.So what’s going on?
One question might be, “why do so many Bible readers still make the basic mistake of choosing the wrong translation (word-for-word) to achieve their goal (accuracy)?”
Another question might be, “is there some merit to the word-for-word translations that linguistic approaches are missing?” (I try to answer that question here: “the value of a word for word translation.”)
A third question might be, “is there something about thought-for-thought translations that makes them unsuitable even though they ought to be more accurate?” (I think the answer is yes.)
But I’m starting to wonder about the ongoing Bible-translation debate that pits accuracy against readability, and words against thoughts. Maybe it’s not primarily about language and translation at all. Maybe the issue is part of the broader disagreement about the roles of religion of science and how to balance the two. In other words, sticking to a word-for-word translation may be like opting for a literal biblical account of history and rejecting evolution, at least for some people.
What do you think?
[Updates: Mike Sangrey has a follow-up on BBB with the delightful title, "Headline news: Accuracy Battles Readability --- Surreality Wins." And in a post on the same topic at BLT, J. K. Gayle creates what I think is the right frame of mind with, "Imagine having to chose between accuracy and readability in a translation of Orhan Pamuk or Homer or Virgil."]
(*) Just for example, my post on “what goes wrong when we translate the words” gives a sense of one problem; my post on “what goes wrong when we translate the grammar” gives another. My recent TEDx video explores the issue in more detail, and my And God Said goes into much more detail.)
Why Most Bible Translations are So Bad (And Why the Next Generation Should Care)
This past July I had the pleasure of presenting at a TEDx conference in East Hampton, the broad theme of which was “The Next Generation.”
So I offered an 18-minute segment on Bible translation, on what so often goes wrong with translations, and on how to avoid the common mistakes. I couched these topics in the broader theme of why the Bible is important for the next generation.
The edited version of my presentation is available here and on YouTube:
After watching it, you’ll be able to answer these questions:
- Why is the King James Version (“KJV”) so important for understanding Bible translation today?
- What are the three most common ways of understanding ancient languages?
- Why don’t those ways work? How do we know? And what are some consequences?
- What is a better approach? Again, how do we know?
- Why are the Ten Commandments still uniquely relevant?
- What does all of this have to do with supermarkets?
I’ve touched on many of these themes in individual blog posts here, and I go through all of them (except for the supermarkets) in And God Said: How Translations Conceal the Bible’s Original Meaning, but here’s a compact and relatively complete introduction. Enjoy!
And then take a look at the other presentations.
I also want to express my thanks to Left of Frame Pictures for producing the videos.
Making Jesus the “Human One”
Though the text of the new Common English Bible (“CEB”) has been circulating for some time, its recent release made headlines (Bob Smietana in The Tennessean, picked up by Cathy Lynn Grossman on her USA Today blog), in part because of the translators’ decision to change the traditional “son of man” into “human one.”
Why did they make the change, and is it a good one?
Son of Man
The traditional “son of man” is a literal translation of the Hebrew ben adam, which is how God frequently calls Ezekiel. We also find it elsewhere in the OT. In these cases, the Greek Septuagint translates the Hebrew literally as uios anthropou.
The English phrase also occurs in the NT, where it is the nearly literal translation of the Greek uios tou anthropou (“son of the man”), common in all four Gospels, and appearing elsewhere.
While the Hebrew phrase seems to refer to any human (even though it’s only actually used of a few humans), the Greek phrase seems to refer specifically to Jesus. For this reason, many translations capitalize it, either “Son of man” or “Son of Man.”
Against “Son of Man”
Perhaps the biggest drawback of these literal translations is that the Hebrew ben and Greek uois indicate “member of” in addition to “son” or “child.” One famous phrase where we see this is b’nai yisrael (b’nai is the plural of ben), commonly “children of Israel” or “sons of Israel,” but really just “Israelites.” Similarly (just for instance), in Matthew 9:15, the phrase commonly translated as “wedding guests” is literally sons of the weddinghall.
Accordingly, ben adam could simply be someone who is an adam, just as uios tou anthropou could be someone who is an anthropos. That is, both phrases might just refer to a person. This is where the CEB gets “human one.” They are right that “son of man” is overly literal and misses part of the point of the original.
Another problem with “son of man” is that it is doubly gendered in a way that the Greek is not. In Greek, both uios and anthropos can refer to women as well as men. So the traditional translation introduces gender while the CEB’s translation does not.
In Favor of “Son of Man”
On the other hand, the term “son” in the NT is hardly a neutral one. It is part of the trinity. And it makes possible the progression from “son of man” to “son of God.”
In terms of the latter, for example, we find Luke 22:69-70:
“…but from now on the Son of Man will be seated at the right hand of the power of God.” All of them asked, “Are you, then, the Son of God?” (NRSV, my emphasis)
In the CEB, this becomes:
“…but from now on, the Human One will be seated on the right side of the power of God.” They all said, “Are you God’s Son, then?” (CEB)
The progression is destroyed.
And in terms of the trinity, we might consider Matthew 12:32: “Whoever speaks a word against the Son of Man will be forgiven, but whoever speaks against the Holy Spirit will not be forgiven…” (NRSV), which resonates with Matthew 28:19: “baptiz[e] them in the name of the Father and of the Son and of the Holy Spirit.”
In the CEB, we find instead: “And whoever speaks a word against the Human One,” which doesn’t match “baptiz[e] them in the name of the Father and of the Son and of the Holy Spirit” in the same way.
The Tradeoff
I understand the motivation behind “human one” in the CEB. And I think that in isolation it’s a better translation than the traditional “son of man.” But in the broader context of the full NT, I think the association with “son” is too central to give up, and so the CEB misses more than it captures.
What do you think? Which part of uios tou anthropou (“son of man” / “human one”) is more important, the meaning of the phrase or the associations of “son”?
