God Didn't Say That

Bible Translations and Mistranslations

Translation Challenge on Men, Women, and People: Who is an anthropos?

In light of my last post, I thought it might be helpful to move beyond theory to actual translation. How would you translate the Hebrew ish and the Greek anthropos in the following passages?

  1. Genesis 2:24 [Hebrew]: “Therefore an ish leaves his father and his mother and clings to his wife.”
  2. Genesis 2;24 [LXX]: “Therefore an anthropos will leave his father and his mother and be joined to his wife.”
  3. Deuteronomy 17:5 [Hebrew]: “You shall bring out the ish or the woman who has committed this crime…”
  4. Deuteronomy 17:5 [LXX]: “You shall bring out the anthropos or the woman who has committed this crime…”
  5. Genesis 4:1 [Hebrew]: “…I have acquired an ish…”
  6. Genesis 4:1 [LXX]: “…I have acquired an anthropos…”
  7. Numbers 5:31 [Hebrew]: “The ish will be cleansed of sin but that woman will bear her sin.”
  8. Numbers 5:31 [LXX]: “The anthropos will be clear of sin but that woman will bear her sin.”
  9. Matthew 4:4 [Greek]: “The anthropos does not live by bread alone.”
  10. Matthew 12:12 [Greek]: “How much more valuable is an antrhopos than a sheep.”
  11. John 16:21 [Greek]: “When a woman is a labor she is in pain … but when her child is born, she no longer remembers the pain because of the joy of having brought an anthropos into the world.”
  12. Romans 3:4 [Greek]: “Every anthropos is a liar.”
  13. 1 Corinthians 7:1 [Greek]: “It is good for an anthropos not to touch a woman.”

My answers are as follows:

  1. Genesis 2:24 [Hebrew]: man
  2. Genesis 2;24 [LXX]: man
  3. Deuteronomy 17:5 [Hebrew]: man
  4. Deuteronomy 17:5 [LXX]: man
  5. Genesis 4:1 [Hebrew]: person*
  6. Genesis 4:1 [LXX]: person
  7. Numbers 5:31 [Hebrew]: man
  8. Numbers 5:31 [LXX]: man
  9. Matthew 4:4 [Greek]: people**
  10. Matthew 12:12 [Greek]: person
  11. John 16:21 [Greek]: person
  12. Romans 3:4 [Greek]: person
  13. 1 Corinthians 7:1 [Greek]: man

Do you agree? Disagree? Why?



(*) Rabbinic tradition actually understands the word ish here to mean “fully grown man,” as though Cain skipped over childhood and was born a malicious adult. In the context of that tradition, I might prefer “man” as a translation.

(**) A quirk of English grammar — at least in my dialect — doesn’t allow the general definite singular with the word “person.” Even though “the wolf is a mighty animal,” e.g., refers to all wolves, “the person” cannot refer to all people. So we’re forced into “people” here.

September 24, 2013 Posted by | general linguistics, grammar, translation challenge, translation practice, translation theory | , , , , , , , , , , , | 23 Comments

More on Biblical Manhood and Womanhood

Suzanne McCarthy brings up the issue, again, of whether the Greek word anthropos is exclusively masculine (“man”) or gender neutral (“person”).

The short answer is that it is both.

We’ve been through this before, but the Greek framework of gender really is difficult for speakers of languages like English to grasp in the abstract, so here are some English examples that will help make things clearer.

The first example is the English word “day,” which has two clear, mutually incompatible meanings. The first is “24-hour period.” There are seven days in a week, 365 days in a year, stores are open for 24 hours a day, etc. The second is “part of a day.” Some pharmacies are open day and night, night follows day, days get shorter in winter, etc.

The second example is “luck,” which again was two clear, mutually incompatible meanings. The first is “good fortune.” The phrase “with any luck” means “with good fortune.” The second meaning is more general, “fortune of any sort.” That’s why people can have good luck or bad luck, and why “I can’t believe his luck” applies equally to lucky people and unlucky people.

The third example is “child,” which yet again has two meanings: “young human” and “any human with a parent.” So we have the phrase, “men, women, and children,” but also “adult children of aging parents.”

This final case is particularly interesting, because every person has a parent (even if the parents are dead: “children continue to mourn their parents’ death for years”). Just looking at the two definitions, it would seem that “child” in the sense of “someone’s offspring of any age” is a pretty silly word to have. How would it be different than “person”?

The answer is that “child” in this broader sense is only used in connection with parents. “Here comes a child” almost always refers only to a juvenile. But “parents and children” is ambiguous.

