Following are a number of back-translations as well as a sample translation for translators of Job 10:11:
Kupsabiny: “You created my body with bones and sinews and covered (it) with flesh and then overlaid (it) with skin.” (Source: Kupsabiny Back Translation)
Newari: “You clothed me with flesh and skin, didn’t you? And you created me, supporting me with bones and blood vessels, didn’t you?” (Source: Newari Back Translation)
Hiligaynon: “You (sing.) formed me with bones and veins and wrapped with flesh and skin.” (Source: Hiligaynon Back Translation)
English: “He knows which people are worthless; and when he sees people doing wicked things, will he ignore it?/he will certainly not ignore it!” (Source: Translation for Translators)
Translators of different languages have found different ways with what kind of formality God is addressed.
Click or tap here to see the rest of this insight
Like many languages (but unlike Greek or Hebrew or modern English), Tuvan uses a formal vs. informal 2nd person pronoun (a familiar vs. a respectful “you”). Unlike other languages that have this feature, however, the translators of the Tuvan Bible have attempted to be very consistent in using the different forms of address in every case a 2nd person pronoun has to be used in the translation of the biblical text.
As Voinov shows in Pronominal Theology in Translating the Gospels (in: The Bible Translator2002, p. 210ff. ), the choice to use either of the pronouns many times involved theological judgment. While the formal pronoun can signal personal distance or a social/power distance between the speaker and addressee, the informal pronoun can indicate familiarity or social/power equality between speaker and addressee.
In these verses, in which humans address God, the informal, familiar pronoun is used that communicates closeness.
Voinov notes that “in the Tuvan Bible, God is only addressed with the informal pronoun. No exceptions. An interesting thing about this is that I’ve heard new Tuvan believers praying with the formal form to God until they are corrected by other Christians who tell them that God is close to us so we should address him with the informal pronoun. As a result, the informal pronoun is the only one that is used in praying to God among the Tuvan church.”
In Gbaya, “a superior, whether father, uncle, or older brother, mother, aunt, or older sister, president, governor, or chief, is never addressed in the singular unless the speaker intends a deliberate insult. When addressing the superior face to face, the second person plural pronoun ɛ́nɛ́ or ‘you (pl.)’ is used, similar to the French usage of vous.
Accordingly, the translators of the current version of the Gbaya Bible chose to use the plural ɛ́nɛ́ to address God. There are a few exceptions. In Psalms 86:8, 97:9, and 138:1, God is addressed alongside other “gods,” and here the third person pronoun o is used to avoid confusion about who is being addressed. In several New Testament passages (Matthew 21:23, 26:68, 27:40, Mark 11:28, Luke 20:2, 23:37, as well as in Jesus’ interaction with Pilate and Jesus’ interaction with the Samaritan woman at the well) the less courteous form for Jesus is used to indicate ignorance of his position or mocking.” (Source Philip Noss)
In the most recent Manchu translation of 1835 (a revision of an earlier edition from 1822), God is never addressed with a pronoun but with “father” (ama /ᠠᠮᠠ) instead. Chengcheng Liu (in this post on the Cambridge Centre for Chinese Theology blog ) explains: “In Manchu tradition, as in Chinese etiquette, second-person pronouns could be considered disrespectful when speaking to superiors or spiritual beings. Manchu Shamanist prayers avoided si [‘you’] and sini [‘your’] for this very reason. To use them for God would be, in Lipovzoff’s [one of the two translators] words, ‘the most uncouth and indecent way to speak to the Almighty — as if He were a servant or slave.’ There was also a grammatical problem. In Manchu, si and sini could refer to both singular and plural subjects. For a faith that insisted on the singularity of God, this was potentially confusing. By contrast, repeating ama removed any ambiguity.”
Click or tap here to see the rest of this insight.
Like a number of other East Asian languages, Japanese uses a complex system of honorifics, i.e. a system where a number of different levels of politeness are expressed in language via words, word forms or grammatical constructs. These can range from addressing someone or referring to someone with contempt (very informal) to expressing the highest level of reference (as used in addressing or referring to God) or any number of levels in-between.
One way Japanese shows different degree of politeness is through the usage of an honorific construction where the morpheme are (され) is affixed on the verb as shown here in the widely-used Japanese Shinkaiyaku (新改訳) Bible of 2017. This is particularly done with verbs that have God as the agent to show a deep sense of reverence. Here, am-are-ru (編まれる) or “knit/twine” is used.
Thou didst clothe me with skin and flesh: Job continues to remind God how he has been intimately responsible for Job’s prenatal development. Some translations take this verse to be a question, as in verse 10. God is the subject of the verb. And knit me together with bones and sinews: the verb translated knit implies in today’s English the use of needles to intertwine two threads to form a fabric or cloth. The meaning of the Hebrew term is better conveyed by “weave, intertwine, form, or shape.” Good News Translation reverses the two lines to give a more logical sequence. That is, it prefers to have the body formed first with bones and sinews and then covered with muscles and skin, and this may be preferred in other languages. Reversing the sequence in this fashion, the whole verse may be expressed as “wove my body together with bones and muscles, and covered it with flesh and skin.”
Quoted with permission from Reyburn, Wiliam. A Handbook on Job. (UBS Helps for Translators). New York: UBS, 1992. For this and other handbooks for translators see here .
Leave a Reply
You must be logged in to post a comment.