God Didn't Say That

Bible Translations and Mistranslations

Q&A: Morphology in Ruth 2:10

From the About page:

Still working on he and vav and I came across this pair of words in Ruth vatishtachu artza.

Two questions — why the vav at the end of the first word? And why the he at the end of the second? KJV translates it as if it were hithpael — she bowed herself to the ground.

I’m playing catch-up after a wonderful visit to Israel, so I thought I’d start with a grammar question. (After all, nothing says “fun” like a little morphology.)

The first word is a wonderful combination of all sorts of grammatical processes. It’s the apocopated hitpa’el, future feminine third person singular. The root is Sh.Ch.H, and the shin and the tav metathesize (“switch places”) as expected with sibilants in hitpa’el.

By apocopated (“short”) I mean that the the final heh from the root Sh.Ch.H has dropped off, as final hehs frequently do in the future third-person singular. (Another example is vayavk instead of vayivkeh for “he wept.”)

So we would expect the form to be vatishtachv instead of vatishtachaveh. The extra vowel in the longer form under the chet — the “a” after the “ch” in transliteration — comes to prevent the frequently undesirable condition of a syllable ending with a chet. In the shorter form, however, another stratagy prevents a chet-final syllable. The consonantal vav becomes vocalic. This, too, is a regular part of Hebrew grammar — consider the prefix “and” which can be v’- or u- (among other possibilities) — but grammar books don’t often emphasize the general nature of this process.

So the first word is just “she bowed.” (Perhaps “bowed herself” was English when the KJV was composed, but now that translation is just wrong.)

As for artza, the final heh is directional. The word means “toward the ground.”

So we have metathesis, apocopation, and resyllabification in the first word. And — perhaps refusing to disappear completely — the missing heh from the first word shows up on the second.

January 8, 2010 Posted by Joel H. | Q&A, grammar | , , , , , , , | 1 Comment

Q&A: Girl Nations and Boy Nations

From the About comes this great question:

I have a question about the gender of nations. It seems like nations can be referred with both masculine and feminine pronouns. Is there any significance with this change? For example, Moab is “he” in Isa 16:12, Israel is “he” in Jer 2:14; 50:17 but “herself” in Jer 3:11, and Babylon is “she” in Jer 50:29, just to name a few.

What a fascinating observation for those of us who love language.

Gender, as we know, is more complex than Language 101 classes would suggest (I have some particularly vexing examples here), and it’s not unheard of for words to allow two genders.

For example, the Modern Hebrew shemesh, “sun,” is generally feminine but in poetry can be masculine. In this case, the agreement choice even has implications for the translator, because masculine agreement is a sign of poetic register.

On the other hand, multiple gender agreement is fairly rare. So when we see dual agreement with so many nation-words (“Moab,” “Damascus,” “Egypt,” “Israel,” and others) we have to assume that this is more than coincidence.

To get a sense of the issue we need only look at Isaiah 17:1. There, damesek (“Damascus”) is first masculine, then feminine: hinei damesek musar [masculine] mei’ir v’hayta [feminine] m’i hapala, that is, “Damascus will cease to be a city and will become a pile of rubble.” “Will cease” is masculine and “will become” is feminine.

Another example is mitzrayim (“Egypt”). In Exodus 12:33 the word for the nation takes a feminine verb, in Psalm 105:38 (sometimes numbered 104:38), a masculine one.

Exodus 14:25 expands the data set a bit, because Egypt is personified as “I,” not “we”: vayomer mitzrayim anusa…, “Egypt said, ‘I will….’,” though every translation I know of, including the LXX, renders this as “we will…” Going back to Exodus 12:33, we see that even though mitzrayim takes a feminine singular verb at first, the continuation of the verse is masculine plural.

Unfortunately, I don’t have an easy way to gather all of the verbs that have a particular subject. So for now this is more like a “Q and not really A,” because I don’t have an answer yet.