The case of “day” shows us a pattern that is similar in some ways, different in others. It’s different in that “day” is completely ambiguous. In my dialect, at least, if a store is “open all day,” I don’t know if it’s open at night or not. But it’s similar in that the phrase “day and night” is entirely clear.

One important lesson we learn from all of this is that words often have one meaning when they are used alone, and a separate meaning when they are used in distinction to something else. And, perhaps counter-intuitively, the various meanings can seem confusing, inconsistent, or even contradictory. Nonetheless, native speakers usually find the words entirely clear.

Not surprisingly, the Greek anthropos works just like these words.

By itself, it usually means “person.” John 16:21 is a pretty clear example: “a woman in labor suffers pain, but when her child is born she doesn’t remember her pain on account of her joy at having brought a person [anthropos] into the world.” To the best of my knowledge, no one thinks that this only refers to male children.

On the other hand, anthropos also contrasts with female-gender words like thugater (“daughter”), e.g. in Matthew 10:35; gune (“woman”), e.g., in Matthew 19:3; etc. Looking at the second instance, it’s clear that “an anthropos leaves his father and mother and joins his wife” refers only to men taking wives, not women. I don’t think anyone believes otherwise.

These examples point in a very clear linguistic direction. The Greek word anthropos — like many gendered words in gendered languages and like many other words in other languages — has more than one meaning.

In this context — and I think this was Suzanne’s point in her posting — it’s common to observe (as the Council on Biblical Manhood and Womanhood does here) that “in the New Testament, when this term [anthropos] is used for specific individuals, it always refers to males” (their emphasis).

Maybe. But it does not follow from this (potential) fact that anthropos cannot refer to a specific woman. And they even provide the evidence, in their next paragraph: “The list of specific men of which anthropos is used is quite long […] as distinct from the three times Christ refers to a woman (gune) in a parable.”

The lopsided nature of the text here — that is, the very fact that our data set includes a long list of men and only three women — warns us not to draw general conclusions about the word. If we enlarge the data set, to include, for instance, Suzanne’s example from Herodotus’ Histories (1.60), we do find anthropos used in regard to a specific woman.

Two additional points seem in order:

First, I gather from the CBMW piece that some people are trying to use the linguistic qualities of the word anthropos to determine Jesus’ gender. This doesn’t seem like the right approach to me. Again from the CBMW piece: “That Jesus is an anthropos means first of all that he is a human being; but it also means that he is a male human being.” I don’t think so.

Secondly, I frequently read claims like, “Jewish women [in Jesus’ day] were kept in subjection and sometimes even in seclusion” (from Scanzoni and Hardesty’s All We’re Meant To Be: Biblical Feminism for Today, quoted in the CBMW piece). Again, I don’t think so. Salome Alexandra ruled Judaea as queen for about a decade shortly before Jesus’ time. This was a hardly a culture that universally denied power to women.

At any rate, and in summary, lots of words have a variety of interrelated, sometimes contradictory meanings that are determined in part by context. The Greek anthropos is no different. Sometimes its meaning most closely overlaps with “man,” sometimes with “person,” sometimes with “human.” But picking and choosing examples without taking into account how language works will almost always lead to a conclusion that is as convincing as it is wrong.

September 20, 2013 Posted by | general linguistics, grammar, translation practice, translation theory | , , , , , , | 59 Comments

On Biblical Masculinity and Femininity

Gender roles are a hot topic, so it should come as no surprise that people are looking to the Bible for guidance.

Biblical-Masculinity-FemininityOver the summer, Larry Crabb published his Fully Alive: A Biblical Vision of Gender That Frees Men and Women to Live Beyond Stereotypes. Explaining it to Christianity Today, he says:

Neqebah (female) means one who is open to receive, has an invitational style of relating. And zakar (male) means one who remembers something important and then does it.

Unfortunately, Dr. Crabb makes fundamental factual and methodological errors here.

Factually, the Hebrew neqebah (“female”) comes from the root for “pierce,” not “open to receive.” Though the common translation of neqebah as “pierced” is probably not as accurate as “hollow,” the point is the same: the Hebrew neqebah describes the female sex organ.

More importantly, zakar (“male”) comes from a multifaceted root that does not simply mean “remember.” Rather, the root is connected more broadly to referring to something that is not physically present. One way of doing this is to remember something from the past, but there are many others. In Exodus 3:15, for instance, the root gives us zeker as a synonym for “name,” because a name is one way of referring to something that is not physically present. Another way is to point, and it may be this meaning that gives us the Hebrew zakar.

