God Didn't Say That

Bible Translations and Mistranslations

How to Love the Lord Your God – Part 1, “Heart”

“Love the Lord your God with all your heart [and] all your soul…” According to Jesus in Matthew 22:37, Mark 12:30, and Luke 10:27, this is the most important commandment.

Jesus’ Greek is a quotation of Deuteronomy 6:5, and that Hebrew passage is so central to Jews that it’s part of what is inscribed on the parchment inside the mezuzah traditionally affixed to doorways.

But I don’t think “heart” (or “soul”) is what the original meant in either the Old Testament or the New Testament.

As a matter of anatomy, the Hebrew levav (“heart” in Deuteronomy) and the Greek kardia (“heart” in Mattherw, Mark and Luke) is what we would now call the heart in English. But as a matter of metaphor it is something very different.

“Heart” in English

In English, the word “heart” generally indicates emotion. And it’s the opposite of “brain” or “mind,” which represent rationality. For example, someone who is “thinking with his heart” is being emotional and not rational. “To follow your heart” is to do what you love, even if you don’t think it’s a good idea. “A sound mind in a sound body” refers to someone who can think clearly, not necessarily someone whose emotions are well organized. “Let the mind rule the heart” means to let rationality prevail over emotion. The expression “heart-broken” refers to emotions, while “his mind is gone” refers to rational thought.

It’s not that we think that emotion is literally in the heart or that thoughts are literally in the mind (though, in fact, as a matter of science, both are probably mostly in the brain). Rather, we use “heart” metaphorically to represent emotion and “mind” (or “brain”) metaphorically to represent thought.

In fact, this way of using “heart” and “mind” is part of a broader, more fundamental view of people: they have emotions (hope, fear, love, expectation, sorrow, etc.) and they have thoughts. And the two are distinct.

But this ontology is not the only way of divvying up what it means to be human.

“Heart” in the Bible

Hebrew

In the Bible, emotions and thoughts were considered to be closer in nature than they are now. For instance, in modern English “I love him” and “I fear him” are both statements about emotions, even though the emotions differ. Similarly, in the Bible, “I love him” and “I think he’s a capable ruler” were both the same kind of thing.

And the levav (Hebrew for “heart”) and kardia (Greek for “heart”) were used to represent both — that is, what we would now call emotions and also what we would now call thoughts.

We see levav used to represent cognition, for example, in Isaiah 6:10, which contains three pairs. “To see” goes with “eyes.” “To hear” goes with “ears.” And “to understand” goes with levav. (Matthew 13:15, quoting Isaiah, similarly pairs “understand” with kardia.) Deuteronomy 29:4 contains the same three pairs, though it has the alternative form lev instead of levav. In the same way, Isaiah 10:7 pairs “thinking” with levav. And in Ezekiel 38:10, when something enters your levav you think a certain way.

The levav, then, is the seat of thoughts and cognition. In this sense, levav is the opposite of the English “heart.” (Using the opposite of the word you want to translate is usually a bad idea.)

The Hebrew levav is also used for emotion, though. In Leviticus 19:17, the levav is where you should not “hate.” In Psalm 27:3, the levav is connected to “fear.” And so forth.

We see a particularly clear picture: while the English “heart” is used for “emotions and not thoughts,” the Hebrew levav is used for “emotions and thoughts.”

Greek

Greek works like Hebrew in this regard. We’ve already seen Matthew 13:15, but that’s a quote of Isaiah, so it’s not necessarily reliable. But there are plenty of other examples. In Matthew 9:4, when Jesus knows the scribes’ “thoughts,” he knows what is in their kardia. In Matthew 15:19, thoughts come from the kardia. Mark 8:17 connects a “hard kardia” with inability to understand.

And the kardia is also where people are happy (as in Acts 2:26), afraid (John 14:27), and so on.

So, as with Hebrew, Greek combines thoughts and emotions in the kardia. And again this is unlike English, which separates them, using “heart” not just to include emotions but, importantly, specifically to exclude thoughts.

“Love with All Your Heart”

So while it’s tempting to translate levav and kardia as “heart” — particularly because “love” and “heart” go together in a way that “love” and “mind” do not — it’s also a severe mistake, because “heart” excludes thoughts, and what we need is a word that specifically includes them, along with emotions.