(As a guess, this is a case of conflicting agreement considerations. For example, in English, “either he or I will be in jail” is perfectly grammatical. But it’s not so easy to put that sentence into the present. “Either he or I am in jail?” No. “Either he or I is in jail?” Also no. “Either he or I are in jail?” A little better. I suspect that, similarly, in Hebrew there were reasons for nations to be masculine and feminine, singular and plural. But without more data, it’s hard to form a more concrete conclusion.)

Can someone provide a complete or nearly complete set of the verbs for, let’s say, “Israel,” “Moab,” “Egypt” and “Damascus”?

December 27, 2009 Posted by Joel H. | Q&A, translation practice, translation theory | , , , , , , , | 3 Comments

Q&A: Who is bowing down in Psalm 97:7?

From the About page comes this question:

The NET Bible does not render imperatives in Psalm 97:7, while others do. Their footnote is helpful, but not enough for me to opine on which is right. What light can you shed on this?

The phrase here is hishtachavu lo kol elohim. The last three words mean, “to-him all gods.” As chance would have it, though, the verb that starts the phrase could be either an imperative plural or a third personal past plural form. (Except for 2nd person masculine singular future and 3rd person feminine singular future, this doesn’t happen a lot in Hebrew. Usually the role of a Hebrew verb is clear from its form.) For example, in Psalm 96:9, the word hishtachavu is imperative; in Jeremiah 8:2, 3rd-person past.

Furthermore, the word order is ambiguous because — unlike English — the post-verbal phrase in Hebrew can be a subject of any sort.

Finally, even context doesn’t help here.

So the Hebrew means either “all the gods bowed down to [God]” or “all you gods, bow down to [God].”

We do get a clue from the LXX — which translates hishtachavu as an imperative here — but the LXX is generally very unreliable when it comes to disambiguating Hebrew.

So in Psalm 97:7 we have that rare instance of a truly ambiguous text.

December 27, 2009 Posted by Joel H. | Q&A, translation practice | , , , , , | 5 Comments

Too Much Emphasis

It seems that the default explanation for an unknown grammatical feature is to assume, often wrongly, that it is “emphatic.” Here are four examples, three from Hebrew (skip to them: one, two, three) and one from Greek (skip to it here).

The Examples

The Infix Nun

From time to time, a nun will appear between a verb and its pronominal objective ending. For example, in Psalm 72:15, we find y’varachenhu. Breaking down the verb form, we find the prefix y’- representing third-person singular future; the verb varach, “bless”; and the suffix -hu for “him.” So far, the verb means “he will bless him.” But there’s also an added -en- in the middle. That’s the infixed nun, commonly called the “nun emphatic.”

Because nuns are frequently replaced by a dagesh in Biblical Hebrew, it is more common to find the “nun emphatic” represented by nothing more than a dagesh. Probably the best known example is in the Priestly Benediction from Numbers 6:24-26. The last verb of Numbers 6:25 is vichuneka, with a dagesh in the final kaf representing the “nun empahtic” that dropped out.

But there is no evidence anywhere to suggest that this nun has emphatic force.

The Infinitive Absolute

A much more common Hebrew construction is the “infinitive absolute” in conjunction with a conjugated verb form. For example, in Genesis 2:17 we find mot tamut, which the KJV notes in a footnote is literally “dying thou shalt die.” Based on the (wrong) assumption that this doubling of verb forms is emphatic, the KJV translates “thou shalt surely die” here. (As it happens, this Hebraism is preserved in the LXX thanatu apothaneisthe, “by death die.”)

But not only is there no evidence that this construction is emphatic, there is evidence that it is not. In Genesis 3:4 the snake tries to convince the women to eat from the forbidden tree; he (it?) reassures her that lo mot t’mutun. Obviously this doesn’t mean “you will not surely die.” It just means “you will not die.”

The Lengthened Imperative