If so, the Hebrew word for “male” comes from the pointing organ and the word for “female” from the hollow organ.

But whatever the case, the methodological errors make the factual evidence irrelevant, because words do not get their meaning from their etymology. As I explain in And God Said, this is one of the most basic tenets of language, and also one of the most common Bible translation traps.

Just for example, a “building” in English comes from the verb to “build,” but that doesn’t mean that we primarily think of buildings in terms of how they are built, just as the word’s etymology doesn’t preclude the possibility of a building being something we occupy. Another English example is the pair of words “grammar” and “glamour,” which share an etymology even though most people don’t think of grammar as glamorous.

Similarly, the etymologies of the Hebrew words for “male” and “female” — memory and reception, or piercing and pierced, or pointing and hollow — are irrelevant to their meaning. So they do nothing to help answer Dr. Crabb’s question of “what God had in mind when he made a woman feminine and when he made a man masculine.”

It seems to me that what Dr. Crabb has done is take his own notions of what men and women should be and, through flawed linguistics, put them in the mouth of God.

September 17, 2013 Posted by | general linguistics, grammar, translation practice, translation theory, Translation Traps | , , , , , , , , , | 21 Comments

Is God a boy god or a girl god in the Bible?

If God is like a nurse, does that mean that God is female?

What got me thinking about things like this is that John Piper’s “desiring God” blog just ran a post called “Our Mother Who Art In Heaven?” The basic point is to affirm that God is a “masculine God” in spite of 26 places where God is described with feminine imagery.

The author, Tony Reinke, starts off as though he wants to examine the implication of those 26 places neutrally: “But one of the immediate objections to [a masculine God] is the simple fact that God sometimes references himself through feminine imagery, and this is certainly true.”

Of course, by phrasing the question as how “God references himself” (my emphasis), Reinke has already prejudiced the issue. Still, it’s an interesting question, and I don’t believe that Reinke, or John Cooper (whose book, Our Father in Heaven: Christian Faith and Inclusive Language for God, Reinke cites) have understood how language works in these cases.

Cooper’s point, quoted by Reinke, is that there may be a variety of feminine imagery, such as Numbers 11:12, where God “gives birth” to the People Israel. But even so, there “are no instances where God is directly identified by a feminine term, even a metaphorical predicate noun.”

Most interesting is Reinke’s explanation: “That explains why in Scripture we find many many masculine titles for God: Lord, Father, King, Judge, Savior, Ruler, Warrior, Shepherd, Husband, and even a handful of metaphorical masculine titles like Rock, Fortress, and Shield..

What would make “Rock” a “metaphorical masculine title”? Not that it matters, but the word itself is feminine in Hebrew (at least one of the words, eh-ven) and in Greek (petra). Similarly, what makes “lord,” “savior”, “ruler,” etc. masculine? Certainly nothing intrinsic to the words.

I think that Reinke and Cooper are going about this the wrong way. The gender of the words used to describe or identify God is irrelevant.

Rather — as in so many other instances — I think the key to understanding the language here is knowing how imagery works. After all, even if God is our king, God isn’t a king in the same sense that Harald V of Norway is. Rather, “God is our King” means that God has certain attributes of a king.

For example, here are three attributes once common to most kings:

  1. they reigned with absolute power
  2. they inherited their position
  3. they were men

It seems pretty clear to me that the metaphor of God as king refers to (1). It seems equally clear that it does not refer to (2). The question is whether it refers to (3), and I don’t think that it does. I think that (3) is incidental to the metaphor, like (2).

In other words, even though only men were kings, and God is a king, it doesn’t follow that God is a man or even like a man, just as even though only humans were kings, and God is a king, it doesn’t follow that God is human or like a human. (A similar issue arises with the word “man” itself: “How to be a Biblical Man.”)

There can be no doubt that gender roles in antiquity were more sharply defined than they are today. But I don’t think that this cultural difference gives us the clear answer that God was masculine. Rather, I think we have to see past it in order to understand the intent of the text.

July 6, 2012 Posted by | translation theory | , , , , , , , , | 10 Comments

How to be a Biblical Man

The ESV translation of 1 Corinthians 16:13 has Paul tell his audience to “act like men.” This tradition of translation goes back at least as far as the KJV, which renders the text “[behave] like men.” The NRSV, on the other hand, offers “be courageous.” What’s going on?

At issue is the Greek verb andrizomai. That word contains the root andr, which also gives us the word aner, “man.” (The “d” drops in and out, in accordance with Greek grammar. Aner is a “man,” and adres are “men,” for example.)

But the leap from the root andr to the translation “act like men” makes three mistakes.

