-
WORD Research this...Jonah 4
- 1 А Јони би врло недраго, и расрди се.
- 2 И помоли се Господу и рече: Господе! не рекох ли то кад још бијах у својој земљи? зато шћах прије побјећи у Тарсис; јер знах да си ти Бог милостив и жалостив, спор на гњев и обилан милосрђем, и кајеш се ода зла.
- 3 Сада Господе, узми душу моју од мене, јер ми је боље умријети него живјети.
- 4 А Господ рече: је ли добро што се срдиш?
- 5 И Јона изиде из града, и сједе с истока граду, и начини ондје колибу, и сјеђаше под њом у хладу да види што ће бити од града.
- 6 А Господ Бог заповједи, те узрасте тиква над Јоном да му буде сјен над главом да му поможе у муци његовој; и Јона се обрадова тикви веома.
- 7 Потом заповједи Бог, те дође црв у зору сјутрадан, и подгризе тикву, те усахну.
- 8 И кад ограну сунце, посла Бог сух источни вјетар; и сунце стаде жећи Јону по глави тако да обамираше и пожеље да умре говорећи: боље ми је умријети него живјети.
- 9 А Бог рече Јони: је ли добро што се срдиш тикве ради? А он рече: добро је што се срдим до смрти.
- 10 А Господ му рече: теби је жао тикве, око које се нијеси трудио, и које нијеси одгајио, него једну ноћ узрасте а другу ноћ пропаде.
- 11 А мени да не буде жао Ниневије, великога града, у ком има више од сто и двадесет тисућа људи који још не знају шта је десно шта ли лијево, и много стоке?
-
-
King James Version (kjv)
- Afrikaans
- Albanian
- Arabic
- Armenian
- Basque
- Breton
- Calo
- Chamorro
- Cherokee
- Chinese
- Coptic
- Croatian
- Czech
- Danish
- Dari
- 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)
- English and Klingon.
- Esperanto
- Estonian
- Finnish
- French
- German
- Gothic
- Greek
- Greek Modern
- Hebrew
- Hungarian
- Italian
- Japanese
- Korean
- Latin
- Latvian
- Lithuanian
- Malagasy
- Malayalam
- Manx Gaelic
- Maori
- Mongolian
- Myanmar Burmse
- Ndebele
- Norwegian bokmal
- Norwegian nynorsk
- Pohnpeian
- Polish
- Portuguese
- Potawatomi
- Romanian
- Russian
- Scottish Gaelic
- Serbian
- Shona
- Slavonic Elizabeth
- Spanish
- Swahili
- Swedish
- Syriac
- Tagalog
- Tausug
- Thai
- Tok Pisin
- 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...
-
-
Serbian Bible Daničić-Karadžić Ijekavski (srkdijekav - 1)
2017-06-18Serbian (sr)
Serbian Bible: Vuk Stefanović Karadžić translated the New Testament in 1847, and Đuro Daničić finished his translation of the Old Testament in 1865. This Bible translation is a public domain. ,"Biblija Srpski prevod. Vuk Stefanović Karadžić Novi Zakon 1847, Đuro Daničić Stari Zakon 1865."
- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible.Serbian
- Distribution Abbreviation: srkdijekav
License
Public Domain
Source (OSIS)
- history_1.0
- (2017-06-18) First Release
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.