Frequently a verb form will have two imperatives: a shorter one, essentially the future without the prefix, and a longer one with an additional heh at the end. For example, from titen (“you will give”) we have both ten in Genesis 14:21 and t’nah in Genesis 30:26. Some grammars, such a Gesenius (wrongly, in my opinion), suggest that the latter is “give!” Again, there’s no evidence for an emphatic reading in these verb forms. (The forms are also not limited to the imperative, as we see in the continuation of Genesis 30:26, with elecha for elech.)

The Greek Emphatic Pronouns

The forth example comes from Greek, which has two sets of 1st- and 2nd-person pronouns. For example, “my” is either mou or emou. The latter form is called “emphatic” because it is widely assumed to convey particular emphasis. Once again, though, there is nothing to suggest that the longer forms are necessarily more emphatic than the shorter ones. (Bill Mounce has a post — also available here — where he similarly notes that sometimes the “emphatic forms [...] are significant, but when they are objects of prepositions, evidently not.” In other words, he notes a case where the “emphatic” forms are not emphatic.)

Summary

What all four of these cases have in common is that the supposedly emphatic forms are longer than the ordinary ones. I think there has been a general if misguided assumption that longer words are more emphatic that shorter ones. At one level, it seems reasonable. And there are even times when it’s true (I give some examples here). But it’s not a general principal.

I think we have to rethink all of these “emphatic” forms with an eye toward figuring out what they really represent.

December 21, 2009 Posted by Joel H. | general linguistics, translation theory | , , , , , , , , , | 12 Comments

Q&A: Is God’s Son The Son of God?

Another great question from the About page:

I have a question about Matthew 27:54. The centurion and the rest of the detachment set to guard JesusÂ’ body cried out and said “truly he was the Son of God!” — or is that really what they said?

Since it lacks the articles in Greek, and Latin doesn’t have articles, is it possible that they really said “truly he was the son of a god!”?

It’s a simple question with a complex answer.

There are two parts to understanding the issue.

The first is how Greek conveys possessives like “God’s.” In Greek, a possessor is marked by the genitive case, similar to the apostrophe “s” in English. So “God” in Greek is theos and “God’s” is theou. This same genitive also plays the role that “of God” does in English. Similarly “Paul” is paulos and “of Paul” and “Paul’s” is paulou.

At first glance, this seems to be Greek 101, but there a very important nuances that hide in the details. To get a sense of them, we can look just at English, and note that there are three expression that look like they should mean the same thing but do not: “Paul’s,” “of Paul,” and “of Paul’s.” Moving to less religiously charged words helps, so we can better compare:


  • I am a friend of Bill. / I am a vice-president of the company.
  • I am the friend of Bill. / I am the vice-president of the company.

  • I am a friend of Bill’s. / I am a vice-president of the company’s.
  • I am the friend of Bill’s. / I am the vice-president of the company’s.
  • I am Bill’s friend. / I am the company’s vice-president.

Some of these sentences are ungrammatical in English (“I am a VP of the company’s”) and some are odd (“I am the friend of Bill”). Proper names work differently that common nouns, which is why “friend of Bill’s” is so much better than “vice-president of the company’s.” Importantly, some of these phrases imply “the”: “I’m the company’s VP” most naturally means that the company has only one VP. In short, we see a lot of complexity, and subtle nuance related to (1) nouns vs. proper names; and (2) definite vs. indefinite readings.

The second part to understanding Matthew 27:54 is even more complex. “God” in Greek is either theos (“god”) or o theos (“the god”). In John 1:1, for example, the word was with o theos but the word was theos.

My guess is that the two ways of saying “God” convey different nuances, but I’ve yet to see a convincing analysis of the pattern, even though there are lots of partial explanations. Until we understand the pattern, though, I think it will be almost impossible to know how the two phrases for God interact with the genitive.

It’s perfectly reasonable to think that “[a] son of god” means “one son (among many) of one god (among many),” but that’s just based on our English grammar. The syntactically parallel “[a] son of Moses” is only likely — again based on English grammar — to mean “one son (among many) of (the one and only) Moses.” Yet the English “Moses’ son” might mean “(the one any only) son of (the one and only Moses),” even though the Greek would be the same in the last two cases.