In isolation, finding such a word in English is no easy task, as the issue is not just linguistic, but also ontological. Modern English speakers think there are (at least) two kinds of internal human events: thoughts and emotions. Ancient Greek and Hebrew speakers thought there was one. And the point of levav and kardia is to include them both.

Fortunately, the translation task gets easier when we take into account “soul” (which is also a major mistranslation), as I hope to address soon. [Update: the explanation of "soul" is here: "How to Love the Lord Your God --- Part 2, Soul."]

November 28, 2011 Posted by | translation practice | , , , , , , , , , , , , , , | 43 Comments

Translation Challenge: “With” and “For” in Isaiah 54:7

Isaiah 54:7 — part of the incredibly uplifting poetry of Isaiah 54 — has two parallel phrases, both starting with the Hebrew b-. First we find b- attached to rega (“moment”), and then next attached to rachamim (“mercy” or “love” or “compassion”). The effect is to underscore the contrast between God abandoning for a moment and taking back in mercy.

Yet every translation I know destroys the parallel structure, as, for example, the NRSV: “For a brief moment I abandoned you, but with great compassion I will gather you” (my emphasis). In other words, for b’rega the translations have “for [a moment],” but “with [compassion]” for “b’rachamim.”

It’s true that the Hebrew prefix b- can mean both “for” and “with,” among many other possibilities. (It’s a bit like the ablative case — an observation which is likely to help only the people who already knew that.) But here, the whole point is to contrast two phrases that start the same way. So while the translations get the general point of the line, they butcher the poetic effect.

The contrast is further underscored through the Hebrew modifiers katon (“small”) after rega and gadol (“big”) after rachamim. (This is the “brief” and “great” in the NRSV translation.)

So here’s the challenge: Can you think of a way to express Isaiah’s thoughts here while also keeping the important poetic structure? (My best shot is in the comments.)

November 7, 2011 Posted by | translation challenge, translation practice | , , , , | 13 Comments

The Lord isn’t the Shepherd You Think (or: Don’t Mess with the Shepherds)

“The Lord is my shepherd.” This line from Psalm 23 is among the most famous images from the Bible. But as I describe in And God Said, for most people the English words hide the ancient imagery.

Shepherds

To get started, here’s a question: which actor would you cast as a typical shepherd?

When I think of a shepherd, I think of a scrawny man dressed in rags who spends more time with sheep than with people. In term of imagery, I might say, “as lonely as a shepherd,” or “as meager as a shepherd,” or “as ill-dressed as a shepherd.” (If you’re reading this and you are a shepherd, please forgive me!) So in terms of an actor, I think I’d pick Woody Allen. (And Mr. Allen, if you’re reading this, please forgive me; I still love your movies.)

But we see a completely different set of images in the Bible. Shepherds were fierce, regal, and romantic. Back then, one might have said, “as brave as a shepherd,” “as strong as a shepherd,” or “or sexy as a shepherd.”

So even though the Hebrew in Psalm 23 is ro’eh, and even though ro’eh literally means “shepherd,” I don’t think “The Lord is my shepherd” is a very good translation.

Ferocity

For example, Exodus 2:16-20 describes the Midian priest’s seven daughters who are drawing water for their father’s flock when a group of shepherds comes to menace them. Moses proves his amazing capabilities by defending the women against the shepherds. The daughters even say, “[Moses] saved us from the shepherds.” Nowadays, that’s a laughable image. But in the Bible, shepherds were fierce, and Moses demonstrated great worthiness by standing up to them. (In another clash with modern sensibilities, the high priest thanks Moses by giving him a daughter to marry.)

Read more »

October 21, 2011 Posted by | translation challenge, translation practice | , , , , , , , | 26 Comments

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 »

October 12, 2011 Posted by | translation practice, translation theory | , , , , , | 15 Comments

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”?

July 19, 2011 Posted by | translation practice, translation theory | , , , , , , , | 33 Comments

Translating Mistakes in the Text

From time to time, we have what seem to be mistakes in the traditional text of the Bible, frequently the results of apparent errors on the part of a scribe. How should these be translated?

