Part 2: Does Isaiah’s Servant Really Die for the People? The ancient witnesses to Isaiah 53:8 disagree on a central confession about Jesus’ death found in the New Testament. John D. MeadeIsaiah’s fourth servant song is by far the most famous, not least because Christians have long read it as one of the greatest Old Testament prophecies about the heart of the Christian faith, the death of Jesus. In this Easter series, we are focusing on major textual problems in Isaiah 53 as a necessary step in identifying the suffering servant. In our Easter series on major problems in the text of Isaiah 53, we now come to the end of Isaiah 53:8. Most of our English translations read the final line of the verse similar to the ESV, “who considered that he was cut off out of the land of the living, stricken for the transgression of my people.” The NIV has “he was punished,” while the NET reads “he was wounded.” These translations clearly convey that the servant was stricken for the transgression of God’s people. The new NASB 2020 renders the text slightly differently: “For the wrongdoing of my people, to whom the blow was due.” Here, the NASB’s rendering signals that the blow was due to the people and does not portray one, single servant as being stricken or punished. These different renderings arose because of a difficult Hebrew text, whose history shows variants and different ways of understanding it as we shall see. These different renderings arose because of a difficult Hebrew text. The New English Bible actually renders a different Hebrew text, “stricken to death for my people’s transgression.”1See also the commentary by Joseph Blenkinsopp, Isaiah 40–55: A New Translation with Introduction and Commentary (New Haven: Yale University Press, 2002), 345, for a similar translation. According to this translation, the servant is stricken to death, an idea not clearly presented in the translations mentioned above. Clearly, there are two different translations coming from two different Hebrew texts. This problem requires a deeper look at the ancient witnesses in order to arrive at a solution. The testimony of the ancient witnesses First, we will list all the witnesses in original language and English translation, group them according to the Hebrew text they attest, and finally make some observations about them. The textual problem is indicated in each witness by the use of italics so that one can see the different readings most clearly. ReadingWitnessText1. He was stricken to deathLXXDue to the lawless deeds of my people, he was led to death ἀπὸ τῶν ἀνομιῶν τοῦ λαοῦ μου ἤχθη εἰς θάνατον2. He was stricken for them1QIsaaDue to the transgression of his people, he was stricken for them מפשע עמו נוגע למו3. He struck themMS 715Due to the transgression of my people, he struck themמִפֶּשַׁע עַמִּי נָגַע לָמֹוTheodotion, AquilaDue to the faithlessness of my people, he struck themἀπὸ ἀθεσίας τοῦ λαοῦ μου ἥψατο αὐτῶνLatin VulgateDue to the sin of my people, he struck thempropter scelus populi mei percussit eosSyriac PeshittaAnd due to iniquities of my people, they struck himܘܡܢ ܥ̇ܘ̈ܠܐ ܕܥܡܝ ܩܪܒܘ ܠܗAramaic TargumThe sins which my people sinned he will cast on themחובין דחבו עמי עד לותהון ימטי4. Strike was theirsMTDue to the transgression of my people, the strike belonged to them מִפֶּשַׁע עַמִּי נֶגַע לָמֹו SymmachusDue to the offense of my people, the strike belonged to them διὰ τὴν ἀδικίαν τοῦ λαοῦ μου πληγὴ αὐτοῖς 1QIsab, 4QIsadDue to the transgression of my people, the strike(?) belonged to them מפשע עמי נגע למוA survey of witnesses to Isaiah 53:8 To summarize, the witnesses attest four main options for the original Hebrew: “he was stricken to death” LXX “he was stricken for them” 1QIsaa “he struck them” MS 715, Theodotion, Aquila, Vulgate, Peshitta, Targum “the strike belonged to them” MT, Symmachus, 1QIsab(?), 4QIsad(?) Isaiah 53:8 in Codex Leningrad (1008 AD), 1QIsaa (2nd c. BC), and Codex Sinaiticus (4th c. AD). Images from Sefaria, Wikipedia, Codex Sinaiticus Surveying the evidence Reading 1 The first reading is based on the Hebrew source of the Septuagint (LXX), which differed slightly but significantly from the Masoretic Text (MT): “he was stricken to death” (נֻגַּע לַמָּוֶת). Although the LXX has the verb “he was led,” the translator probably wanted to harmonize 53:8 with 53:7 (“as a sheep was led to the slaughter”) by using the same Greek verb. Thus, the Hebrew source of the LXX contained the same consonants for the word “stricken” as all our other Hebrew manuscripts and most probably agreed with the verb that we see in 1QIsaa, the most famous Dead Sea Scroll. Because most of our English translations are based on the MT, readings like this one are often overlooked and not even included in a footnote. We will return to the full reading of the LXX below as we make a decision on the original text. Reading 2 The second reading is found in 1QIsaa and it also differs from the MT slightly: “he was stricken for them” (נוגע למו). Although most of our English translations render the MT as a passive verb (“was punished”), the only clear ancient evidence for such a translation is actually found, not in the MT, but in 1QIsaa, a manuscript discovered seventy-five years ago. Reading 3 The third reading is based on several witnesses that usually agree with the MT but, here, differ with it slightly by giving “he struck them” (נָגַע לָמֹו). Not only was this the Hebrew source of several ancient translations such as the Latin Vulgate, but it is also attested in one medieval Hebrew manuscript (known as DeRossi 715). Thus, this vocalization was probably known from an earlier time and existed alongside the MT’s reading (see Reading 4). But this, like reading 4 below, arose from a guess. The reason for this is that the translators and the later scribe didn’t have a copy of the text with vowel letters (known as matres lectiones) like what we find in 1QIsaa or the later vowel signs. RelatedA New Series on Isaiah’s Suffering ServantJohn D. MeadeRecovering the Resurrection in Isaiah 53: Textual Criticism and EasterJohn D. MeadePart 3: The Servant’s Burial according to the ScripturesPeter J. Gentry Reading 4 The final reading is found in the MT and reads “a strike belonged to them” (נֶגַע לָמֹו). Only Symmachus, who revised the Greek Septuagint around 200 AD, unambiguously preserves a noun “strike” in agreement with the MT (1QIsab and 4QIsad are ambiguous on this point). That’s a fascinating observation in itself since most English translations claim to translate the MT and then usually footnote where they diverge from it—but here they give no note. Regarding the meaning of who receives the blow (“to them”; לָמֹו), only the Syriac Peshitta has “him,” but it also rendered the verb as a plural “they struck,” which is a clear sign of interpretation. This raises the question about whether the Hebrew pronoun (לָמֹו) is plural “them” or singular “him.” All the ancient translations (except Peshitta) use the plural “them,” and this is the normal way to read the Hebrew. But the very interesting part is that most of our English translations lack an equivalent for this word in the MT (but see NASB above), probably because it is difficult to translate. But a literal translation of the MT would be “a strike belonged to them.” In context, this would refer to the people of Israel as the ones receiving the blow. By now, one can see that textual criticism is essential for understanding what happens to the suffering servant and so for identifying who he is. The careful study of our witnesses not only shines a light on the textual problems, but it also offers a probable solution too. Unfortunately, most translations do not footnote this problem, so English Bible readers are usually unaware of it. So, what text should we choose and then translate? The original text Basically, textual criticism works by identifying the reading that best explains the origin of the others. This assumes that a scribe is likely to modify the original text, either accidentally or intentionally. From the three texts listed above, we prefer the first reading (“he was stricken to death”) as the original text.2See Jan de Waard, A Handbook on Isaiah (Winona Lake, IN: Eisenbrauns, 1997), 194–95; Dominique Barthélemy, Critique Textuelle de l’Ancien Testament. 2. Isaïe, Jérémie, Lamentations. Orbis Biblicus et Orientalis 50/2 (Göttingen: Vandenhoeck & Ruprecht, 1986), 397–99. The LXX attests both the verb “he was stricken” (נוגע) and the oldest form of the final word “to death” (למות). It is easier to believe that a scribe accidentally omitted a letter in copying, or that the letter was lost in a damaged margin of a manuscript than to think that a scribe intentionally modified the text. Since the LXX’s text also preserves the continuity of the masculine singular subject found in the rest of the song, this reading commends itself as what Isaiah most probably wrote. Get new articles and updates in your inbox. Leave this field empty if you're human: On the other hand, 1QIsaa shows an intermediate form of the text, a form which still preserves the original reading of the verb “he was stricken” (the reading most of our English translations assume anyway), but one which already shows the accidental omission of the single letter taw from “to death” (למות) resulting instead in “to them” (למו). This copyist error must have occurred very early in the transmission of the text for it now appears in the very wide base of witnesses shown above. If the error crept in early, we would expect exactly this situation. For its part, the MT continued to transmit the text it received, which then preserved an inferior vocalization for “strike” (נֶגַע) along with the corrupted final word “to them” (למו). Its reading “a blow belonged to them” must have been interpreted as referring to the people of Israel and eventually aided a national interpretation of the servant. Conclusion The textual decision here significantly changes the meaning of this song with respect to whether the servant dies and, in turn, who the servant is. Only the Hebrew parent text of the LXX preserves the servant’s death on account of the people’s transgression. Later scribal mistakes obscure the servant’s death and its purpose found in the original text. What’s at issue is ultimately something central to the New Testament’s witness about Jesus. What’s at issue, then, is ultimately something central to the New Testament’s witness about Jesus. One of the matters of chief importance that Paul received is that “Christ died for our sins according to the Scriptures” (1 Cor. 15:3). Paul, and those who transmitted early tradition about the Messiah’s death, seems to have been reading the version of Isaiah 53:8 argued for here (cf. Isa. 53:12) which explains how he arrived at this conclusion.Notes1See also the commentary by Joseph Blenkinsopp, Isaiah 40–55: A New Translation with Introduction and Commentary (New Haven: Yale University Press, 2002), 345, for a similar translation.2See Jan de Waard, A Handbook on Isaiah (Winona Lake, IN: Eisenbrauns, 1997), 194–95; Dominique Barthélemy, Critique Textuelle de l’Ancien Testament. 2. Isaïe, Jérémie, Lamentations. Orbis Biblicus et Orientalis 50/2 (Göttingen: Vandenhoeck & Ruprecht, 1986), 397–99.
Part 1: The Servant Sprinkles Many as Anointed Priest The first in our Easter series argues that the servant is not marred but rather anointed as a priest who sprinkles many. Peter J. GentryIsaiah’s fourth servant song is by far the most famous, not least because Christians have long read it as one of the greatest Old Testament prophecies about the heart of the Christian faith, the death of Jesus. In this Easter series, we are focusing on major textual problems in Isaiah 53 as a necessary step in identifying the suffering servant. Isaiah’s fourth servant song begins with an important prologue that not only sets the tone but also contains the seeds that will sprout into the rich theology of the rest of the song. Three lines in the center (Isa. 52:14–15) describe what in the servant’s role and work cause astonishment. But a series of textual problems require revision to the traditional translation of the servant’s disfigurement and instead highlight his anointing as a priest and thus his atonement for many nations. In the New Revised Standard Version (NRSV), the text reads as follows, with the key issues italicized: 13 See, my servant shall prosper; he shall be exalted and lifted up, and shall be very high.14 Just as there were many who were astonished at him —so marred was his appearance, beyond human semblance, and his form beyond that of mortals—15 so he shall startle many nations; kings shall shut their mouths because of him;for that which had not been told them they shall see, and that which they had not heard they shall contemplate. We will treat three crucial problems for the interpretation of the prologue: (1) the “just as… so… so…” structure governing 14–15; (2) the meaning of the verb in 15 and whether it should be translated “startled” or “sprinkled”; and (3) the meaning of the term in v. 14 translated “marred” by the NRSV (“his visage was so marred more than any man”). Each of these will help confirm the overall view of who this servant is and what he does.1Dominique Barthélemy has offered excellent solutions to these issues, but they are not widely known. I hope in what follows to build upon his proposals. See Dominique Barthélemy, Critique Textuelle de l’Ancien Testament, 2, Isaïe, Jérémie, Lamentations (Orbis Biblicus et Orientalis 50/2; Göttingen: Vandenhoeck & Ruprecht, 1986). 1. The Grammatical structure The first problem to be addressed is overall structure of this section of the prologue. Misunderstanding this has led to confusion on the other points. Properly understanding it is essential for solving the textual problems addressed below. The clause structures of vv. 14–15a are governed by the sequence of particles “just as… so… so…” (…כאשׁר… כן… כן). The following literal translation highlights these with italics: 14a just as many were astonished at you14b so his appearance was disfigured (or anointed) beyond human …15a so he will sprinkle (or startle) many nations These words correlate the two “so” affirmations about the servant with the “just as” affirmation of the reaction of the many to him. It is difficult, however, to make sense of the sequence of thought. The Geneva Bible, one of the most popular Protestant translations before the King James Version (KJV), led Christian intepreters in a new direction by understanding the first “so” clause as a parenthesis. This solution was then popularised by the KJV. Few modern translations, if any, faithfully present the structure in Hebrew. The NIV is representative of the problem: 14 Just as there were many who were appalled at him—his appearance was so disfigured beyond that of any manand his form marred beyond human likeness—15 so will he sprinkle many nations… Note how the NIV’s translation makes the first “so” clause a statemement about the degree to which he’s disfigured. This is problematic since this is not how the Hebrew word for “so” (כן) normally works. When the word is moved in translation, the English reader can no longer appreciate the original structure. The NIV is trying to solve a real interpretive problem here, but there is a better solution which we explain below. Neither Christian nor Jewish interpretations in the past adequately grappled with the grammatical structure. In short, neither Christian nor Jewish interpretations in the past adequately grappled with the grammatical structure in the text in the prologue. This structure will affect how we deal with the next two issues, the disputed words in v. 14b and v. 15a. We must choose an interpretation that honors this syntactic structure. We will begin by looking at the verb that means either “he will sprinkle” or “he will startle” (נזה) in v. 15. 2. Does the servant “startle” or “sprinkle” many nations? We will look at the full textual evidence before commenting on the Masoretic Text (MT), the dominant form of the Hebrew text behind our English Bibles. ReadingWitnessTextAmbiguousMasoretic TextSo he will sprinkle/startle many nations כֵּן יַזֶּה גּוֹיִם רַבִּים עָלָיו Dead Sea ScrollsSo he will sprinkle/startle many nationsכן יזה גואים רבים עליו“Astonish”LXXSo shall many nations be astonished at him οὕτως θαυμάσονται ἔθνη πολλὰ ἐπʼ αὐτῷ“Sprinkle”Theodotion, AquilaHe shall sprinkle… ῥαντίσει Symmachushe will reject… ἀποβάλλει Latin VulgateHe shall sprinkle many nations iste asperget gentes multas Syriac PeshittaThis one purifies many nations2One manuscript (11L4, Sinai, Monastery of St. Catherine, Syr MS 8, 9th–10th Century AD) has “thus” (ܗܟܢܐ) instead of “this” (ܗܢܐ). Whether this reading is influenced by MT or LXX is uncertain. ܗܢܐ ܡܕܟܐ ܥ̈ܡܡܐ ܣܓܝ̈ܐܐ Aramaic Targumso he shall sprinkle many nations כֵין יְבַדַר עַמְמִין סַגִיאִיןA survey of key witnesses to the verb in Isaiah 52:15 Leaving the LXX to one side for the moment, the other ancient translations of the Hebrew text such as Theodotion and the Vulgate understand the meaning of the verb as “sprinkle.” Symmachus’s “he will reject” probably shows he confused two letters in the Hebrew. What these translations show is that, the ancient translators did not find this verb difficult to understand. But the LXX translator did render it differently and this forces us to look more closely at the Hebrew original. Objections have been raised to interpreting the Hebrew verb as “sprinkle” (נזה) because of the unusual grammatical construction. The normal construction for the verb (used 23×) is to sprinkle a liquid (e.g., blood) on a person or thing (e.g., Lev 5:9, 8:11, 30) or before someone (Lev. 4:17, 14:16). In our text, however, no liquid is mentioned, and there is no preposition “upon” (על) before “nations” to mark the object being sprinkled. Get new articles and updates in your inbox. Leave this field empty if you're human: There are instances, however, where the liquid that is sprinkled is omitted if it can be assumed from the context (e.g., Exod. 29:21, Lev. 14:7, Num. 19:19). There are also cases where the object sprinkled is the direct object of the verb marked by the Hebrew direct object marker (Lev. 4:6, 17). Since Isaiah is poetry, this marker (את) is normally omitted. This probably explains the LXX translation. The unusual grammar of the verb may have caused the translator to render the verb “will be astonished” because he already had “will be appalled” in Isaiah 52:14. If so, the LXX was not translating a different Hebrew text here but rendering the same Hebrew word contextually (“as many will be appalled … so many will marvel”). If correct, then the “nations” is best understood as who the servant sprinkles and the liquid that’s sprinkled is assumed and is likely the blood of a sacrifice. In other words, the text is describing the servant’s priestly work in sprinkling the nations with the blood of a sacrifice. One of the remarkable implications of this is that it describes the servant as an Israelite priest who sprinkles the nations. One of the remarkable implications of this is that it describes the servant as an Israelite priest who sprinkles the nations. A number of scholars have found this solution unacceptable and have proposed to interpret the verb from a root related to an Arabic verb nazā that means “to jump,” translating the text as “he will cause people to jump,” which is a way of saying that he will startle them. But support for this proposal is weak because the verb in Arabic is not used of jumping as a result of being emotionally startled. The appeal to Arabic, therefore, is linguistically unsound. To suggest that Isaiah’s audience easily recognized an otherwise unknown verb instead of a common one is not plausible. Linguistically, then, “to sprinkle” has more to commend it if one can argue that it fits the context well. Showing how this reading does fit the context is what we address next. 3. Is the servant’s appearance “disfigured” or “anointed”? As argued above, verses 14–15a are syntactically bound together and the verb in v. 15 means “to sprinkle” as a priestly function. We must now revisit the meaning of the second disputed word, the noun (משׁחת) translated “marred” (KJV) or “disfigured” (NIV).3Barthélemy offers the most detailed and thorough treatment of the history of interpretation of this word and this will be conveniently summarized here. See D. Barthélemy, Critique Textuelle de l’Ancien Testament, 2:385–386. Thankfully, all our textual witnesses attest the same text. RelatedA New Series on Isaiah’s Suffering ServantJohn D. MeadeRecovering the Resurrection in Isaiah 53: Textual Criticism and EasterJohn D. MeadePart 3: The Servant’s Burial according to the ScripturesPeter J. Gentry There are two possibilities for understanding the Hebrew noun in the Masoretic Text: a noun derived from (1) the root “to ruin” (שׁחת), or (2) the root “to anoint” (משׁח). The meaning is either “ruining” or “anointing” depending which of these two is adopted. Thus two translations are possible. Either “his appearance is anointed beyond that of men” or “his appearance is ruined beyond that of men.” Note that in the latter translation, “his appearance is ruined,” the word “ruined” is passive. This involves changing the vowels in the Masoretic Text where the form of the word requires an active interpretation: “his appearance is a ruining beyond that of men. This active interpretation doesn’t make sense of the text we have. Almost all interpreters from ancient times to the present have connected the word with the first of these two roots (“to ruin”). Nonetheless, in the Great Isaiah Scroll (1QIsaa) dating around 100 BC, the reading is actually “I anointed” (משׁחתי) which may be a simplification of the reading in Masoretic Text, but also clearly shows that this scribe interpreted the word as being from the second root (“to anoint”). This scribe’s instinct was right for the following reasons. The noun “anointing” (מִשְׁחָה) is well attested in the biblical text (23×) whereas a noun “ruination” (מִשְׁחָת) is otherwise unknown in the Hebrew Scriptures. This fits with other priestly anointings in the Old Testament. Regulations concerning a special anointing oil devoted strictly for particular occasions and persons and not for common use is found in Exodus 30:30–33. The anointing of the high priest with this oil to install him into his office set him above his fellow priests (Lev. 21:10) and the anointing of the king to indicate his divine election for this office set him above his fellow Israelites (Psa. 45:8). Such parallels show, then, that an expression “an anointing above that of men” is natural in biblical Hebrew while an expression “a destruction above that of men” is otherwise unattested. This reinforces the exalted stature of Isaiah’s servant. If this reading is correct, then several significant pieces of the servant’s identity fall neatly into place. It shows his high office Parallel to “his appearance” (מַרְאֵהוּ) is “his form” (תֹּאֲרוֹ). This second term is similar to our English expression “he cut a fine figure.” This is not just indicating that he may be attractive, but may also suggest his rank and social status. In Isaiah 53:2 this same term is found: “He had no form or majesty to attract us to him, nothing in his appearance that we should desire him.” This means that the servant does not have a royal bearing in his appearance. He does not “cut a fine figure” in such a way that people would say, “We want him for a king!” (This stands in contrast to Israel’s choice of Saul in 1 Samuel 9:1–2, 10:23–24 where Saul’s physique is precisely what encourages Israel to make him king.) Thus Isaiah is here describing the dignity and social status of a high office like that of the high priest or king whose entry into office is symbolized by an anointing. Isaiah is describing the dignity of a high priest or king whose entry into office is symbolized by an anointing. It fits the Old Testament pattern The meaning “anointing” suits the progression of thought in the two “so” clauses of vv. 14–15. According to Leviticus, a priest can only sprinkle after he’s been anointed: The priest who is anointed and ordained to succeed his father as high priest is to make atonement (Lev. 16:32; NIV). The meaning “anointing” makes excellent sense of the sequence in this text. The servant sprinkles because he has been anointed. As we have already seen, the symbolism of anointing indicates that the high priest was exalted above his fellow Israelites. This anointing qualifies him to atone for the nation. In the same way in our text, the servant is exalted above all humans and so atones for all the nations. This interpretation also explains the exaltation of the servant described in v. 13 better than any other proposal.4John Goldingay adds significant support: “[t]he observation that, following his desolation, the servant is superhumanly anointed fits with the description of his superhuman exaltation in v. 13. The reference to anointing (mišḥat) parallels the account of David’s anointing as a person good in appearance and a man of [good] looks (1 Sam. 16:12–13, 18; cf. *Grimm/Dittert). It also again parallels Ps. 89:19–20, 50–51 [20–21, 51–52], where Yhwh’s ‘servant’ David is ‘anointed’ as well as ‘exalted’ and his successor as Yhwh’s ‘servant’ and ‘anointed’ is taunted by ‘many’ peoples. Further, the anointing of this servant as if he were a king parallels the designation of Cyrus as Yhwh’s anointed in 45.1. Tg was not so outlandish in adding reference to Yhwh’s anointing in 52.13 as at 42.1.” John Goldingay, The Message of Isaiah 40–55: A Literary-Theological Commentary (London: T&T Clark, 2005), 491. It makes best sense of the structure The resulting meaning from understanding the term as “anointing” best honors the “just as… so… so…” structure that has tripped up translators in the past. The logic can best be appreciated by comparing the structure in Exodus 1:12: just as they [the Egyptians] mistreated them [the Israelites], so they increased and so they spread. The idea is that despite the Egyptians mistreatment, the Israelites increased. So here, the anointing and sprinkling of the Servant is in contrast to the astonishment many feel when looking at him. Modifying the NRSV, the result would be something like this: 14 Just as there were many who were astonished at him, so his anointing was beyond that of men, and his form beyond that of mortals,15 so he shall sprinkle many nations The upshot of all this is that Isaiah is not saying that the people are shocked because of how disfigured he is. Rather, the people’s shock is proportional to the servant’s incredible anointing and his work of sprinkling many nations. Although this proposal may seem novel, Dominique Barthélemy discusses five Jewish interpreters from the 12th to 19th centuries who adopted “anointing” as the best interpretation, and two Christian interpreters from the 16th to 17th centuries who held such a view.5D. Barthélemy, Critique Textuelle de l’Ancien Testament, 2:388-390. It is noteworthy that the interpretation proposed by Barthélemy and developed here is also that expounded recently by John Goldingay, The Message of Isaiah 40–55: A Literary-Theological Commentary, 490–492, although no reference is made to Barthélemy and discussion of grammatical, lexical, and textual issues is extremely limited (these, however, are not the focus of his work). This is also the understanding of the scribe of the Great Isaiah Scroll from Qumran as we saw earlier. There is good precedent, then, for this interpretation. Conclusion Scholars and Bible translators have long had to face the difficulties in the prologue to Isaiah’s fourth servant song. English translations have typically solved these problems by presenting the servant’s shocking appearance as the reason for the people’s astonishment. But a comprehensive look at the issues results in a more cohesive portrait of the servant, one that anticipates key themes throughout the rest of the song. It shows that the people’s astonishment is contrasted with his exalted status as an anointed priest who, surprisingly, sprinkles the nations. This idea of Jesus’ high priestly work is picked up repeatedly by the New Testament writers. This idea of Jesus’ high priestly work is, of course, picked up repeatedly by the New Testament writers. The writer of Hebrews, for example, tells us that Jesus is “the mediator of a new covenant” whose “sprinkled blood” speaks a better word (Heb. 12:24). Because of his work, we are exhorted to “draw near with a true heart in full assurance of faith, with our hearts sprinkled clean from an evil conscience” (Heb. 10:22). The original version of this article cited the KJV at the beginning when the NRSV was meant. This article is adapted from the author’s longer treatment in the Southern Baptist Journal of Theology. Notes1Dominique Barthélemy has offered excellent solutions to these issues, but they are not widely known. I hope in what follows to build upon his proposals. See Dominique Barthélemy, Critique Textuelle de l’Ancien Testament, 2, Isaïe, Jérémie, Lamentations (Orbis Biblicus et Orientalis 50/2; Göttingen: Vandenhoeck & Ruprecht, 1986).2One manuscript (11L4, Sinai, Monastery of St. Catherine, Syr MS 8, 9th–10th Century AD) has “thus” (ܗܟܢܐ) instead of “this” (ܗܢܐ). Whether this reading is influenced by MT or LXX is uncertain.3Barthélemy offers the most detailed and thorough treatment of the history of interpretation of this word and this will be conveniently summarized here. See D. Barthélemy, Critique Textuelle de l’Ancien Testament, 2:385–386.4John Goldingay adds significant support: “[t]he observation that, following his desolation, the servant is superhumanly anointed fits with the description of his superhuman exaltation in v. 13. The reference to anointing (mišḥat) parallels the account of David’s anointing as a person good in appearance and a man of [good] looks (1 Sam. 16:12–13, 18; cf. *Grimm/Dittert). It also again parallels Ps. 89:19–20, 50–51 [20–21, 51–52], where Yhwh’s ‘servant’ David is ‘anointed’ as well as ‘exalted’ and his successor as Yhwh’s ‘servant’ and ‘anointed’ is taunted by ‘many’ peoples. Further, the anointing of this servant as if he were a king parallels the designation of Cyrus as Yhwh’s anointed in 45.1. Tg was not so outlandish in adding reference to Yhwh’s anointing in 52.13 as at 42.1.” John Goldingay, The Message of Isaiah 40–55: A Literary-Theological Commentary (London: T&T Clark, 2005), 491.5D. Barthélemy, Critique Textuelle de l’Ancien Testament, 2:388-390. It is noteworthy that the interpretation proposed by Barthélemy and developed here is also that expounded recently by John Goldingay, The Message of Isaiah 40–55: A Literary-Theological Commentary, 490–492, although no reference is made to Barthélemy and discussion of grammatical, lexical, and textual issues is extremely limited (these, however, are not the focus of his work).
A New Series on Isaiah’s Suffering Servant Our Easter series addresses a set of textual problems that are crucial to the identity of the suffering servant in Isaiah 53. John D. MeadeAs Easter approaches, many Christians will be remembering the gospel of Christ, that he died for our sins, was buried, and was raised “according to the Scriptures” (1 Cor. 15:3–4). No doubt, one scripture that many will read during holy week will be Isaiah 52:13–53:12, also known as the fourth servant song. This passage is a crucial text for understanding the events that took place in Jerusalem some 2,000 years ago. Numerous questions surround this famous text, the most important of which is the identity of the servant. Four servant songs Isaiah 52:13–53:12 is the last and by far the most famous of Isaiah’s four servant songs. In all four, the vexing question is the identity of the servant. In the first song (Isa. 42:1–9), Isaiah presents the nation of Israel as the servant. In the second (Isa. 49:1–13), at first, Israel is identified with the servant (49:3) but then, shockingly, the servant is tasked to turn Jacob back to the Lord and to gather Israel to him (49:5). The servant must be one who can both embody the nation and be distinct from it at the same time, as a king who represents his people completely. The third and fourth servant songs (50:4–9; 52:13–53:12) read straightforwardly, if the servant is the future king, David’s awaited descendant. Thus, the last three of the servant songs can be read as speaking about the one king in relationship to the nation: he embodies and represents the nation totally, but he must also now intervene and save the nation. The servant’s identity But not all readers arrive at this conclusion and interpretation has been varied. The identity of the servant in Isaiah 52:13–53:12 has been debated from the beginning. In Acts 8:26–35, the Ethiopian eunuch is reading the prophet Isaiah, but he does not know how to interpret Isaiah 53:7–8. The eunuch asks Philip to help him understand, “I ask you, concerning whom does the prophet say this? Concerning himself or concerning another?” (Acts 8:34). Philip begins from this scripture to preach Jesus to him. The identity of the servant has been debated from the beginning. Today, debate over the identity of the Servant continues to divide interpreters. Jewish interpreters typically say the servant is the nation of Israel. Most Christian interpreters claim the servant is Jesus the Messiah, while some commentators continue to hold that the servant is the prophet. Have most Christians been wrong for 2,000 years in interpreting the servant as Jesus? To answer this, we need to ask a prior question about the textual transmission of Isaiah 52:13–53:12. RelatedRecovering the Resurrection in Isaiah 53: Textual Criticism and EasterJohn D. MeadePart 3: The Servant’s Burial according to the ScripturesPeter J. GentryPart 4: Who Does the Servant Intercede For?John D. Meade The text The more fundamental question is what the text of the song is. English Bible readers may not be aware that there are several important problems in the textual history of this passage that affect translation and therefore interpretation. In fact, our major English versions disagree on which manuscripts preserve the original text, and therefore, they disagree at several key points within this passage. And these are no minor differences. They center on the servant’s identity and work, his suffering and death, his burial, his resurrection, and his bearing of sins and intervention at the rebellions of the many. Indeed, the problems cluster around the very tenets of the Gospel that Paul says he received as of chief importance (1 Cor. 15:3–5). A new series Over the weeks leading up to Easter, the Text & Canon Institute will be addressing some of the most important textual problems in the fourth servant song. Dr. Peter Gentry, Dr. Anthony Ferguson, and I will guide readers through these difficulties. We will treat these five textual issues: Does the servant startle the nations because he is disfigured or sprinkle them after being anointed? (Isa. 52:14–15) Is the servant stricken for the people’s rebellion, or are they? (Isa. 53:8) Is the servant’s death or his tomb that is with the rich? (Isa. 53:9) Who and what does the servant intercede for? (Isa. 53:12) Is the resurrection of the servant anticipated in what he sees? (Isa. 53:11) We want to help readers see the problems in the textual history of this passage by comparing English translations and commentaries. When readers see the analysis of difficulties in our primary sources, they can appreciate how textual criticism aims to determine the probable, original text and how those decisions influence Bible translation at the most fundamental level. Since texts were copied by hand, those hands sometimes changed the text when copying it. Many of these modifications are insignificant, but in Isaiah 52:13–53:12, there are important differences to the text we would do well to note and form opinions about. Join us this Easter season for a series of articles on the intersection between textual criticism and Bible translation as we give a deep reading of one of the most significant passages that informs us about the person and work of Christ. Be sure to subscribe to get the new articles in the series in your inbox. Get new articles and updates in your inbox. Leave this field empty if you're human:
Who Really Killed Goliath? Knowledge of scribal mistakes may provide a better solution to the historical puzzle of who killed Goliath in 2 Samuel 21:19. Kaspars OzoliņšOne of the more puzzling verses in the Old Testament is 2 Samuel 21:19. This verse is situated in the context of a brief epilogue to David’s reign, after his return from fleeing from his son Absalom (2 Sam 15–19). Here’s the verse in the ESV, “And there was again war with the Philistines at Gob, and Elhanan the son of Jaare-oregim, the Bethlehemite, struck down Goliath the Gittite, the shaft of whose spear was like a weaver’s beam.” On the face of it, this verse seems to flatly contradict the famous story of David killing Goliath recounted in 1 Samuel 17. Further Problems Things get even more confusing when we examine the parallel passage in 1 Chronicles 20:5 (much of Samuel-Kings is paralleled in the book of Chronicles): “And there was again war with the Philistines, and Elhanan the son of Jair struck down Lahmi the brother of Goliath the Gittite, the shaft of whose spear was like a weaver’s beam.” This verse, quite distinctly, claims that it was Goliath’s brother who was killed by Elhanan. English Bible footnotes sometimes hint that the text of 1 Chronicles may solve the problem. The ESV note at 2 Samuel 21:19 reads, “Contrast 1 Chronicles 20:5, which may preserve the original reading.” In this case, the full solution is probably more complex and involves scribes making mistakes in both verses. Unfortunately, the Dead Sea Scrolls don’t offer us much help, since there is a gap at exactly this verse in 1QSam. Likewise, the versions don’t seem to offer us any particularly helpful insights, since they broadly agree with each respective verse in the Hebrew Masoretic tradition. In the history of scholarship, the tendency has been for conservative scholars to claim that Chronicles has the original text here (as in the ESV note), with the understanding that Samuel’s text has somehow been corrupted over time. By contrast, non-confessional scholars view the verse in 2 Samuel as retaining the original wording, whereas Chronicles is seen as having been deliberately altered in order to “harmonize” the contradiction with the story of David in 1 Samuel 17. The basic idea is that the oldest tradition is assumed to have preserved the story of an otherwise unknown Elhanan who killed Goliath, while later traditions deliberately attributed this heroic deed to David to shore up the reputation of Israel’s greatest king. A Closer Look at the Text When we juxtapose the Hebrew words in the problematic portions of the two verses side-by-side, interesting features emerge. To appreciate this, we can set the English to follow the Hebrew word order of verb-subject-object (color coded as blue-yellow-red). 2 Sam. 21:19And (he) struckElhanan son ofJaare-oregimthe Beth-lehemite —Goliath the Gittite wayyakelḥānān benyaʿrê ͗ōrĕḡîmbêthallaḥmî ͗ētgolyat haggittî1 Chron. 20:5And (he) struckElhanan son ofJaur —Lahmibrother ofGoliath the Gittite wayyakelḥānān benyāʿûr ͗ētlaḥmî ͗ăḥîgolyat haggittîThe key differences between the two verses are marked in bold The two main problems that require attention are (1) the identity of the Israelite hero and (2) the identity of the Philistine giant. The Hero’s Name The first problem is the easier one to solve. Notice that the family (or patronymic) name of the hero, Elhanan, differs slightly in both verses. In 1 Chronicles 20:5 he is Jaur but in 2 Samuel 21:19 he is Jaare-oregim.1There is more to say about the Jaare/Jaur/Jair name but the textual history is too much to get into for this article. The word “oregim” ( ͗ōrĕḡîm) actually means “weavers” and it is found at the end of both verses as a description of the spear carried by the giant whom Elhanan slew: “…the shaft of whose spear was like a weaver’s ( ͗ōrĕḡîm) beam.” For this and other reasons, it is likely that Elhanan’s father (or ancestor) did not bear such a compound name and that this extra ͗ōrĕḡîm has crept into the text of 2 Samuel 21:19 from the end of the verse through a series of scribal mistakes. The Giant’s Name The real difficulty, as mentioned above, is the identity of the Philistine giant. Because of the way the Hebrew text is laid out, this problem partly intersects with the issue we just addressed: the identity of Elhanan. In Samuel, Elhanan is identified as a Bethlehemite, but not in Chronicles. Conversely, in Chronicles, the giant’s name is given as “Lahmi,” whereas in Samuel, this name is missing. Notice further that these two features occur in precisely the same position in the Hebrew text, and that both words look very similar: Chronicles has “Lahmi” laḥmî (presumably the giant’s name), while Samuel has “[Beth-]lehemite” [bêt] hallaḥmî. The longer form is what’s called a “gentilic,” a place name assigned to an individual (like “American” or “European”). In forms of this type of word, the second half normally bears the Hebrew definite article ha-. This leaves us with three possibilities: (1) “Lahmi”really was the name of the Philistine giant, and therefore “Bethlehemite”has later crept into the text of Samuel; (2) Elhanan really was a Bethlehemite, and therefore we have a scribal error at Chronicles (i.e., “Lahmi” wasn’t the name of the Philistine giant); or (3) both were true: Elhanan was a Bethlehemite, and “Lahmi” really was the name of the giant he slew. One way to decide between these three options is to consider whether we have any evidence elsewhere in the Hebrew Bible about the identity of the Israelite hero and/or the Philistine giant. It turns out that in another list of David’s mighty men in 2 Samuel 23 (and in its parallel in 1 Chronicles 11), the same Elhanan shows up, and the text there explicitly mentions that he comes from Bethlehem. This is therefore very likely the same Elhanan as our giant-slaying hero. (Nowhere else in the Hebrew Bible do we find the name Elhanan.) If Elhanan really was a Bethlehemite, then what should we make of the Philistine giant’s name “Lahmi”? Let’s recall a few things about this name: (1) it only occurs in the Chronicles parallel; (2) it occurs in precisely the same place that the word “[Beth-]lehemite” is found in the Samuel text; and (3) it looks very similar to it in Hebrew (הלחמי vs. לחמי), differing in only one letter. The two even sound similar (hallaḥmî vs. laḥmî). On balance, these three factors (and others) should make us seriously consider the possibility that the name “Lahmi” has accidentally entered the text of Chronicles as a scribal confusion of the second half of the name “Bethlehemite.” One Last Problem With all this, however, the apparent contradiction still remains in place. Elhanan the Bethlehemite slew Goliath. A couple of clarifications should be given at this point. Notice from the chart that the word ͗ēt (which has no equivalent in English) is a way that Biblical Hebrew marks the direct object (the word that receives the action of a verb: “John hit the ball”). In our texts, the word ͗ēt precedes the name of the individual Elhanan killed. Although it occurs in each verse, its placement differs. The ͗ēt of 2 Samuel 21:19 is paralleled by “brother of” ͗ăḥî in Chronicles. Visually, both words look very similar in Hebrew (את vs. אחי), even though they have very different meanings. Conversely, the direct object marker ( ͗ēt) of 1 Chronicles 20:5 is paralleled by the very similar-sounding word for “house of” (bêt), which occurs as the first half of the gentilic “Beth-[lehemite]” discussed earlier. RelatedDoes Isaiah Predict the Virgin Birth?Peter J. GentryThe Bible and Slavery in Colonial AmericaMark A. NollHow Bible Software Solves Differences in Versification for YouRick Brannan When you think about it, the same three factors mentioned above are at play here: (1) “brother of” ( ͗ăḥî) is found only in Chronicles, whereas we find the direct object marker ( ͗ēt) in Samuel; (2) both words occur in the same place in the text when we align the two verses; (3) both words strikingly resemble each other visually. This same kind of complementary distribution, where two similar-looking words occur at the same point in the text, should make us suspect that one of these words is a scribal alteration of the other. So, was the direct object marker ͗ēt deliberately changed to “brother of” ͗ăḥî in Chronicles by a scribe in order to avoid an embarrassing contradiction? Or, instead, was this simply an accidental visual oversight, in which a scribe misread “brother of” ͗ăḥî (אחי) as the direct object marker ͗ēt (את) in Samuel? We ought to favor the second explanation for at least two reasons: (1) visually similar words are most naturally explained as accidental (not deliberate) scribal errors; (2) scribes who copied Samuel apparently were not bothered by the resulting contradiction! Putting It All Together A translation of the text of 2 Samuel 21:19, highlighting the suggested changes, would read as follows: “And there was again war with the Philistines at Gob, and Elhanan the son of Yaur, the Bethlehemite, struck down the brother of Goliath the Gittite, the shaft of whose spear was like a weaver’s beam.” We can now put all the steps together, for both verses, and show the progression in the following table. 2 Samuel 21:191 Chronicles 20:5Original…and Elhanan the son of Jaur, the Bethlehemite, struck down the brother of Goliath the Gittite, the shaft of whose spear was like a weaver’s beamStep 1An extra oregim appears after “Yaur” in 2 Sam.…and Elhanan the son of Jaare-oregim, the Bethlehemite, struck down the brother of Goliath the Gittite, the shaft of whose spear was like a weaver’s (oregim) beamStep 2“brother of” is misread in 2 Sam. and “Bethlehemite” is misread in 1 Chron.…and Elhanan the son of Jaare-oregim, the Bethlehemite, struck down Goliath the Gittite, the shaft of whose spear was like a weaver’s beam…and Elhanan the son of Jaur, struck down Lahmi the brother of Goliath the Gittite, the shaft of whose spear was like a weaver’s beam Lessons Learned As can be seen, the textual issues involved are complex. Given the arguments outlined above, however, one plausible historical reconstruction is that Elhanan the Bethlehemite actually killed the brother of Goliath, whose name we aren’t given. That this giant was unnamed is not unusual, since the very next mini episode in 2 Samuel 21:20–21 mentions another giant (this time slain by Jonathan the son of Shimei), who is likewise left unnamed in the narrative. One should always pay attention to text-critical issues before resorting to other types of higher criticism. Finally, we can draw several important lessons from this solution. First, one should always pay attention to text-critical issues (what is sometimes called lower criticism) before resorting to other types of higher criticism (such as the claim that we are dealing here with two different, and contradictory, sources or traditions). Second, only in limited cases did scribes make deliberate changes when copying the text in front of them, so we should be cautious before making such claims unless there is very good evidence. As can be seen from this example, even minor differences in wording and spelling can sometimes make a big difference. The way we engage with and approach text-critical details in Holy Scripture is important and ought to be characterized by a degree of editorial constraint, in proportion to the evidence we actually possess. The reconstruction proposed here is an attempt to provide a possible solution to a significant issue. This article is a summary of the author’s much more detailed argument published in the journal Vetus Testamentum.Notes1There is more to say about the Jaare/Jaur/Jair name but the textual history is too much to get into for this article.
How Much Can the Most Famous Dead Sea Scroll Prove? The Great Isaiah Scroll is a crucial piece of the Old Testament puzzle, but it doesn’t give us the whole picture. Anthony FergusonThe Dead Sea Scrolls are famous. Very famous. Unlike other archeological discoveries like Hezekiah’s Siloam Tunnel inscription in Jerusalem or the discovery of the Elephantine Papyri in Egypt, the term “Dead Sea Scrolls” is a household phrase that can draw crowds to museums unlike any cuneiform tablet. Almost everyone has some knowledge of this discovery and significance, and rightly so. The most famous—and substantial—of these biblical manuscripts is, without a doubt, the Great Isaiah Scroll (a manuscript scholars designate as 1QIsaa). The factors that justify this manuscript’s notoriety and fame include the timing of its discovery, its size, its contents, and its closeness to the Hebrew text behind our English Bibles known as the Masoretic Text (MT). Given these facts, 1QIsaa furnishes a solid starting point for one’s study of these intriguing texts from the Dead Sea. But these facts sometimes lead one to unhelpful conclusions about the biblical texts from the Dead Sea, if 1QIsaa is all we know or we assume that every biblical manuscript from the Dead Sea is like it. In this article, we’ll survey the importance of this manuscript while also nuancing its impact on our understanding of the biblical text as preserved in the Dead Sea Scrolls. Its Claim to Fame The timing of the manuscript’s discovery rightly contributed to its fame since it belonged to the first batch of manuscripts discovered in early 1947. When Bedouin first journeyed into Cave 1 to explore the sound of breaking jars, they retrieved three or four manuscripts wrapped in cloth from a jar. One of these manuscripts was the now famous 1QIsaa. This discovery encouraged the Bedouin and scholars to further explore this region so that over the next fifteen years roughly 1000 manuscripts would be discovered. The cascade effect of this initial discovery was truly immense. Unlike most manuscripts from the Judean Desert, 1QIsaa is preserved almost in its entirety. This is due to its being stored in a jar covered with pitch. By God’s grace, it sat for millennia in a sort of sealed time capsule. Because this manuscript is well preserved, the various problems associated with fragmentary manuscripts like calculating column heights and hypothesizing about what words have been lost to the harshness of the desert are almost nonexistent when studying 1QIsaa. One of the remarkable features of the Great Isaiah Scroll is how well it’s preserved, including the very beginning (right) and end (left) of the scroll. Photo from Wikipedia The very first words and the last words of the manuscript are all preserved, and the text consists of only a few holes (i.e., lacunae). Stitching holes exist in the right-hand margin of column 1 which indicates that leather once existed to the right of the first words of Isaiah. There was probably once a handle sheet to the right of the first column to protect the text of this manuscript. The handle sheet has done its job since, although it has since been lost to time, the beginning of the document remains. The contents of this manuscript have also brought it a level of notoriety since it preserves the text of Isaiah, one of the more famous books of the Old Testament. This book appears to have been quite popular among the works found in the library of the Dead Sea since many copies of Isaiah were found there. The New Testament quotations of Isaiah suggest the same as does the amount of attention paid to this important book by contemporary scholars. Christians sometimes refer to Isaiah as the fifth Gospel because of how much it tells about the coming hope of the Messiah. Although Bedouin discovered other texts alongside 1QIsaa such as a commentary to Habakkuk, 1QIsaa became more popular. This may be, since it was a biblical text, not a commentary, but it is also likely due to the fact that it concerned Isaiah. RelatedAppreciating the Diverse Evidence from the Dead Sea ScrollsAnthony FergusonRecovering the Resurrection in Isaiah 53: Textual Criticism and EasterJohn D. MeadeWhat We Know about the People behind the Dead Sea ScrollsAnthony Ferguson The popularity of this manuscript is also due to its relationship to the Masoretic Text. The consensus among the first generation of scholars who analyzed this text was that 1QIsaa preserved a popular version of the Masoretic Text. Since the analysis of these scholars, the trend has shifted. Whereas the original scholars who studied 1QIsaa noted its similarities to the Masoretic Text, current scholars tend to highlight its differences. These differences are real, but often minor. Emmanuel Tov, for example, indicates that 1QIsaa is non-aligned but regarding minor details such as a different approach to spelling.1Emanuel Tov, “A Didactic and Gradual Approach toward the Biblical DSS,” in Textual Criticism of the Hebrew Bible, Qumran, Septuagint: Collected Essays, Volume 3 Vetus Testamentum, Supplements (Brill: Leiden, 2015), 303. (The term non-aligned refers to texts that are inconsistent in their agreement with the Septuagint, MT, and Samaritan Pentateuch while preserving unique readings).2Emanuel Tov, “Groups of Biblical Texts Found at Qumran,” in Time to Prepare the Way in the Wilderness: Papers on the Qumran Scrolls, ed. Devorah Dimant and Lawrence H. Schiffman, Studies on the Texts of the Desert of Judah 16 (Leiden: Brill, 1995), 98. We could synthesize the conclusions of scholars this way: early scholars tended to emphasize the similarities between 1QIsaa and the Masoretic Text. The trend, now, is to emphasize the differences. Regardless of one’s emphasis, when one removes the minor differences such as spellings, the text of 1QIsaa is quite close to the Masoretic Text, and this feature is a major reason for its notoriety. The Limits of 1QIsaa to our Understanding of the Biblical Text 1QIsaa contributes immensely to our understanding of the Old Testament text. On the one hand, it is strong indirect evidence to the antiquity of the Masoretic Text. That is, in the cases where 1QIsaa and the Masoretic Text disagree, scholars most often view the reading of the Masoretic Text as more original, and this is for good reason, since most of the differences preserved in 1QIsaa appear to derive from common scribal tendency or from scribal error. Thus, although the Masoretic Text as we know it is best represented by medieval codices dating to around 1000 AD, the parent text of 1QIsaa appears to be a text close to these medieval codices. Get new articles and updates in your inbox. Leave this field empty if you're human: This is where Christian scholars and apologists can make a mistake. 1QIsaa is the most popular biblical Dead Sea Scroll and for good reason. It was one of the first manuscripts discovered and it preserves almost all of Isaiah in a form close to the Masoretic Text. All of this is true. Based on this information, it is tempting to assume that just because 1QIsaa aligns closely to the Masoretic Text, we can therefore be confident that our Old Testament text is a reliable copy of the original. I agree that we should be confident, very confident in this fact, but the problem is that 1QIsaa is not sufficient proof, and this is for a few reasons. First, 1QIsaa is a copy only of Isaiah, not the entire Old Testament. Thus, we can’t conclude that 1QIsaa proves that the entire Old Testament has been copied carefully. It is only a copy of Isaiah. Extrapolating from this one manuscript of this one book to the full copying of the entire Old Testament is dangerous. Second, scholars date 1QIsaa to the second century BC, which makes it our oldest copy of this book. Yet, it is still hundreds of years removed from the original copy of Isaiah. As important as 1QIsaa is, it doesn’t completely close the gap for us. Third, although 1QIsaa remains close to the Masoretic Text, other ancient texts are further removed. There is a spectrum of how close the Dead Sea Scrolls align with the Masoretic Text: some are almost identical while other diverge more significantly. My point is simple: since the Dead Sea Scrolls represent a spectrum of more or less agreement with the Masoretic Text, the Great Isaiah Scroll does not represent the entire picture. One (Important) Piece of the Puzzle 1QIsaa does not single-handedly prove that the Old Testament has been carefully copied from antiquity. Its contribution is still important, but less extensive. In short, I would say that 1QIsaa is a popular version of a text very close to the Masoretic Text, and thus, it attests to the antiquity of the Masoretic Text of Isaiah long before our earliest copies from the Middle Ages. The copies we have of the Old Testament are a reliable guide to the original, but this conclusion depends on more than one very famous manuscript. The copies we have of the Old Testament are a reliable guide to the original, but this conclusion depends on more than one very famous manuscript. It depends on a variety of data such as the practice of textual criticism, the study of manuscripts, scribal habits, various early translations, the nature of a covenant, and the evidence from the Dead Sea Scrolls. This conclusion also depends on our view of God and what the Bible attests about itself. As we do textual criticism, let’s not forget that the Old Testament testifies to the God who sovereignly controls all things. We make best sense of the biblical data when we carefully consider the evidence while remembering that the evidence we have is not by accident, but according to God’s plan.Notes1Emanuel Tov, “A Didactic and Gradual Approach toward the Biblical DSS,” in Textual Criticism of the Hebrew Bible, Qumran, Septuagint: Collected Essays, Volume 3 Vetus Testamentum, Supplements (Brill: Leiden, 2015), 303.2Emanuel Tov, “Groups of Biblical Texts Found at Qumran,” in Time to Prepare the Way in the Wilderness: Papers on the Qumran Scrolls, ed. Devorah Dimant and Lawrence H. Schiffman, Studies on the Texts of the Desert of Judah 16 (Leiden: Brill, 1995), 98.
Five Decisions Every Bible Translator Must Make Knowing the hard decisions Bible translators face inspires gratitude for our Bibles and encourages us to read them. Peter J. GurryA Bible translation is a major undertaking. A good one can take more than ten years to finish even when a full team is involved. Besides the translators, there is often a team of editors, proofreaders, publishers, printers, marketers, and more. Along the way, a translation committee has thousands of decisions to make, many of which go beyond the most obvious one of deciding how to translate any given word or phrase. Here are five decisions that every translator has to decide—whether their readers know it or not. 1. Who’s the audience? The first decision is arguably the most important because it will determine many other decisions along the way. The first way to define a translation’s audience is, of course, based on what’s called the target language. A translation into German will have a German-speaking audience; a French translation will have French speakers, etc. Though target language is the most obvious form of this question, there is much more to it. Since some language groups like English are so vast and have so many translations already, translation teams often aim their work at a narrower set of readers. RelatedHow Was the Divine Name Translated in the Reformation? Part 4Andrew CaseA Newly Digitized Bible Reveals the Origins of the King James VersionTimothy BergBible Translations Are for PeopleDrew Maust American Bible readers are sometimes surprised to learn that major English translations usually result in an American edition and a separate British edition that has British spelling and, in some cases, different word choices. The ESV, for example, has both an Anglicized version and an American version. There is now even a Catholic edition that includes the Apocrypha. In other cases, the choice is not about geography or theology, but reading level. The original NIV was designed to be especially readable, and so was designed for a seventh-grade reading level. But even that audience could be narrowed. That’s why it was revised in a special edition published in 1996 called the New International Reader’s Version or NIrV. It was aimed at a third-grade reading level with the hope of reaching children and readers whose first language isn’t English. This was accomplished by using smaller words and shorter sentences whenever possible. Psalm 23:2 was changed from the NIV’s “He makes me lie down in green pastures” to “He lets me lie down in fields of green grass.” The Lord’s prayer became “Our Father in heaven, may your name be honored. May your kingdom come. May what you want to happen be done on earth as it is done in heaven” (Matt. 6:9–10). These small translation choices add up, but they are all the result of a much larger decision about who the audience is. It’s a choice every translator needs to make. 2. Will it be a fresh translation or a revision? The example of the NIrV illustrates another question that translators have to answer and that is whether their work will be a new translation from the original languages or will instead use the originals to revise an existing translation. The original NIV, for example, was a fresh translation. It was not based on any prior English Bible. The NIrV, as we just saw, started with the NIV and then revised it. It was revised again in 2014. English Bible readers are often surprised to learn that it’s this second approach that is by far the more common one historically. Completely new translations are a relative rarity. The reason is obvious to translators but probably not to most readers. It’s simple: translating the entire Bible is a massive undertaking. Starting from scratch increases the work exponentially. It’s much faster to start from something and change it than to work with nothing. Besides that, revising a well-known translation often gives the new one a much-needed boost in respect and authority. The translators of the most famous English Bible—the King James—knew this well. That’s why in the original preface, they make clear that their work is a revision of previous English Bibles. Their expressed goal was not to “make a new translation, nor yet to make of a bad one a good one,” but only “to make a good one better, or out of many good ones, one principal good one.” That tradition of revision continues right up to the present. A special insert in the Chicago Tribune on May 22, 1881 printed the entire New Testament of the Revised Version. It took 92 compositors working 12 hours to produce all 118,000 words from a telegram from New York City. In 1885, the King James itself was finally revised for the first time since 1611 in a major translation.1Dates given in this section are the date when the entire Bible was first published. In many cases, the publication of the New Testament preceded the Old by several years. The result was published to great fanfare as the Revised Version. This was then further revised by a team of scholars in North America and published as the American Standard Version in 1901. The Revised Version was again revised in 1952 as the Revised Standard Version and that, in turn, became the New Revised Standard Version of 1990. Even now, an update to the NRSV is set for release in 2022. A separate translation team went back to the Revised Standard Version in 2001, producing the English Standard Version. Even this doesn’t tell the full story of revisions in the KJV lineage. Objections to translation choices in the RSV (like “young girl” instead of “virgin” in Isaiah 7:14) led to the revision of the ASV known as the New American Standard Bible published in 1971. The NASB itself received a major update in 1995 and now exists in two further revisions known as the NASB 2020 and the Legacy Standard Bible. So, the cycle continues with revision upon revision, each one claiming to improve on its predecessors. Only rarely does an English translation team start from scratch. 3. What text will it translate? Mark 1:41 in Codex Bezae (5th c.), showing the reading with Jesus becoming indignant. British Library Another question that follows closely on the last one is which Hebrew and Greek texts the translators will work from. Because our manuscripts of the Bible have differences and because some of these differences affect translation, translators must sometimes decide what text to translate. Does Jesus become “indignant” before healing a man in Mark 1:41 as the NIV 2011 has it, or does he have “compassion” as virtually all other English Bibles have? In this case, the NIV has (unwisely, in my opinion) chosen to follow the text found in a single Greek manuscript from the fifth century known as Codex Bezae. (The NIV does footnote the alternative reading.) In Genesis 4:8, the English Standard Version, following the standard Hebrew text, says that “Cain spoke to Abel his brother” before killing him in the field but does not tell us what he said. But the Christian Standard Bible, follows the evidence of several ancient translations, including the Septuagint, so that Cain says to his brother, “Let’s go out to the field.” In both Mark 1:41 and Genesis 4:8, the differences are not matters of translation philosophy but of text. In places where textual differences affect translation, translators must decide which text they think is the original and then translate that. Sometimes the choices are difficult, and these are places where Bibles will often alert the reader with a footnote. These decisions illustrate why the finely tuned skill of textual scholars is so important. 4. How will it handle culturally specific terms? A fourth question that translators must wrestle with is how to handle terms that are specific to the time and culture of the Bible. Some of the most common ones are terms for weights and units of measurement. No English speaker knows what an ephah of flour is without help or how much a denarius could buy. And how long is a cubit or a span or a stadion? These are all terms found in the original languages, but translations handle them differently. In some cases, a translation may include a table of weights, measures, and monetary units at the back. The NIV and ESV have one after Revelation, for example. A translation may also explain these terms in footnotes. The ESV footnotes often tell the reader that a denarius is about a day’s wage in the first century. Get new articles and updates in your inbox. Leave this field empty if you're human: Another solution is to try to convert these terms into their closest modern equivalent. Paraphrases often take this route. The Living Bible, for example, starts the parable of the unforgiving servant in Matthew 18:23 with a debtor who owes his master, not 10 thousand talents, but 10 million dollars. Later, he reveals his unforgiving heart by trying to collect on $2,000 instead of 100 denarii. The New Living Translation, the successor to the Living Bible, is less specific with “millions of dollars” and then later “thousands of dollars.” Both do a great job conveying the vast difference in amounts, but they must do so by sacrificing something from the original culture in the process. And this is just the tip of the cultural iceberg. Beyond such ancient units of measurement, translators must deal with terms like “Leviathan,” “kinsman-redeemer,” “legion,” “centurion,” not to mention difficult terms for diseases, animals, plants, peoples, and places. Sometimes, translators are at a loss because the precise meaning of the original term is lost to us. At other times, they need to avoid anachronism as with biblical terms for skin ailments that do not actually refer to what we know as “leprosy” or Hansen’s disease. Perhaps future discoveries will clarify, but translators must work with what they have. So, they do the best they can. Their solution is often determined largely by the first question we mentioned: who is the audience? 5. How (much) will the translation explain itself? Finally, many of these questions give rise to this last one which is how and how much the translators will try to explain their decisions to the reader. Most often, this happens through footnotes, but we have already seen other ways that translations can explain their work such as the table of weights and measures. There is also the introduction—but who reads that? (You should!) Translators also have at their disposal features like headings, book introductions, maps, concordances, cross references, appendices and, of course, sometimes study notes. Such aids to the reader can be quite helpful and are found as far back as Bible translations go. It’s little wonder that the first English Bibles, produced by John Wycliffe and his followers in the 14th century, have them too. The Wycliffe Bible oriented its readers with prologues, here showing the one for Mark (left) in Egerton MS 618 (c. 1390–1397), ff. 21v–22r. British Library. The modern Bible that goes the furthest to explain itself is certainly the New English Translation or NET Bible. It was novel at the time, not only because it was provided freely online, but because the translators received mountains of online feedback from its first readers. Today, the NET Bible has over 60,000 translators’ notes, explaining virtually every decision made. The result is a Bible that “explains itself,” pulling the curtain back so to speak. Because of this, it has become something of a favorite among an unexpected audience: other Bible translators. Appreciating Translators These are just five decisions translators must make. There are also many decisions that translators don’t have to make because of the long history of the Bible in English. Things like the names and order of the biblical books as well as their division into chapters and verses are well established by tradition. But that still leaves plenty of work to do besides the most important one which is actually putting Hebrew and Greek into another language. In some cases, one decision affects the others (such as audience) and at other times, decisions cause tension. If you revise a beloved translation too much, for example, you may lose your intended audience. Our judgment of which translation is “best” should always take into account who the audience is. Knowing this leaves us with two important lessons. The first is that our judgment of which translation is “best” should always take into account who the audience is. So many translation decisions are affected by this decision that any fair assessment of a new translation must begin by understanding that. Sometimes, your dislike for a given translation may reflect more the fact that you aren’t the intended audience than it does any failure on the translators’ part. Second, the multitude of decisions translators face should give us a deep appreciation for good translations—and we have many in English. What we’ve covered here are just some of those that have to be made. We haven’t touched on matters like idioms, word order, word plays and other figures of speech, and more. But considering just these five decisions should make us very thankful for the Bibles we have and encourage us to do what every good translator wants us to do with the Bible and that’s to read it. The ESV is a revision of the RSV not the RV as an earlier version of this article stated. It also wrongly called the New Living Translation the New Living Bible and the NET Bible the New English Bible.Notes1Dates given in this section are the date when the entire Bible was first published. In many cases, the publication of the New Testament preceded the Old by several years.