We also have the word order to deal with. In Matthew 27:54 (along with 14:33), we find theou uios, instead of the more common reverse order.

All of which is a long-winded way of saying that I don’t think we can conclude that the Greek means what “a son of a god” would in English. So your interpretation is certainly possible, but I don’t think it’s more (or less) likely than the more common “Son of God.” (I also think that theou uios would have sounded very different in Greek than o uios tou theou [e.g., Matthew 26:63], with two determiners and a different word order — and as a guess, the word order adds more than it seems.)

I do think that we’re missing something important here, and Matthew 27:54 is a valuable clue.

December 13, 2009 Posted by Joel H. | Q&A, translation practice | , , , , , , , , | 3 Comments

How Many Women is One Woman in 1 Timothy 2:12?

Peter Kirk drew my attention to a post by Bill Heroman about I Timothy 2:

If anyone wants us to be perfectly literal about 1 Tim 2:12, we should note, at least as a beginning, that Paul is primarily speaking against one-on-one mentoring, female to male. “I do not allow a woman to teach or to direct a man.” Everything in this statement is entirely singular. [Emphasis in original.]

Bill then asks whether “[t]he male/female intimacy of a one-on-one discipling relationship may be all Paul is really afraid of.”

In other words, Bill suggests that Paul may not be talking about women in general, but rather about one woman teaching one man, in private (and perhaps even the specific instance of that).

It’s a lovely suggestion — and I laud the effort — but I don’t think the grammar supports it.

It’s common to use singular nouns generically, both in English (which is why I might equally write that “it’s common for a singular noun to be used generically”) and in Greek. Furthermore, the tendancy in Greek is to use eis (“one”) to refer specifically to one of something.

For example, in John 11:50 we find, “it is better for eis anthropos to die…,” that is “one person.” Without eis the text would more naturally mean that it is better for people to die. I think that John 11:50 is particualy instructive because the context could make it clear that anthropos means just one person, because “it is better for people to die than for the whole nation to perish” doesn’t make any sense. But the grammar still has to support the context.

So it seems that the way to say, “I do not allow one woman to teach one man” would be to use the word eis twice.

Even so, I have to agree with Peter, who “love[s] the way that blogger Bill Heroman is prepared to think outside the box.”

December 10, 2009 Posted by Joel H. | translation practice | , , , , , , , , | 7 Comments

On Contractions

The issue of contractions in English translations has come up again recently, so I thought a look at how contractions work in English might be a good idea.

Spoken English

Spoken languages tend to obey a general rule that less is more, or, more specifically, the shortest form possible is generally the only grammatical form. So if there are two forms, one short and one long, a speaker needs a reason to use the longer one.

For example:

- Where’s Bill?

- I saw him yesterday.

In my dialect, there are two ways to pronounce “him,” namely, him and im. The only natural way to say “I saw him yesterday” is to contract “saw him” into “saw’im.” The “less is more” rule is why “saw him” sounds unnatural.

However the shorter form can’t be used when it’s conjoined. (I’ll explain why below.) So:

- Where are Bill and Mary?

- I saw him and her yesterday.

There’s no way to change “saw him and her” into *”saw’im and’er.” It’s just not Enlgish.

Similarly, “I am” can only be pronounced “I’m” in most circumstances in English, but, again, there are cases where “I’m” is impossible. (For example, *”he’s taller than I’m.”)

Clitics

The shorter words “‘im,” “‘er,” “‘m,” etc. are clitics, a term more familiar to students of Romance languages than of English. But English has them too. And, in fact, like all clitics, they obey three general rules:

1. They can’t be conjoined (combined with “and,” “or,” etc.).

2. They can’t be emphasized or contrasted.

3. They need something to latch on to.

Rule (1) is what goes wrong with *”I saw’im and’er.” Rule (3) is why *”He’s taller than I’m” is so terrible in English. And Rule (2) prevents “Oh, Bill? I saw him sneaking into the cookie jar” from becoming *”…I saw‘im…”