Here are three examples.

Leviticus 20:10 (dittography)

In Leviticus 20:10, we find the phrase “a man who commits adultery with the wife of” repeated, almost certainly inadvertently. So the Hebrew text reads, literally:

and
a man who commits adultery with the wife of
a man who commits adultery with the wife of
his neighbor:
[in that case the adulterer and adulteress shall be put to death.]

Three translation options seem to present themselves:

1. Translate the text as it is, repetition and all.

2. “Fix” the text by ignoring the repetition.

3. “Fix” the text by making sense of the repetition.

Most translations take the second route. The ESV, NRSV, and The Message, for example, translate the repeated phrase only once. (The ESV and NRSV note the Hebrew duplication in a footnote.)

I don’t know of any version that follows the first strategy exactly, but the KJV comes pretty close: “And the man that committeth adultery with another man’s wife, even he that committeth adultery with his neighbour’s wife, the adulterer and the adulteress shall surely be put to death.” If we disregard the italics, the duplicated phrases are almost identical. But even so, the KJV doesn’t reproduce the effect of having the same phrase twice.

The remaining translations try to make sense of the duplication, much as the KJV did. For instance, the NIV gives us, “If a man commits adultery with another man’s wife — with the wife of his neighbor — …,” as if the second phrase is an explanation of the first.

The merits of Option 2 are pretty clear: Just because a scribe made a mistake doesn’t mean we should introduce a mistake into English.

I can understand Option 1 as well: We should translate the text, not emend it.

But it’s hard for me to understand why Option 3 is a good idea. Rather, it seems like a mistake born of misunderstanding the nature of the original text.

Deuteronomy 31:1 (parablepsis)

We find a different challenge in Deuteronomy 31:1. That verse starts in Hebrew, “Moses went [vayelech] and spoke…” The problem is that Moses didn’t go anywhere. In fact, it’s pretty clear that he’s exactly where he was in the previous verse.

It seems that the original text was not “Moses went” but rather “Moses finished.” While those two verbs seem unrelated in English, in Hebrew the first (without vowels) is V-Y-L-K, while the second is V-Y-K-L. Except for the order of the final two letters, they’re the same. Furthermore, we find V-Y-K-L (“finished”) in the Dead Sea Scrolls (“DSS”), and the Septuagint translates sunteleo, “finished.”

Again, we have three basic options: translate the text as is, ignore the mistake, or make sense of the mistake.

The KJV, among others, takes the first approach. (This is hardly surprising. Until the discovery of the DSS, it wasn’t clear that this was a mistake. Many people thought the Septuagint had it wrong. And, in fact, I suppose it’s possible that the Septuagint and DSS are both wrong.)

Other translations, such as the NAB and NRSV, simply translate “finished” here, as though the Hebrew read V-Y-K-L.

And other translations yet try to reconcile the text, with such options as, “So Moses continued to speak” (ESV).

Again, I understand the first two approaches better than the third.

Psalm 93:4 (haplography)

A third example comes from the poetry in Psalm 93:4. The Hebrew is, literally, “more than the sounds of much water mighty sea-breakers mighty on high is Adonai” — which doesn’t make much sense.

The Hebrew grammar here is complicated, but three basic points will help: The Hebrew letter mem (“M”) is used at the end of a word to indicate plurals. It is used at the beginning of a word to indicate nouns. And, also at the beginning of a word, it means “more than.”

So the plural of “mighty” (adir) is adirim. The word “breaker” starts with a mem: mishbar. And the first word of Psalm 93:4, mikolot comes from mi- (“more than”) plus kolot (“sounds”).

Accordingly, the way to say “mightier than sea-breakers,” if “mightier” is plural, is adirim mi-mish’b'rei yam, or, without vowels or spaces, A-D-Y-R-Y-M-M-M-Sh-B-R-Y-Y-M. However, the traditional text gives us A-D-Y-R-Y-M-M-Sh-B-R-Y-Y-M.

In short, if we add a third mem (back?) into the text, we get the much more sensible, “God is mightier than the sound of the water, mightier than the sea breakers.”

Here, every translation I know adopts what we’ve been calling the second strategy, fixing the text by ignoring the mistake.

