-
WORD Research this...Sirach 2
- 1 Sone, neiyynge to the seruyce of God, stonde thou in riytfulnesse, and drede; and make redi thi soule to temptacioun.
- 2 Bere doun thin herte, and suffre, and bowe doun thin eere, and take the wordis of vndirstonding, and haaste thou not in to the tyme of deeth.
- 3 Suffre thou the susteynyngis of God; be thou ioyned to God, and abide thou, that thi lijf wexe in the last tyme.
- 4 Take thou alle thing that is set to thee, and suffre thou in sorewe, and haue thou pacience in thi lownesse.
- 5 For whi gold and siluer is preued in fier; forsothe men worthi to be resseyued ben preued in the chymeney of lownesse.
- 6 Bileue thou to God, and he schal rekeuere thee; and dresse thou thi weie, and hope thou in to hym. Kepe thou his drede, and wexe thou eld ther ynne.
- 7 Ye that dreden the Lord, abide his merci, and boowe ye not awei fro hym, lest ye falle doun.
- 8 Ye that dreden the Lord, bileue to hym, and youre mede schal not be auoidid.
- 9 Ye that dreden the Lord, hope into hym, and merci schal come to you into delityng.
- 10 Ye that dreden the Lord, loue hym, and youre hertis schulen be liytned.
- 11 Sones, biholde ye the naciouns of men, and wite ye, that no man hopide in the Lord, and was schent;
- 12 noon dwellide in hise heestis, and was forsakun; ether who inwardli clepide hym, and he despiside hym `that clepide?
- 13 For whi God is pitouse, and merciful, and he schal foryyue synnes in the dai of tribulacioun; and he is defendere to alle men, that seken hym in treuthe.
- 14 Woo to the `man with double herte, and with cursid lippis, and misdoynge hondys; and to a synnere entrynge in to the lond bi twei weies.
- 15 Wo to hem that ben dissolute of herte, that bileuen not to God; and therfor thei schulen not be defendid of him.
- 16 Wo to hem that han lost pacience, and that han forsake riytful weies, and han turned awei in to schrewid weies.
- 17 And what schulen thei do, whanne the Lord schal bigynne to biholde?
- 18 Thei that dreden the Lord, schulen not be vnbileueful to his word; and thei that louen hym, schulen kepe his weie.
- 19 Thei that dreden the Lord, schulen enquere tho thingis, that ben wel plesaunt to hym; and thei that louen him, schulen be fillid with his lawe.
- 20 Thei that dreden the Lord, schulen make redi her hertis, and schulen halewe her soulis in his siyt.
- 21 Thei that dreden the Lord, schulen kepe hise comaundementis, and schulen haue pacience til to the biholdyng of hym;
- 22 and schulen seie, If we doon not penaunce, we schulen falle in to the hondis of the Lord, and not in to the hondis of men.
- 23 For bi the greetnesse of hym, so and his merci is with hym.
-
-
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.