(Some dialects of British English have a full word “im” which isn’t a clitic but rather the word “him” with a silent “h.” That’s different from (to) the clitic.)

Other impossible examples in English include *”he’s and always will be king” (Rule 1), *”he wasn’t known back then but he’s now” (Rule 2), and *”I know what you’re.”

Written English

Native speakers are often unaware of their own speech patterns, which may be why, for a long time, contracted spoken forms were written out in full. About 500 years ago, though, English printers starting using the apostrophe to indicate “missing letters,” which is to say, letters which might be written in a word but which are not pronounced (including, perhaps, the missing “e” in the now-defunct genitive ending “-es,” which may be why the “’s” is used for possession today).

With some exceptions (“’s” of possession, “o’clock,” etc.) the apostrophe came to be associated with speech, and then informality. For this reason it was frowned upon in early 20th century writing.

But English writing — at least in America — has seen a general trend toward informality. The word “whom” is practically dead. (Though even Fowler, many years ago, advised rewriting a sentence that called for “whom.”) The informal “preposition at the end of a sentence” used to be a sign of poor written English; now it’s common (e.g., “to whom are you speaking?” vs. “who are you talking to?”) And so forth.

Along with this trend, apostrophes and contractions have returned to written English.

So the use of the apostrophe is really a matter of spelling. When the words are read aloud, most people will pronounce “I will” as “I’ll” no matter how it’s spelled, just like they will pronounce “donut” (“doughnut”) the same way regardless of the spelling.

But because of it’s association with informality, the apostrophe is also a subtle yet powerful clue about the general nature of the text.

November 6, 2009 Posted by Joel H. | general linguistics | , , , , | 7 Comments

Q&A: The Hebrew Suffix -ki

Again from the about page:

What’s going on with the pronominal suffixes in Psalm 103 3-8? I can’t find -ki as a pronominal suffix in any of my grammar books — neither singular nor plural!

Good question.

The suffix -ki (also spelled -chi) is a variant form of -k, and it means “your (sng, f).” We see it in Psalm 103, as you note, and also, e.g., in Psalm 116:19 (b’tocheichi, “within you [Jerusalem]“).

It may have been formed by analogy with the feminine singular future tense, or may be part of a broader pattern in which matres lectionis get added to words for reasons we no longer know (poetic affect, maybe). Other examples include the final heh that is added to some verbs, and, perhaps, the alternation between al and alei.

October 28, 2009 Posted by Joel H. | Q&A, grammar | , , , | 1 Comment

Hebrew Grammar Quirks

Still following up on what Pete Enns said:

Second, I would be prepared at how Hebrew does not “behave itself,” i.e., how grammars necessarily abstract the language almost to the point where a fair amount of what you’ve been learning doesn’t correspond to the actual biblical text.

More than once I have encountered this sort of surprise at the biblical text. So I’m curious, what sorts of quirks of Hebrew grammar have people encountered that seem to run contrary to what they learned about Hebrew?

October 8, 2009 Posted by Joel H. | general linguistics | , , , | No Comments Yet

The Grammar Can’t Be Wrong

In an interview with Karyn Traphagen, Pete Enns says:

Second, I would be prepared at how Hebrew does not “behave itself,” i.e., how grammars necessarily abstract the language almost to the point where a fair amount of what you’ve been learning doesn’t correspond to the actual biblical text.

While a printed grammar of a language can be (and frequently is) wrong, the underlying grammar of the language is always right. That is, there are rules by which all languages operate, and one task of the linguist is to discover those rules. In this regard modern linguistics, beginning last century, has been particularly helpful. (Steven Pinker’s The Language Instinct is a great introduction.)

So if people are working from books that don’t match up with the language they’re studying, I think it’s time to stop blaming the language and start blaming the books.

October 8, 2009 Posted by Joel H. | general linguistics | , | 2 Comments