Summary and Questions

Even though these three — and other — scribal errors are in principal the same, we find that translations deal with them differently.

1. Do you think a translation should fix erroneous text? If so, when?

2. When a translation does fix the text, should it also indicate what the uncorrected text means?

3. What value might there be to printing the uncorrected Hebrew (or Greek) next to the corrected English?

June 22, 2011 Posted by | Bible versions, translation practice, translation theory | , , , , , , , , , , , , , , , | 13 Comments

What is the Dust of the Ground from which Man is Formed?

Genesis 2:7, according to the KJV, has the creation of man “from the dust of the ground.” But why “dust”?

The Hebrew here is afar, and it doesn’t seem to mean “dust.”

From Genesis 2:7, we know that it’s something on the ground, but we don’t know what. “Dust” is a possibility, just from this verse, but — again, just from this verse — so is “grass,” “rocks,” “lichen,” “mud,” etc. So we look further.

Genesis 13:16 helps us a little. There we read that Abram’s descendants will be like the afar on the earth, so that if the afar can be counted, so can Abram’s descendants. So afar can’t mean “mud” or “clay.” It seems to refer to particles of some sort.

Genesis 18:27 is helpful in a different way. There we see afar used as a metaphor of humility. (The full phrase is “afar and efer.” I’ve explained elsewhere that the English “dust and ashes” doesn’t do justice to the repetition of sounds in afar and efer:Doublets Are Part And Parcel of Bible Translation.”) I Samuel 2:8 emphasizes the connotation of lowliness: God “raises the poor from afar, lifts up the needy from the trash.” And the vivid imagery of Isaiah repeatedly uses afar to represent humility.

But next we look at Genesis 26:15, which explains that the Philistines had filled Abram’s wells with afar. And here we see the problem with “dust” for afar, because one would use “dirt,” not “dust,” to plug up a well. (And, indeed, the KJV goes with “earth” here for afar.)

The basic problem is this: “Dust” in English refers specifically to particularly fine-grained particles, of earth or otherwise. “Dirt,” by contrast, is just what’s on the ground, and we seem to be talking about dirt here.

In Numbers 5:17, the priest is instructed to take afar form the floor of the Tabernacle, so again afar seems to be “dirt,” not “dust” Dust would have been swept away as part of regular cleaning (I presume).

In Greek for afar we usually find gi, a word that pretty clearly means “land,” both in the sense of “dirt” and of “country.” So in addition to its use as the substance that filled the wells, we read that Jacob lived in the gi of his ancestors, the gi of Canaan (Genesis 37:1). The Greek gi also means “(the entire) Earth,” a usage we find, for instance, in Genesis 6:11.

So far we have yet to see any indication that afar is particularly fine-grained, so we see no support for “dust.” We do see “fine as afar” in Deuteronomy 9:21, but there the fineness is in reference to the golden calf. “As fine as dirt” works as well as “as fine as dust.” (Though if the calf was made of gold, I’m not clear how it was burned into dust or ash or whatnot. Why didn’t it melt? But I guess that’s for another time.)

And in II Samuel 16:13, we see that afar can be flung along with rocks, again arguing for “dirt” and not “dust.”

Similarly, afar is a common image in Job, and there the word is frequently translated “earth.”

But “dirt” or “earth” isn’t quite right, either, because afar isn’t limited to what’s on the ground. In Leviticus 14:41, concerning a contaminated house, scraping a house produces afar — perhaps “debris,” in English. It’s probably not “dust” because the afar can be collected and poured out outside the city. (You won’t find “dust” in most English translations here, so if you’re not reading the Hebrew, it’s hard to know that it’s the same word.)

But then in the very next verse, “other stones” and “other afar” are supposed to be used to rebuild the house. (I don’t know of any English translation that uses “dust” here.) Is this just poetic symmetry? (Leviticus 14:40 refers to stones, so both “stones” and afar in 14:42 might refer to that which was discarded.) Or does afar also metonymically refer to “plaster,” made from earth and water? This latter possibility is consistent with Leviticus 14:45, where houses seem to be made of “wood, stones, and afar.” Or, perhaps, is the idea here that new stones, wood, and dirt are supposed to gathered, and then worked in the way that stones, wood and dirt usually are?