The first is the wrong assumption that internal structure tells you what a word means. (I have more here: “Five Ways Your Bible Translation Distorts the Original Meaning of the Text.”) Relatedly, the root actually means “person,” not “man,” which we see from words like androphonos in 1 Timithy 1:9. The word phonos means “murder,” but androphonos means “murderer,” not “murderer of men.” (Similarly, “manslaughter” in English doesn’t only mean “slaughtering men.”) So we have methodological and factual errors.
Continue reading

March 2, 2012 Posted by | translation practice, translation theory | , , , , , | 9 Comments

Bible Translations Make News in 2011

According to the Religion Newswriters Association, Bible translation stories were among the top 10 religion stories of 2011.

The RNA singled out three events that contributed to the prominence of Bible translations in the news this past year:

  • Celebrations of the 400th anniversary of the King James Version. There’s no doubt that the King James Version (“KJV”) has had an unprecedented impact on English and on religion, as well as on the practice of Bible translation, though I insist that at this point its value lies less in what it tells us about the original text of the Bible — I did, after all, call it a fool’s gold standard — and more in its historical and cultural role. (For more on why I think the KJV is now inaccurate, take my “Exploring the Bible” video quiz: “Do You Speak KJV?“)

  • Criticism of the newest NIV. The NIV was officially published in 2011, but it was released on-line in 2010, which is perhaps why the RNA didn’t single out the publication of the NIV, but rather criticism of the gender decisions in it. Southern Baptists were especially vocal in this regard, and I don’t think this gender debate is going away. (Just a few days ago I was denounced by some Southern Baptists for my translation work, in particular for my suggestion in the Huffington Post that the Song of Solomon advocates equality between men and women.)

  • The completion of the Common English Bible (CEB). The CEB proved hugely popular, even beyond what its publishers expected, though I like it less than many. It’s not a surprise that the translation made news. It was reprinted twice within weeks of its initial run, and has over half a million copies in print. It also made some bold decisions, like changing the traditional “Son of Man” into “human one.”

Though all three of these news items seem to be about Bible translation, I think there’s more going on.

The gender debate, in particular, seems less about translation than about the role of men and women. As I told the AP, I think the NIV is a step backwards in terms of gender accuracy in translation. The loudest complaints this year were that it didn’t take a big enough step backward.

Similarly, I think the admiration (and sometimes reverence) that many people have for the KJV has a lot to do with keeping things the way they were.

And on the other side of the coin, part of the CEB’s appeal is tied up with specifically not keeping things the way they were.

Certainly one common theme here is how we deal with modernity. There seems to be a more specific message behind the stories, too, but I can’t quite put my finger on it.

December 15, 2011 Posted by | Bible versions, translation practice | , , , , , , , , , , | 5 Comments

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.

October 3, 2011 Posted by | translation theory | , , , , , | 30 Comments

Girl Animals, Boy Animals, and Neuter Animals

CNN’s belief blog has an interesting story about a request by PETA not to call animals “it” in Bible translations:

PETA is hoping the [NIV’s] move toward greater gender inclusiveness will continue toward animals as well.

“When the Bible moves toward inclusively in one area [human gender -JMH] … it wasn’t much of a stretch to suggest they move toward inclusively in this area,” Bruce Friedrich, PETA’s vice president for policy, told CNN.

Friedrich, a practicing Roman Catholic, said, “Language matters. Calling an animal ‘it’ denies them something. They are beloved by God. They glorify God.”

I think it’s an interesting and complex question, and I’ll try to post some reactions when I have time. For now, read the article.

March 24, 2011 Posted by | translation practice, translation theory | , , , , , , | 5 Comments

Top Translation Traps: Too Much Information

Translators frequently have information at their disposal that doesn’t come directly from the text they are translating.

Though it’s often tempting, it is nonetheless almost always a mistake to add the additional information into the translation.

For example, if a mystery novel starts, “a man was walking by the beach,” the translator should not change it to, “Mr. Smith was walking by the beach,” even if it later turns out that Mr. Smith was the man.

Dostoevsky’s Crime and Punishment begins with odin molodoi chelovek, “a young man.” The reader soon learns that the young man used to be a student. But it would surely be a mistake for a translator to render the Russian as “former student” instead of “man,” even though the guy happens to have been a student.

This sort of mistake comes up frequently in Bible translation.

Four Examples

People / Men — Anthropos

We just saw one clear case at Bible Gateway‘s new translation blog, regarding the people in 2 Timothy 2:2 (“and what you have heard from me through many witnesses entrust to faithful people [anthropoi] who will be able to teach others as well,” NRSV). The question there is whether the translation for anthropoi should be “people” or “men.”

