Talk:Eben-Ezer

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

No section[edit]

its also one of the four parts of the shulchan aruch —Preceding unsigned comment added by 85.250.151.81 (talk) 19:21, 9 March 2011 (UTC)[reply]

Any chance that Dickens deliberately called the protagonist for his Christmas Carol Ebenezer? Besdomny (talk) 12:53, 3 February 2012 (UTC)[reply]

Come Thou Fount of Every Blessing Reference?[edit]

Should this include that this place is mentioned in the hymn Come Thou Fount of Every Blessing? I would find it useful, and it seems relevant. According to the page on Come Thou Fount, the hymn is about the place, and it may be where most people hear the phrase, if not a Christmas Carol. Treyofdenmark (talk) 01:18, 30 August 2014 (UTC)TreyOfDenmark[reply]

Izbet Sartah: link, identification, importance[edit]

The search word "Izbeth Sartah" leads automatically to this page. There are three issues here.
1. "Izbeth Sartah" is MISSPELLED. It should read "Izbet Sartah", without -th. Thousands of google hits vs. close to none are the quick proof, hundreds of academic articles the long one. So please, change the link to "Izbet Sartah".
2. Izbet Sartah is only one possible, if likely, location of Eben-Ezer, because Eben-Ezer's identification depends on that of Aphek. Eben-Ezer is indeed Izbet Sartah only if Aphek is Ras al-Ayin. (See Avraham Negev and Shimon Gibson (2001), Eben Ezer (p. 149) and Izbet Sartah (p. 250), in Archaeological Encyclopedia of the Holy Land (New York and London: Continuum, ISBN 0-8264-1316-1)
3. The Izbet Sartah ostracon (an Iron Age I abcedary in Proto-Canaanite script) is quite an important find, it deserves its own article, and for the time being, definitely more info right here. — Preceding unsigned comment added by Arminden (talkcontribs) 16:26, 3 October 2015 (UTC)[reply]

Automatic link needed[edit]

... for Izbet Sartah. See for instance the spelling in the title of the PhD thesis of Israel Finkelstein. Arminden (talk) 18:07, 4 July 2019 (UTC)[reply]