Also moving away from “dirt” for afar is Numbers 19:17, where we see that afar is the result of burning a sacrificial animal. Most translations have “ashes” here, not “dust.”

So afar seems to refer generally to any granular material, and in particular to the granular material on the surface of the earth. Additionally, it symbolizes humility. In English, we usually call that “dirt.”

So I think Genesis 2:7 should read, “The Lord God formed man from the dirt of the ground.”

May 6, 2011 Posted by | translation practice | , , , , , , , | 9 Comments

Why the Debate between Formal Equivalence and Functional Equivalence is Deceptive

The debate between “formal equivalence” and “functional equivalence” has come up again at BBB, this time in the comment thread to a post about David Ker’s The Bible Wasn’t Written To You. (It’s a free e-book. Take a look.)

Dannii started the debate with a reference to his post “In which I ask if there’s any value to conveying morphosyntax.”

John Hobbins countered that “mimicking syntactical patterns of the source text in translation is [...] a reasonable default strategy.”

That is, essentially, the crux of the debate: whether or not the grammatical details of the original should be mimicked in translation or not. The formal equivalence camp thinks yes. Functional-equivalence translators disagree.

My take is that mimicking the grammar is as foolish as mimicking the sounds. We don’t translate the Greek ho (which means “the”) as “hoe” just to mimick the sounds. And we shouldn’t translate, say, a passive verb in Greek or Hebrew as a passive one in English just to mimic the grammar. Failure to realize this basic point, it seems to me, is to misunderstand what translation is.

So why is this basic theoretical point nonetheless so hard to grasp?

I think part of the answer lies in the practice of Bible translation. By and large, published English versions of the Bible are either formally equivalent or flawed in other ways, so the debate ends up, in practice, pitting formal equivalence not against functional equivalence but instead against other kinds of mistranslations.

The non-formally equivalent CEB can help us understand how this plays out.

Among that translation’s aims is that it should be written at a 7th-grade reading level. But I think that that goal is a mistake, because the Bible is not written at a 7th-grade reading level, so from the outset, the CEB has made a decision to abandon accuracy in some regards. And as part of pursuing that goal, the CEB’s editors make other mistakes. For instance, the CEB recasts Hebrews 12:1, turning it into a statement about going in a different direction in life, while the original is about going unburdened in the same direction.

Similarly, from the CEB translation comparison, we see that Genesis 2:7 now reads, “the Lord God formed the human from the topsoil of the fertile land” instead of the NRSV, “then the Lord God formed man from the dust of the ground” (their italics, to highlight the comparison). But the original doesn’t have any notion of “fertile,” and “topsoil” is almost certainly wrong for what should be “dust.”

My point is not to pick on the CEB, but rather to use it to highlight what I think goes wrong in the formal equivalence versus functional equivalence debate.

The formal equivalence crowd looks at the kinds of mistakes we just saw in the CEB, and, rightly in my opinion, notes that these versions miss essential aspects of the original. Then they compare, say, the NRSV renditions of these verses. The NRSV correctly has “lay aside every weight” in Hebrews 12:1. It correctly has “dust” in Genesis 2:7. And it doesn’t introduce the notion of “fertile” there.

In these cases, the NRSV is more accurate that the CEB. But I don’t think that the NRSV’s accuracy here comes from its philosophy. Rather, I think it comes, in this case, in spite of its philosophy.

After all, it’s this same philosophy that leads the NRSV to translate Mark 12:18 as, “The Sadducees … asked him a question, saying:” even though we don’t “say” questions in English; we ask them. The NRSV makes the same mistake in Genesis 44:19.

The supporters of functional equivalence use mistakes like these in the NRSV to attack formal equivalence.

And what follows is a debate where both sides are right — because both the CEB and the NRSV have mistakes — but where neither side is really talking about translation theory. They are talking about practice.

So instead of asking which version is better, I think the right questions are:

1. Can functional-equivalence translations be fixed without abandoning their translation philosophy?

2. Can formal-equivalence translations be fixed without abandoning their translation philosophy?

