As explained
see here
, this approach is characteristic of translating UP. Yet the source languages of the scriptures—Hebrew, Greek, and Latin—are still, without doubt, and especially for adherents to the faith, much nearer the essence of the texts’ religious meaning than any of the vernacular translations they could turn out. Seen in this light, twentieth-century Bible translation ought to be the largest case study we have of translating DOWN—translating from a language of prestige to a local idiom, from a “general language of truth” to a specific vernacular. However, the majority of Bible translations that Nida oversaw were not from Greek or Latin (and Hebrew even less) but from the American versions of the Bible in English, and from two influential Spanish versions, the Reina-Valera of 1909 and a simplified text called
Dios Habla Hoy
(“God Speaks Today”).
3
These are, of course, the “general languages” or “dominant idioms” in many parts of the world nowadays.
Retranslation (translating a text that is already a translation) is not a modern departure for the Bible. Only the Aramaic
targums
and the Greek Septuagint were translated directly from biblical Hebrew. The Armenian, Coptic, Old Latin, Syriac, Ge’ez, Persian, and Arabic translations of the Old Testament were done from the Greek; the Georgian Bible was probably first translated from Armenian (though it may have also used the Syriac and the Greek); the Old Gothic likewise, probably with some reference to Latin versions. Jerome used Hebrew and Aramaic texts to complement the Septuagint for his long-influential version of the Old Testament in Latin, and the original Greek for the New Testament. Early German translations of the Bible in the fifteenth century were done from Jerome’s Latin, as were the first Bibles in Swedish. Martin Luther was the first among European translators to use Greek and Hebrew as source texts; his German formulations were, however, copied by many translators into other European languages, who sometimes used Luther’s version as their sole source (the Icelandic Bible is a case in point). The Bible was not translated into French until the sixteenth century—from Latin and Italian, not from Hebrew or Greek. The first complete English Bible, by Miles Coverdale, also had no contact with the original languages but drew on Jerome’s Latin, a later Latin translation by Erasmus, and Luther’s German. The use of modern European translations to retranslate the scriptures into nearly two thousand mostly non-European tongues in the last hundred years is therefore no innovation in the long history of these texts, but it raises issues of great magnitude. It confirms and drives the perception of English and Spanish, not of Hebrew or Greek, as “languages of truth”; their status as the source for Bible translation is hard to separate from the political, economic, and cultural status of the speakers of these two vehicular tongues.
Translating DOWN from a dominant to a vernacular language is typically accompanied by substantial imports of vocabulary and syntactic constructions from the source. Such was the process that enriched and expanded Syriac when it was used as a vehicle for the preservation of Greek medicine and astronomy. Such was the process that altered and enhanced French when it became the target language for mass translation from Italian in the sixteenth century. Such was the process that Schleiermacher strongly recommended for German as the recipient of the treasures of Greek philosophy in the early nineteenth century. Target-language modification was also, in fact, the fate of English at the hands of the translation committee established by King James I. “The Lord Our God,” for instance, is less a Jacobean way of expressing the first-person plural possessive in English than it is a calque of Hebrew grammar: the corresponding expression in the Torah,
, pronounced “adonai ilehenu,” can be worded out as “God, the Lord-Our.”
The spread of English-language terms in the field of electronic communications into almost all the vehicular languages of the world (
computer
,
Internet
,
to surf
,
hardware
,
USB
, and so forth) is a contemporary reminder of what a language hierarchy is. The French would rather not be so reminded, and their government set up the Commission Générale de Terminologie et de Néologie in 1996 to push back the tide of foreign words. It may have more success than King Canute, but I wouldn’t bet on it.
Target-language modification through translations of prestigious works from a language of higher status may in some instances be imposed on the receiving cultures, but in most cases it is not. More characteristically, it arises from the wishes and needs of the translating community itself. (It hardly needs pointing out that there were no “Hebrews” around to spur King James’s translators to bend English into shapes more typical of Hebrew grammar.) But Bible translation in the twentieth century is a different kettle of fish. The agents of modern Bible translation into indigenous languages are closely involved in the missionizing project itself, and many of them are American as well.
They work into languages they have learned long after the critical age of language acquisition—they are what we termed L2 translators
see here
of this book. They therefore run the same kind of risk of creating unintentionally comical or offensive effects as do the creators of international signage in Croatian seaside hotels. Nida’s main concern was to try to ensure they did not.
Bible translation into non-European languages, which began with European colonial expansion as early as the seventeenth century, was highly inventive from the start. Albert Cornelius Ruyl, a junior trader in the Dutch East India Company with unusual linguistic skills, first taught himself Malay—a regional contact language—when he began his service in Sumatra. He wrote a grammar, then translated the Gospel of Matthew from Dutch. Ruyl altered and adapted Malay as he went along, using words from Arabic, Portuguese, and Sanskrit when he knew no corresponding term in Malay. But he also did something more.
Where the Dutch version of Matthew talks of a fig tree, Ruyl’s version has
pisang
—which means a banana tree in Malay. The substitution was justified by the fact that there were no figs on Sumatra. But what really marks it as special is that it signals a new ideology in the age-old business of translating DOWN. Ruyl initiated the principle of cultural substitution that Nida would theorize and promote three centuries later.
From Hebrew into Greek, from Greek into Latin, from Syriac into Arabic, and so forth, when the receiving language didn’t have a word for some item, it got a new one—the word of the source language, adapted to its new linguistic home. Not so from Dutch into Malay. The receiving language did not get a new word for a new thing. It got a substitute thing, with its existing word.
Douglas Hofstadter once asked, “How do you say ‘jazzercise’ in Aramaic?” He meant it as a mind game, not as a question about what the small group of Aramaic speakers in contemporary Jerusalem would say if they joined a gym and found themselves doing aerobics to a Dave Brubeck track. There is no reason why speakers in the ancient world should have had a word for a thing they did not have, but speakers of Aramaic or any other language today would have to choose one of three ways of making up a word for
jazzercise
. They might import the word as it stands, making whatever modifications in form that are needed to allow it to function in a sentence. Or they might take two Aramaic words with meanings analogous to “syncopated music” and “exercise” and run them together to make a new compound in imitation of the English. Finally, they might take an existing Aramaic word and expand its use to include musical stretch-and-jump. Those are the three ways in which new things can be represented in any receiving language—by a foreignism (the first option), a calque (second option), or a semantic expansion. Each of them changes the target language by one item, with possible repercussions over time on the use and form of other words. But cultural substitution would simply put some other, more or less analogous activity current in the world of Aramaic speakers in the place of “jazzercising.”
That’s what Ruyl did to Malay: he didn’t invent a new word for a new thing (“fig”), he used an existing word to say something else (“banana”). It worked only because there are no figs on Sumatra. When the referent of a term is available, such as a musical gym in an Aramaic-speaking quarter of Tel Aviv, cultural substitution can’t work as a way of translating an exotic term.
Imagine: Sir Walter Raleigh presents Queen Elizabeth I with an amazing root vegetable he’s brought back from the New World and beseeches Her Majesty to reward him for the discovery of … the turnip. It wouldn’t have worked because it was not a turnip. When you have a potato in your hand, you can’t call it by the name of anything that you could be holding in your other hand. “Cultural substitution” is a naming and translation device that is suited exclusively to things that aren’t there. You can’t just expand the meaning of
turnip
by using it to name things that aren’t turnips. Similarly, when Ruyl wrote
pisang
for “fig,” he did not expand the meaning of the Malay term. No new class of tree suddenly arose that included both bananas and figs. What this kind of cultural substitution really says is that you can’t really understand, and we’re not going to try to explain. Have a banana instead.
Analogy-based substitutions are frequent in non-European Bible translations. “White as snow” in the Bible text may become “white as a cockatoo’s feathers” in languages spoken in areas where snow has never been seen, or “white as a cotton boll” in some languages of South America. In Asmat, a language spoken in a swampy area of Indonesian Papua where houses are all built on stilts, the parable of the wise builder who builds on stone and the foolish builder who builds on sand turns into a story about a wise builder “who builds a house on stilts made of iron wood … while the foolish builder is the one who builds a house on stilts made of white wood” (white wood being used only for temporary hunting shacks, because it rots quickly).
4
Nida reports examples of even more extensive cultural transpositions he encountered and approved. In many parts of Africa, he says, casting branches in the path of a chief expresses contempt, whereas in the Gospels it is done to mark Jesus’s return to Jerusalem as a triumph. Similarly, fasting is not easily seen as a form of devotion in many parts of the world—it is more likely to be understood as an insult to God.
5
Revision of the Gospel’s account of Palm Sunday and of the role of fasting in the Old Testament is both absolutely necessary to avoid giving the wrong message to African readers and at the same time impossible without profoundly altering the story being told. Nida’s job was to help produce texts that were functionally equivalent to the Bible considered not as sacred script but as the repository of a sacred story.
Nida also promoted the use of native speakers of indigenous languages as full partners and, wherever possible, as prime movers in Bible translation projects. That’s because reliable judgments about the appropriateness of cultural substitutes are not easily made by L2 speakers. If acceptability is the paramount aim, then L1 speakers are in a much better position to invent and adapt. Their intuitions about acceptability are the ones that count.
Nida’s insistence on adaptive translation can be understood in two ways. First, it follows from the beliefs he shares with other Christians that a religious truth must be accessible to all humans, whatever their culture and language. Equally important, however, is Nida’s wish to respect the cultures that Bible translators inevitably affect and alter by their work. Adaptive translation is a compromise between these two contradictory aspirations. It helps the receiving culture accept and integrate something completely new by using terms that are already familiar.
Nida’s position is not popular among translation-studies scholars, particularly those mainly concerned with the translation of literary works. They might point out how preposterous it would be in the translation of an oral epic from an African language into English to replace
banyan
with
chestnut
on the grounds that banyan trees are nowhere to be seen in England’s green and pleasant land. Such attacks miss the main point, which is this: translating UP doesn’t normally use the same techniques as translating DOWN. There’s no good reason to think that a single undifferentiated set of practices or principles should or ever will hold sway over the whole vast field of translation. The hierarchical relationship between source and target isn’t the sole determinant of the methods that translators may use, but it affects quite fundamentally what they do and how they do it.