Following are a number of back-translations as well as a sample translation for translators of 2 Kings 15:38:
Kupsabiny: “Later, Jotham died and then he was buried where his forefathers were buried in the City of David. But then, his son who was called Ahaz took over rulership replacing his father.” (Source: Kupsabiny Back Translation)
Newari: “Jotham died, as had his ancestors. He was buried with them in the city of his ancestor, David. His son Ahaz became king after him.” (Source: Newari Back Translation)
Hiligaynon: “When Jotam died, he was-buried in the burial-place of his ancestors in the Town of David who was also his ancestor. And Ahaz his child/(son) succeeded him as king.” (Source: Hiligaynon Back Translation)
English: “Jotham died and was buried where his ancestors had been buried in the part of Jerusalem called ‘The City of David’. Then his son Ahaz became the king of Judah.” (Source: Translation for Translators)
Slept with his fathers: See the comments on 1 Kgs 1.21.
Was buried with his fathers: Good News Translation makes it specific that Jotham “was buried in the royal tombs.” See the comments on 1 Kgs 14.31.
The city of David: See the comments on 1 Kgs 2.10.
His father is translated “his ancestor” by New Revised Standard Version and “his forefather” by Revised English Bible. This phrase is omitted by Good News Translation, but there seems to be no compelling reason to do so.
Ahaz his son: If there is any doubt about who the pronoun his refers to, translators may have to say “Ahaz the son of Jotham.” Ahaz is mentioned at the beginning of the prophetic books of Isaiah, Hosea and Micah. Isaiah, in fact, refers to him frequently, especially in chapter 7. His reign is described in greater detail in the following chapter.
Reigned in his stead: See the comments on 1 Kgs 11.43.
Quoted with permission from Omanson, Roger L. and Ellington, John E. A Handbook on 1-2 Kings, Volume 2. (UBS Helps for Translators). New York: UBS, 2008. For this and other handbooks for translators see here .
Leave a Reply
You must be logged in to post a comment.