-
WORD Research this...Judges 10
- 1 Aftir Abymelech roos a duyk in Israel, Thola, the sone of Phua, brother of `the fadir of Abymelech; Thola was a man of Ysachar, that dwelliden in Sanyr, of the hil of Effraym;
- 2 and he demyde Israel thre and twenti yeer, and he `was deed, and biriede in Sanyr.
- 3 His successour was Jair, a man of Galaad, that demyde Israel bi two and twenti yeer;
- 4 and he hadde thretti sones, sittynge aboue thretti coltis of femal assis, and thretti princes of citees, whiche ben clepid bi `his name, Anoth Jair, that is, the citees of Jair, `til in to present day, in the lond of Galaad.
- 5 And Jair `was deed, and biriede in a place `to which the name is Camon.
- 6 Forsothe the sones of Israel ioyneden newe synnes to elde synnes, and diden yuels in the `siyt of the Lord, and serueden to the idols of Baalym, and of Astoroth, and to the goddis of Sirie, and of Sidon, and of Moab, and of the sones of Amon, and of Filistiym; and thei leften the Lord, and worschipiden not hym.
- 7 And the Lord was wrooth ayens hem, and he bitook hem in to the hondis of Filistiym, and of the sones of Amon.
- 8 And alle that dwelliden ouer Jordan in the lond of Ammorrey, which is in Galaad, weren turmentid and oppressid greetli bi eiytene yeer,
- 9 in so myche that the sones of Amon, whanne thei hadden passid Jordan, wastiden Juda and Benjamyn and Effraym; and Israel was turmentid greetli.
- 10 And thei crieden to the Lord, and seiden, We han synned to thee, for we forsoken oure God, and seruyden Baalym.
- 11 To whiche the Lord spak, Whether not Egipcians, and Ammorreis, and the sones of Amon, and of Filistiym, and Sidonyes,
- 12 and Amalech, and Canaan, oppressiden you, and ye crieden to me, and Y delyuerede you fro `the hondis of hem?
- 13 And netheles ye forsoken me, and worschipiden alien goddis; therfor Y schal not adde, that Y delyuere you more.
- 14 Go ye, and clepe goddis whiche ye han chose; delyuere thei you in the tyme of angwisch.
- 15 And the sones of Israel seiden to the Lord, We han synned; yelde thou to vs what euer thing plesith thee; oneli delyuere vs now.
- 16 And thei seiden these thingis, and castiden forth fro her coostis alle the idols of alien goddis, and serueden the Lord; which hadde `rewthe, ether compassioun, on the `wretchidnessis of hem.
- 17 And so the sones of Amon crieden togidere, that is, clepyden hem silf togidere to batel, and excitiden ayens Israel, and settiden tentis in Galaad, `ayens whiche the sones of Israel weren gaderid, and settiden tentis in Masphat.
- 18 And the princes of Galaad seiden ech to hise neiyboris, He, that bigynneth first of vs to fiyte ayens the sones of Amon, schal be duyk of the puple of Galaad.
-
-
King James Version (kjv)
- Afrikaans
- Arabic
- Armenian
- Basque
- Breton
- Chamorro
- Cherokee
- Chinese
- Coptic
- Croatian
- Czech
- Danish
- Dutch
-
English
American King James Version (akjv) American Standard Version (asv) Basic English Bible (basicenglish) Douay Rheims (douayrheims) John Wycliffe Bible (c.1395) (wycliffe) King James Version (kjv) King James Version (1769) with Strongs Numbers and Morphology and CatchWords, including Apocrypha (without glosses) (kjva) Webster's Bible (wb) Weymouth NT (weymouth) William Tyndale Bible (1525/1530) (tyndale) World English Bible (web) Young's Literal Translation (ylt)
- Esperanto
- Estonian
- Finnish
- French
- German
- Gothic
- Greek
- Greek Modern
- Hebrew
- Hungarian
- Italian
- Japanese
- Korean
- Latin
- Latvian
- Lithuanian
- Malayalam
- Manx Gaelic
- Maori
- Myanmar Burmse
- Norwegian bokmal
- Portuguese
- Potawatomi
- Romanian
- Russian
- Scottish Gaelic
- Slavonic Elizabeth
- Spanish
- Swahili
- Swedish
- Syriac
- Tagalog
- Thai
- Turkish
- Ukrainian
- Uma
- Vietnamese
-
-
Active Persistent Session:
To use a different persistent session key, simply add it above, and click the button below.
How This All Works
Your persistent session key, together with your favourite verse, authenticates you. It links to all your notes and tags in the Bible. You can share it with loved ones so they can see your notes and tags.
However, to modify your notes and tags, you need both the persistent session key and your favourite verse.
Please Keep Your Favourite Verse Private
Your persistent session key and favourite verse provide you exclusive access to edit your notes and tags. Think of your persistent session key as a username and your favourite verse as a password. Therefore, ensure your favourite verse is kept private.
The persistent session key allows viewing, while editing is only possible when the correct favourite verse is provided.
-
Loading...
-
-
John Wycliffe Bible (c.1395) (wycliffe - 2.4.1)
2020-08-01English (enm)
The Holy Bible, containing the Old and New Testaments, with the Apocryphal books, in the earliest English versions made from the Latin Vulgate by John Wycliffe and his followers, c.1395
Source text https://en.wikisource.org/wiki/Bible_(Wycliffe)
John Wycliffe organized the first complete translation of the Bible into Middle English in the 1380s.
The translation from the Vulgate was a collaborative effort, and it is not clear which portions are actually Wycliffe's work.
Church authorities officially condemned the translators of the Bible into vernacular languages and called these heretics Lollards.
Despite their prohibition, revised versions of Wycliffite Bibles remained in use for about 100 years.
Wikisource attributes its source as the Wesley Center Online.
That in turn was derived from the Fedosov transcription on the Slavic Bibles site http://www.sbible.ru
The source text makes no use of archaic letters that were part of Middle English orthography.
The Latin letter Yogh [ȝ] was evidently replaced by the letter [y] in the Fedosov transcription.
The text is available under the Creative Commons Attribution-ShareAlike License.
Verse numbers were not used in either the earlier or later version of the Wycliffe Bible in the fourteenth century. Each chapter consisted of one unbroken block of text. There were not even any paragraphs. Hence whatever verse numbers we now have in modern editions have been added retrospectively by comparison with other English Bibles and the Latin Vulgate.
Two books found in the Vulgate, II Esdras and Psalm 151, were never part of the Wycliffe Bible.
Module build notes:
1. The Prayer of Manasseh has been separated from 2 Chronicles in order to avoid a critical versification issue.
cf. In Wikisource it was assigned as 2 Paralipomenon chapter 37.
2. The Letter of Jeremiah has been joined to Baruch as chapter 6 thereof.
3. The book order of Wycliffe's Bible differs from that of the Vulg versification used in this module.
4. There are now 313 notes in the Wikisource document.
5. The Wikisource text substantially matches that of the nine books in module version 1.0
6. Each of these five verses not in the Vulg versification was appended to the previous verse: Deut.27.27 Esth.5.15 Ps.38.15 Ps.147.10 Luke.10.43
7. There are also several verses without any text. Use Sword utility emptyvss to list these.- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible.Old English (1100-1500)
- Distribution Abbreviation: wycliffe
License
Creative Commons: BY-SA 4.0
Source (OSIS)
https://en.wikisource.org/wiki/Bible_(Wycliffe)
- history_1.0
- (2002-09-05) Initial incomplete edition based on the Slavic Bible source text for the Pentateuch and the Gospels only.
- history_2.0
- (2017-03-27) Rebuilt from complete Bible text at Wikisource.
- history_2.1
- (2017-03-28) Minor improvement: Versified Prayer of Manasseh on Wikisource.
- history_2.1.1
- (2017-03-29) Added GlobalOptionFilter=OSISFootnotes (the module already had 14 notes in 2 Samuel, Job and Tobit).
- history_2.2
- (2017-04-03) Rebuilt after 299 notes were added to Pentateuch & Gospels in Wikisource. Minor change to markup of added words.
- history_2.3
- (2019-01-07) Updated toolchain
- history_2.4
- (2020-08-01) title misplacement is fixed for the *Prayer of Jeremiah* in Baruch 6
- history_2.4.1
- (2022-08-06) Fix typo in DistributionLicense
Basic Hash Usage Explained
At getBible, we've established a robust system to keep our API synchronized with the Crosswire project's modules. Let me explain how this integration works in simple terms.
We source our Bible text directly from the Crosswire modules. To monitor any updates, we generate "hash values" for each chapter, book, and translation. These hash values serve as unique identifiers that change only when the underlying content changes, thereby ensuring a tight integration between getBible and the Crosswire modules.
Every month, an automated process runs for approximately three hours. During this window, we fetch the latest Bible text from the Crosswire modules. Subsequently, we compare the new hash values and the text with the previous ones. Any detected changes trigger updates to both our official getBible hash repository and the Bible API for all affected translations. This system has been operating seamlessly for several years.
Once the updates are complete, any application utilizing our Bible API should monitor the hash values at the chapter, book, or translation level. Spotting a change in these values indicates that they should update their respective systems.
Hash values can change due to various reasons, including textual corrections like adding omitted verses, rectifying spelling errors, or addressing any discrepancies flagged by the publishers maintaining the modules at Crosswire.
The Crosswire initiative, also known as the SWORD Project, is the "source of truth" for getBible. Any modifications in the Crosswire modules get reflected in our API within days, ensuring our users access the most precise and current Bible text. We pledge to uphold this standard as long as getBible exists and our build scripts remain operational.
We're united in our mission to preserve the integrity and authenticity of the Bible text. If you have questions or require additional information, please use our support system. We're here to assist and will respond promptly.
Thank you for your understanding and for being an integral part of the getBible community.
Favourite Verse
You should select one of your favourite verses.
This verse in combination with your session key will be used to authenticate you in the future.
This is currently the active session key.
Should you have another session key from a previous session.
You can add it here to load your previous session.