130. - Collection Point® | The Total Digital Asset Management System

130. - Collection Point® | The Total Digital Asset Management System 130. - Collection Point® | The Total Digital Asset Management System

cipg.codemantra.us
from cipg.codemantra.us More from this publisher
02.04.2013 Views

1. Investigating Structure 61 e. Attempt to explain the purpose(s) of the writer(s)/editor(s) in presenting material in this particular way. f. Investigate the unit under discussion in its context, to check that any proposed structure is consistent with the relationships that its members have with features elsewhere in the book or section of a book. As explained in the Introduction I shall attempt to follow my own guidelines as we investigate the book of Zechariah. Chapters 2-4, therefore, consist of the following. Chapter 2: a decision regarding the divisions of the text that we shall investigate, based on traditional form-critical and literary-critical work, and with regard to the scholarly consensus. Chapter 3: an investigation of individual units, examining first the words that occur two or more times in the unit in question, with regard to their appropriateness to be used to indicate structure. The structure discerned will be discussed, taking into account points d, e and f above. Chapter 4: an investigation of individual units seen in relation to the rest of Zechariah 1-8 and/or 9-14. The same pattern will be followed as in Chapter 3.

Chapter 2 THE DIVISION OF THE BOOK OF ZECHARIAH The first task in approaching the book of Zechariah will be to specify those divisions which may plausibly be considered to be units. These will be different in nature; for example, 2.10-16 is intended to form a unit in connection with 2.5-9, but not on its own. Verses 10-16 may have been added by a redactor and the resulting unit 2.5-16 would then be a secondary unit. This being the case we need to investigate 2.5-9, 2.10-16 and also 2.5-16. An analysis of the whole will, of course, cover the two individual sections and it will not usually be necessary to present a separate table for every small unit. We shall investigate those divisions of the text which are agreed by the majority of scholars, noting points of substantial disagreement. The criteria used in determining these divisions will be largely formcritical in nature. 1 The text of Zechariah does not present great problems, despite the fact that there are several very obscure passages. 2 In other words, we 1. The main sources for this preliminary investigation are the books and commentaries by Amsler, Baldwin, Beuken, Chary, C. Jeremias, Lamarche, Mason, C.L. and E.M. Meyers, Mitchell, Otzen, Petersen, Petitjean, Rignell, Rudolph, Saeb0, R.L. Smith, and Willi-Plein. Others are consulted where there is a particularly disputed passage 2. It is generally agreed that Zech. 1-8 is well preserved. For example, D.L. Petersen (Haggai and Zechariah 1-8 [London: SCM Press, 1985]) only finds it necessary to offer emendations to the MT in 1.4; 2.11-12; 3.2, 5; 4.2, 7, 9; 5.6; 6.3 6-7; 7.13; 8.6, 16 (p. 125). The only serious problem in these concerns ch. 6 (pp. 263-64); in 8.16 PDK is omitted; in 5.6 he reads rnu? for ori>; the others change the forms but not the words found in the text (by adding a or a; changing a person: T for 'he' and vice versa; omitting a daghesh from he mappiq). It would not affect our enquiry greatly if we accepted these; conversely it does not matter greatly if we are wrong in keeping the MT in all these instances. The case of Zech. 9-14 is more difficult, and corruption is often suspected.

Chapter 2<br />

THE DIVISION OF THE BOOK OF ZECHARIAH<br />

<strong>The</strong> first task in approaching the book of Zechariah will be to specify<br />

those divisions which may plausibly be considered to be units. <strong>The</strong>se<br />

will be different in nature; for example, 2.10-16 is intended to form a<br />

unit in connection with 2.5-9, but not on its own. Verses 10-16 may<br />

have been added by a redactor and the resulting unit 2.5-16 would<br />

then be a secondary unit. This being the case we need to investigate<br />

2.5-9, 2.10-16 and also 2.5-16. An analysis of the whole will, of<br />

course, cover the two individual sections and it will not usually be<br />

necessary to present a separate table for every small unit.<br />

We shall investigate those divisions of the text which are agreed by<br />

the majority of scholars, noting points of substantial disagreement.<br />

<strong>The</strong> criteria used in determining these divisions will be largely formcritical<br />

in nature. 1<br />

<strong>The</strong> text of Zechariah does not present great problems, despite the<br />

fact that there are several very obscure passages. 2 In other words, we<br />

1. <strong>The</strong> main sources for this preliminary investigation are the books and<br />

commentaries by Amsler, Baldwin, Beuken, Chary, C. Jeremias, Lamarche, Mason,<br />

C.L. and E.M. Meyers, Mitchell, Otzen, Petersen, Petitjean, Rignell, Rudolph,<br />

Saeb0, R.L. Smith, and Willi-Plein. Others are consulted where there is a particularly<br />

disputed passage<br />

2. It is generally agreed that Zech. 1-8 is well preserved. For example,<br />

D.L. Petersen (Haggai and Zechariah 1-8 [London: SCM Press, 1985]) only finds it<br />

necessary to offer emendations to the MT in 1.4; 2.11-12; 3.2, 5; 4.2, 7, 9; 5.6; 6.3<br />

6-7; 7.13; 8.6, 16 (p. 125). <strong>The</strong> only serious problem in these concerns ch. 6<br />

(pp. 263-64); in 8.16 PDK is omitted; in 5.6 he reads rnu? for ori>; the others change<br />

the forms but not the words found in the text (by adding a or a; changing a person:<br />

T for 'he' and vice versa; omitting a daghesh from he mappiq). It would not affect<br />

our enquiry greatly if we accepted these; conversely it does not matter greatly if we<br />

are wrong in keeping the MT in all these instances.<br />

<strong>The</strong> case of Zech. 9-14 is more difficult, and corruption is often suspected.

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

Saved successfully!

Ooh no, something went wrong!