18.07.2013 Views

The Aramaic Bible: Targums in their Historical Context

The Aramaic Bible: Targums in their Historical Context

The Aramaic Bible: Targums in their Historical Context

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

KAUFMAN Dat<strong>in</strong>g the Language of the Palest<strong>in</strong>ian <strong>Targums</strong> 125<br />

exclusively a literary one—but a real dialect none the less. It is<br />

virtually the same as the language found <strong>in</strong> the canonical <strong>Targums</strong> of<br />

Job and the Psalter, and is related <strong>in</strong> many <strong>in</strong>terest<strong>in</strong>g ways to dialects<br />

found <strong>in</strong> other medieval works such as the Tobit text published <strong>in</strong><br />

1878 by Neubauer. 19 <strong>The</strong> standard <strong>Aramaic</strong> dialect most closely<br />

related to it is Syriac—whatever the historical implications of that<br />

relationship may be. To be sure, many of its features are clearly<br />

derived from the Palest<strong>in</strong>ian tradition—such as the particle or>» for<br />

Hebrew "o and the verb *on, 'to see', for example, but, <strong>in</strong> my op<strong>in</strong>ion,<br />

that is no reason to assume a Palest<strong>in</strong>ian orig<strong>in</strong> for any of the texts<br />

written <strong>in</strong> this dialect. Lexemes from this dialect will be cited <strong>in</strong> the<br />

CAL under the siglum LJLA—Late Jewish Literary <strong>Aramaic</strong>.<br />

How, then, are all of these Jewish <strong>Aramaic</strong> texts and all of these<br />

Jewish <strong>Aramaic</strong> dialects related? And is there any k<strong>in</strong>d of methodological<br />

control available that would enable us to justify our picture of<br />

those <strong>in</strong>terrelationships? To follow the old paths will not do, for the<br />

old paths are founded on a premise no longer true—the premise that<br />

all we have are the canonical texts. We must remember that the classical<br />

conceptions of the history of the targumim developed <strong>in</strong> the n<strong>in</strong>eteenth<br />

century, and even the substantial changes occasioned by the discoveries<br />

and <strong>in</strong>itial publications of materials from the Cairo Geniza<br />

were made <strong>in</strong> the pre-Qumran era. <strong>The</strong>re was no firm foundation on<br />

which to rest one's analyses.<br />

I believe that now there is such a foundation—at least bits and<br />

pieces of one. All of us who study and teach targumic literature are<br />

used to the process of compar<strong>in</strong>g parallel texts to the same passage. In<br />

order to compare and evaluate those comparisons, however, we must<br />

have a model <strong>in</strong> m<strong>in</strong>d. If text A is dependent on text B <strong>in</strong> manner X,<br />

what should text A look like? If then, we f<strong>in</strong>d A and we f<strong>in</strong>d B, we can<br />

posit that relationship X obta<strong>in</strong>s. Before now, however, there have not<br />

really been any good models. Thanks to the publications from the<br />

Genizah and to the release of the Qumran material, now there are. Let<br />

us take a look at what they may teach us.<br />

<strong>The</strong> appended <strong>Aramaic</strong> text material consists of three separate<br />

sections of textual 'scores': 20 (A) Traditional <strong>Targums</strong> of Gen. 11.1-8,<br />

19. A. Neubauer, <strong>The</strong> Book of Tobit: A Chaldee Text from a Unique Ms. <strong>in</strong> the<br />

Bodleian Library (Oxford: Clarendon Press, 1878).<br />

20. All read<strong>in</strong>gs are those of the files of the Comprehensive <strong>Aramaic</strong> Lexicon,<br />

which variously have been derived from manuscript photographs, microfilms, and

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!