Ray Van Neste’s answer notes that the leadership position referred to in 2 Timothy 2:1-7 “has been forbidden to women in [verse 12 of] 1 Timothy 2.” Based on this, Dr. Van Neste seems to claim that anthropoi should be translated “men.”

But even if he is right about who the anthropoi are, his reasoning is flawed. Just because the people are men doesn’t mean that anthropoi means “men,” or that “men” is the right translation, any more than “young student” is the right translation for the “young man” in Crime and Punishment.

Hebrews 5:1 works the same way. There, high priests are selected from among anthropoi. I suppose they were probably men, but that doesn’t mean the translation should say “men” where the original is broader: “people.”

Similarly, I suppose the people in 2 Timothy 2:2 were also followers of Christ. Should we therefore translate “reliable Christians” for pistoi anthropoi? Of course not. To translate “Christians” is to add information that comes from other parts of the text. To translate “men” is to make the same mistake.

People / Slaves — Nephesh

Another example came up in a comment to a discussion about nephesh in Genesis 12:5 on BBB: “Abram took … the persons [nepheshes] whom they had acquired in Haran…” (NRSV). Yancy Smith points out that some versions translate nephesh as “slave,” rather than “person,” because the nepheshes there are “acquired.”

But again, the reasoning (of the TEV and others) is flawed. Even if the people are slaves, there is a difference between “acquiring people” and “acquiring slaves.” The Hebrew has the former, and so should the translation.

The Son of God / Christ

A third example comes from Mark 1:1: “The beginning of the good news of Jesus Christ, the Son of God” (NRSV). The “Son of God” is, of course, “Christ,” also translated as “Messiah.” We see the identity, for example, in Matthew 26:63: “tell us if you are the Messiah, the Son of God” (NRSV). But that doesn’t mean that we can translate Mark 1:1 as “Jesus Christ, the Messiah.”

Dry Bones

Our final example for now comes from the “dry bone” prophesy in Ezekiel, who is told in verse 37:4: “Prophesy to these bones, and say to them: O dry bones, hear the word of the LORD” (NRSV). In verses 37:9 and 37:11, the reader learns that these bones are the “slain” “house of Israel.” It’s a brilliant progression, and it would be destroyed by translating “bones” as “slain of the house of Israel” in 37:4.

Summary

It seems to me that, wherever possible, translators should translate the text of the Bible without destroying the nuances of the original. And often, providing too much information makes a translation less accurate.

December 19, 2010 Posted by | translation practice, translation theory, Translation Traps | , , , , , , | 10 Comments

Gender in the Updated NIV

According to the translators’ notes for the updated (“2011”) NIV, “every single change introduced into the committee’s last major revision (the TNIV) relating to inclusive language for humanity was reconsidered.” This is in keeping with an announcement the translators made in 2009.

Some people were concerned about this, because they were afraid the translation committee might reverse some of the progress the TNIV made in preserving gender accuracy.

From the quick look I took today, it seems that the gender-neutral translations for humanity have largely been preserved.

OT Examples

For example, the phrase ashrei adam appears six times. In all six places, the TNIV had “those” for adam, an update from the 1984 “man” in five out of six of the instances.

In half of those cases (Psalm 32:2, Psalm 84:16, and Proverbs 28:14), the NIV2011 changes “those” to “the one,” while in the other half (Psalm 84:6(5), Proverbs 3:13(12), and Proverbs 8:34) the newer version retains “those.” I think it’s unfortunate that ashrei adam now enjoys two translations in English, but I think the more important point is that the gender neutrality was preserved in the new NIV.

Likewise, Psalm 1:1 with its similar asrei ha-ish is now “one.” It was “those” in the TNIV, and “man” in the older NIV84.

In Psalm 147:10, surprisingly, the NIV translators chose “warrior” for ha-ish. I think it’s a mistake, but it still demonstrates a commitment to gender accuracy in translation.

NT Examples

On the other hand, for Matthew 4:4 (ouk ep’ arto zisetai o anthropos), the NIV2011 reverses a decision made by the TNIV, reverting to “man” (which is what NIV84 had) for anthropos: “Man shall not live on bread alone.”

This is confusing. Unless the translators think that “man” is gender inclusive, the translation is wrong. But if they do think that “man” is inclusive, it’s not clear why they didn’t use it elsewhere.
Continue reading

November 1, 2010 Posted by | Bible versions, translation practice, translation theory | , , , , , , , | 19 Comments