April 21, 2011 Posted by | translation practice, translation theory, using Bible translations | , , , , , , , | 13 Comments

“Judge Not” And Preserving Poetry

Judge Not

“Judge not…” Most people are familiar with this famous verse from Matthew 7:1 (and the similar Luke 6:37), and know that the full line runs along the lines of “Judge not, that you be not judged” (ESV).

The content of the line is pretty easy to understand, but the poetry is very hard to convey in English, as evidenced by the wide variety of translations: “Stop judging, that you may not be judged” (NAB), “Do not judge, or you too will be judged” (NIV), “Do not judge, so that you may not be judged” (NRSV), etc.

The Greek of Matthew 7:1

The Greek is a pithy five-word admonition: mi krinete ina mi krithite. The word mi means “not,” krinete means “judge,” ina means “so that,” and krithite means “be judged.” In addition to its brevity, the Greek offers a certain symmetry. The word ina sits nicely in the middle, with the two similar-sounding phrases mi krinete and mi krithite on either side. Except for the -ne- in the first part and the -thi- in the second, both sides are identical.

On Poetry and Symmetry

Similar in English is “you are what you eat,” where “what” fits nicely between the similar “you are” and “you eat.” (The original comes from German, where “are” and “eat” are both pronounced ist, so the similarity is even more pronounced: man ist vas man isst.)

Also similar in nature, if not in detail, is the English “no pain, no gain.” The phrase is successful because of the symmetry, and because “pain” and “gain” rhyme. This is why the phrase “without pain one is unlikely to achieve much” is unlikely to catch on as a training motto among athletes, even though it means the same thing as “no pain, no gain.”

Yet most translations of Matthew 7:1 are like “without pain one is unlikely to achieve much.” The translations miss the poetry.

Some people may dismiss the value of the poetry, but I disagree. I think that poetic phrasing is important. This is why so many of our proverbs either rhyme or otherwise “sound well” (as Mark Twain would say): “A stitch in time saves nine,” “no rhyme or reason,” “don’t do the crime if you can’t do the time,” and many, many more. And even if the poetry isn’t as important as I think, it’s still part of the original. It seems to me that a good translation should convey it.

On Grammaticality

Furthermore, also like my poor paraphrase of “no pain, no gain,” translations of Matthew 7:1 tend to sound stilted and awkward. “Judge not,” for example, is no longer standard English. (Compare, “comment not that you be not flamed.”)

And I don’t think that “judge” without an object is particularly successful in English. At least in my dialect, “I saw the modern art paintings, and I couldn’t help but judge” doesn’t work as well as “…couldn’t help but judge them.” I understand why translators want to force the English construction “do not judge.” They want to make the first part sound like the second part, “do not be judged.” But their decision comes at the expense of English grammar. In English (unlike in Greek), the most common phrasing is “do not judge something,” as in “do not judge others” or “do not judge people.”

Again, not everyone thinks that a translation into Modern English has to be in Modern English (at the risk of prejudicing the issue), but I do.

Translating Matthew 7:1

So where does that leave us?

We need a translation that means “do not judge (other) people, so that you will not be judged.” It should be symmetrical, with the first and second parts sounding similar. It should be pithy. And it should be grammatical in English.

In general, I’m unwilling to compromise on grammaticality in English, at least when the original is grammatical (in the original language), and I’m unwilling to compromise on meaning. When it comes to poetry, I think poetic texts should be translated poetically, but the details of the poetry can differ. So in this case, I think the symmetry is important, but I think — if something has to go — we can do without the pithiness.

So the best I can come up with is this: “Do not judge others, so that others do not judge you.”

What do you think? And can you come up with something even closer to the original?

April 15, 2011 Posted by | translation challenge, translation practice, translation theory | , , , , | 22 Comments

If not by bread alone then by what?

Matthew 4:4 (also Luke 4:4) is among the most famous Bible quotations: “Man shall not live on bread alone” (NIV2011) or, better, “one does not live on bread alone.” But if not on bread, then what?

What’s interesting is that there are two completely different answers.
Read more »

March 29, 2011 Posted by | translation practice | , , , , , | 7 Comments

Follow

Get every new post delivered to your Inbox.

Join 114 other followers