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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

252 <strong>The</strong> <strong>Aramaic</strong> <strong>Bible</strong>: <strong>Targums</strong> <strong>in</strong> <strong>their</strong> <strong>Historical</strong> <strong>Context</strong><br />

Vatican's expansions occur <strong>in</strong> Genesis 49. That is a full 14 per cent<br />

higher than Neofiti, which has only 32 per cent of its expansions <strong>in</strong><br />

Genesis 49. This difference becomes clearer from the opposite perspective;<br />

92 per cent of the expansions <strong>in</strong> Neofiti ch. 49 also appear <strong>in</strong><br />

Vatican, while Vatican parallels the expansions <strong>in</strong> the rema<strong>in</strong><strong>in</strong>g 22<br />

chapters only 49 per cent of the time. <strong>The</strong> difference between Neofiti<br />

and the Paris Targum is only slightly less marked. Paris's version of<br />

Genesis 49 conta<strong>in</strong>s 81 per cent of Neofiti's expansions, while <strong>in</strong> the<br />

other chapters, it parallels Neofiti only 56 per cent of the time. Both<br />

the Fragmentary <strong>Targums</strong>, then, are more likely to <strong>in</strong>clude an expansion<br />

from a large series of expansions than those more isolated with<strong>in</strong><br />

the translation, away from other expansions.<br />

This phenomenon has implications for our understand<strong>in</strong>g of<br />

Pseudo-Jonathan's character, for Pseudo-Jonathan's parallels with<br />

Neofiti follow a similar pattern. In fact, Pseudo-Jonathan's parallels<br />

with Neofiti <strong>in</strong> Genesis 28-50 suggest that Pseudo-Jonathan derives its<br />

expansions from a fragmentary Targum, rather than a complete<br />

Targum like Neofiti. In Genesis 28-50, Pseudo-Jonathan parallels<br />

Neofiti's expansions <strong>in</strong> the same pattern as the two Fragmentary<br />

<strong>Targums</strong>; more <strong>in</strong> Genesis 49, less <strong>in</strong> the other chapters. Pseudo-<br />

Jonathan parallels 24 of Neofiti's 26 expansions <strong>in</strong> ch. 49—that is 96<br />

per cent—while <strong>in</strong> the rema<strong>in</strong><strong>in</strong>g 22 chapters, it parallels 40 of<br />

Neofiti's 57 expansions, only 70 per cent.<br />

Other circumstantial evidence supports the suggestion that Pseudo-<br />

Jonathan's material comes from a fragmentary Targum. First, dependence<br />

on a fragmentary Targum would expla<strong>in</strong> the number of<br />

expansions <strong>in</strong> Neofiti to Genesis 28-50 that f<strong>in</strong>d no parallel <strong>in</strong> Pseudo-<br />

Jonathan; the 15 verses that conta<strong>in</strong> expansions <strong>in</strong> Neofiti but which<br />

Pseudo-Jonathan merely translates constitute the expansions which that<br />

particular fragmentary Targum failed to <strong>in</strong>clude. Secondly, if Pseudo-<br />

Jonathan's editor drew only upon a fragmentary Targum, he would<br />

have had to compose his own translation. This would expla<strong>in</strong> why<br />

Pseudo-Jonathan's translation differs to such a great extent from that<br />

of the other Palest<strong>in</strong>ian <strong>Targums</strong>. Indeed, this might expla<strong>in</strong> why<br />

Pseudo-Jonathan's language has such strong l<strong>in</strong>ks to Targum Onqelos.<br />

If these results are borne out by further study, then this would be a<br />

step forward <strong>in</strong> understand<strong>in</strong>g Pseudo-Jonathan.<br />

In conclusion, mapp<strong>in</strong>g the synoptic relationships among the<br />

Palest<strong>in</strong>ian <strong>Targums</strong> of the Pentateuch provides both a new method of

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

Saved successfully!

Ooh no, something went wrong!