28.12.2013 Views

cheenc03a.pdf

cheenc03a.pdf

cheenc03a.pdf

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.

SXESEACH ($@, as if humiliation.' cp PV .to<br />

:rouch') in generally explained as a cypher-farm of<br />

SHEPWPH~N (/?D*, 3 7s ; Gray. HPNgs, hut Babel' (Babylon), which indeed is given instead of<br />

Sheshach' by Tg. (Jer. 25~65141). In Jer. 2526 the<br />

the suggestion 'serpent' may he as fallacious as that<br />

of 'rock-badger' for SHAPHAN ; another form is<br />

whole clause. and in 5 1 ' ~ Sheshach,' is omitted in 6<br />

SHEPHUPHIM), b. Bela b. BENJAMIN (8 la), I Ch. 85<br />

Qmp, adds in 2526, xai poothdr riria~ €oxarar<br />

~Gr&r, and in 51+1 il>rertr 6 rzoan) ; Cornill follo\vr<br />

(cw+ap+an [B], c~+&N KAI axlph [A]. can-<br />

6,<br />

@&,&$ [Y). Cp -4HlRAM. SHtiPHO. SHUPHAM, SHLP- md so too Giesebrecht ie 51 rl. whereas in 25 m6 this<br />

ichoiar retains ' Sherhach,' but regards wa. zi f as an<br />

PlM, SHAI'HAN.<br />

r~t~~~ol~tion. But would a late glossator acquainted<br />

SHERAE. or rather, as RV, SHEERAH (71-SV, . ..<br />

~ith the Afhbesh cypher (in which ~ =n, a=.. etc.) have<br />

caapa [A], cdpaa [Ll; aB [€N EKEINOIC TOIC lied it in interpolating a prophecy ascribed to Jeremiah?<br />

Kar&ho~no~c] and Pesh. connect with lKV, Niphal md what reason was there for uiine a crvotoeram? ,.<br />

.to be left'), a ,daughter' of EPHRAIM (5 12) (I Ch. Enplica!ion deeerperee assurement '-(Renan, ~opport<br />

7 ~ who ~ 'built' ~ ) the two Beth-horonr and UPZEN- rnnuei de ia $or. niiatiqur. 1871, p 26). As to 511r.<br />

SHERAH (I Ch. 714b, a?$w]?r, RV UZZEN~SHEERAH). :here<br />

~~ ~<br />

can be no doubt that ' Sherhach' should he<br />

I. . .,a eL pive3 vpc.do. (for vpoqa?). @a* maker Intitted ; it mars the beauty of the elegiac metre (see<br />

Shela (v",~.,) ~"d Rephah 1s. 14) son3 of 4-u (UZ.~"). LAMBNTATION). TO pIOVe this let US put 5013 and<br />

Conder suggests, as the rite, Bet Sir&, a village 2 m. 5lr1, both elegiac passages, side by side :-<br />

SW. of the Lower Beth-horon (Mcm. 3x6). But on (a) How is cut ~under and broken I the whole earth's<br />

we implicitly trust the name7 [The name Ephnim fixed<br />

kmrncr 1<br />

itself not 0n1y in central hut also in southern Palestine, How is become desolation I Babylon among the<br />

"iiti~"~ !<br />

where it is perhaps more original, and some of the (6) How ir lShe$=achl mkzn and surprised I the whole<br />

names in the genealogy have an unmistakable N.<br />

earth's prmrs I<br />

Arabian affinity. Sheerah may, therefore, be a corrup- How ir bscome a dewlation I Babylon among the<br />

nations !<br />

tion of ,n!r ' Arhhur,' which turns out to be a N.<br />

As to Jer. 2516. we must view the passage in connee-<br />

A~abian tribe-name (ep Geshur). Heres in Ir-heres' :ion with the whole list of peoples in w. 18-26, and<br />

(see HEXES, MOUNT) seems to have the same origin<br />

:arefully niticire the text. The list begins with Judah.<br />

(Crif. Bid.).-T. K. c.] Ebr (TX (Uzzen) we should<br />

Next comes Misrim (so read; cp MIZRAIM). Arabia,<br />

probably (cp '3%) substitute 7.y 'city,' and refer to<br />

Judg. 135. Cp EPHRAIM, 5 11. Beth-shemesh or Irshemesh<br />

isa curiously parallel name, if ,shemesh' comes<br />

from .cilrhim' (see SHAAI.BIM). See, however. NAMES,<br />

5 99, where 'ear (=earlike projection) of Sheerah' is<br />

(5 9 [ii.]) : I Ch. 7r6.t See PsnEsH.<br />

SHE&EZER(~YK~W). Zech. 7 zAV, KV SHAREZeR.2.<br />

SHERIFFS (S',33R, 6 rak fa' i2ovatGuxard. ~bp~pou,<br />

ol (T' ~(OYS. [also Theod.]). EV's rendering of a Bibl:<br />

Aram. official title (such at least ir the prevailing<br />

opinion) in Dan. 3 ~f. It has been generally connected<br />

with the Ar. ~fti 'to advise' (whence the pnicipiul SHESHAN (IW, 9 58 ; some MSS. iW'W [Kenn.] ;<br />

'mufti'), and accordingly translated 'counsellor' (cp<br />

cwcam, CwCaN [?Is CWCbN [A], CICAN [Ll),<br />

KVm8, .lawyers '). A still more far-fetched suggestion daughter married his servant JARHA (qv.) and became<br />

is to read wnan=daaro~ 'consuls' ; for the n instead of the head of an interesting genealogical list ( r Ch. 234.41).<br />

D Gratz (MG WI 19 irl) compares ~.R>OL~=+~A~~LOY. See JZRAHMEEL,~ 2 f Thenamesmay contain authentic<br />

Another scholar says. 'possibly a mutilated form of a<br />

Pers. title in pot "chief"' (Bevan. Don. 80). and<br />

Andrear (Marti. Gram. Bid[.-Aram., Glossary] ruggertr<br />

wnm, denfipfdvi, 'chiefs of religion.' Nor does this<br />

of ,her variants wnim has probably coke from ay>n, ihrou~h<br />

the intermediate form which occurs earlier m MT'r list,<br />

unm3 'All the rul:rs of the province' is, of course. an<br />

editorial insertion, the incorrcctnerr of which is shown by m. 4,<br />

where the hemld addrerrer 'peoples, nations, and language\.'<br />

Cp S*TRAPS. T. K. C.<br />

SHESHAN<br />

Zarephathim, . . . Edom. Moab, Ammon, Misgur (a<br />

repetition, hid undcr ' Tyre and Zidon '), Dedan, Tema.<br />

Bua. Zarephathim, Arabia (thrice), Curhanim, Zimri<br />

;=Zimran), Jerahmeel (Elam and Madai), Zaphon,<br />

lerahmeelim, Cush-jerahnleei (repetitions); then at the<br />

zlose something which by editorial manipulation becnme<br />

'and the king of Sheshach (7) shall drink after them.'<br />

x.The view of huth that 'Sheshach' is il Hcbraiirtion of<br />

>c?.ka, n Babylonian district which gave its nrrnc(?) toan nncicnt<br />

~~gg~~ted as the possible meaning of Uzzen-sheerah ; cp<br />

AzNorH-TABOR.<br />

SHEREBIAE (~!ll~, 53% hut form reemsdoubtful.<br />

C~~~BL~I~]), a porl~exilic priest nnd famil, (Ezrrars dpxijv<br />

[BAl. iv & p ~ g apouLa lL1, a. 24 mpmra IBAI, Nch.8194 Habyloninn dyrmrty, according ro Pinches's reading (but see<br />

~lpn~~n [B, where m+IIScaiepreiena Sn~saa~*n, rvBaca[Al, Pinches himself, TSBA, 188.. 48). is unrenmblc. WincLler<br />

:GBA<br />

9 om. enx*, lolz Ir3l

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

Saved successfully!

Ooh no, something went wrong!