The term that is transliterated as “Canaan” in English is translated in American Sign Language with the sign loosely referencing the act of hiding/covering one’s face in shame. The association of “shame” with the name “Canaan” comes from Genesis 9, specifically verse 9:25. This sign was adapted from a similar sign in Kenyan Sign Language (see here). (Source: Ruth Anna Spooner, Ron Lawer)
“Canaan” in American Sign Language, source: Deaf Harbor
Click or tap here to see a short video clip about Canaan in biblical times (source: Bible Lands 2012)
In Bauzi “swear” can be translated in various ways. In Hebrews 6:13, for instance, it is translated with “bones break apart and decisively speak.” (“No bones are literally broken but by saying ‘break bones’ it is like people swear by someone else in this case it is in relation to a rotting corpse’ bones falling apart. If you ‘break bones’ so to speak when you make an utterance, it is a true utterance.”) In other passages, such as in Matthew 26:72, it’s translated with an expression that implies taking ashes (“if a person wants everyone to know that he is telling the truth about a matter, he reaches down into the fireplace, scoops up some ashes and throws them while saying ‘I was not the one who did that.'”). So in Matthew 26:72 the Bauzi text is: “. . . Peter took ashes and defended himself saying, ‘I don’t know that Nazareth person.'” (Source: David Briley)
The Hebrew, Aramaic, Greek, Ge’ez, and Latin terms that are typically translated as “mercy” (or “compassion” or “kindness”) in English are translated in various ways. Bratcher / Nida classify them in (1) those based on the quality of heart, or other psychological center, (2) those which introduce the concept of weeping or extreme sorrow, (3) those which involve willingness to look upon and recognize the condition of others, or (4) those which involve a variety of intense feelings.
While the Englishmercy originates from the Latinmerces, originally “price paid,” Romance languages (Italian, Spanish, Corsican, Catalan, Friulian) and other Germanic languages (German, Swedish, Danish — Barmherzigkeit, barmhärtighet and barmhjertighed, respectively) tend to follow the Latin misericordia, lit. “misery-heart.”
Many languages distinguish between inclusive and exclusive first-person plural pronouns (“we”). (Click or tap here to see more details)
The inclusive “we” specifically includes the addressee (“you and I and possibly others”), while the exclusive “we” specifically excludes the addressee (“he/she/they and I, but not you”). This grammatical distinction is called “clusivity.” While Semitic languages such as Hebrew or most Indo-European languages such as Greek or English do not make that distinction, translators of languages with that distinction have to make a choice every time they encounter “we” or a form thereof (in English: “we,” “our,” or “us”).
For this verse, the Jarai and the Adamawa Fulfulde translation both use the exclusive pronoun, excluding Eleazar, Joshua, and the heads of the families of the tribes of the Israelites.
Following are a number of back-translations as well as a sample translation for translators of Joshua 2:12:
Kupsabiny: “But now, please, swear before God that you will honor the house/family of my father as I have honored you. And especially, what mark/sign is there by which I will know that” (Source: Kupsabiny Back Translation)
Newari: “So now, because I have shown loyalty to you, please swear an oath me in the name of the LORD that you will also show loyalty to our family circle. And please give me a sure sign of this. ” (Source: Newari Back Translation)
Hiligaynon: “Therefore now, [you (plur.)] swear in the name of the LORD that you (plur.) will-show kindness to my family, as I have- also -showed you (plur.) kindness. [You (plur.)] give me a guarantee” (Source: Hiligaynon Back Translation)
English: “So now I want you to solemnly promise me, and ask Yahweh to punish you if you do not do what you promise. Solemnly promise me that you will act kindly to me and my family, because I have acted kindly to you.” (Source: Translation for Translators)
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 choice of a formal plural suffix to the second person pronoun (“you” and its various forms) as shown here in the widely-used Japanese Shinkaiyaku (新改訳) Bible of 2017. In these verses, anata-gata (あなたがた) is used, combining the second person pronoun anata and the plural suffix -gata to create a formal plural pronoun (“you” [plural] in English).
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 choice of a benefactive construction as shown here in the widely-used Japanese Shinkaiyaku (新改訳) Bible of 2017.
Here, chikatte (誓って) or “swear” is used in combination with kudasaru (くださる), a respectful form of the benefactive kureru (くれる). A benefactive reflects the good will of the giver or the gratitude of a recipient of the favor. To convey this connotation, English translation needs to employ a phrase such as “for me (my sake)” or “for you (your sake).” (Source: S. E. Doi, see also S. E. Doi in Journal of Translation, 18/2022, p. 37ff. )
Leave a Reply
You must be logged in to post a comment.