-
WORD Research this...1 Chronicles 10
- 1 Filistejci su zavojštili na Izraelce. Izraelci su pobjegli pred njima i padali pobijeni po gori Gilboi.
- 2 Filistejci stisnuše Šaula i njegove sinove i pogubiše Šaulove sinove Jonatana, Abinadaba i Malki-Šuu.
- 3 Boj je postao žešći oko Šaula. Iznenadiše ga strijelci s lukovima i on pade ranjen od strijelaca.
- 4 Tada Šaul reče svome štitonoši: "Izvuci svoj mač i probodi me da ne dođu ti neobrezanci i ne narugaju mi se." Ali se njegov štitonoša prestravi i ne htjede toga učiniti. Zato Šaul uze mač i baci se na nj.
- 5 Kad je štitonoša vidio da je Šaul umro, baci se i on na svoj mač i umrije s njim.
- 6 Tako onog dana pogiboše zajedno Šaul, njegova tri sina i sav njegov dom.
- 7 Kad su svi Izraelci koji su bili u dolini vidjeli da su sinovi Izraelovi pobjegli i da je poginuo Šaul sa sinovima, ostavili su svoje gradove i razbježali se. Filistejci dođoše i nastaniše se u njima.
- 8 Kad su sutradan došli Filistejci da oplijene pobijene, našli su Šaula s njegovim sinovima gdje leže mrtvi na gori Gilboi.
- 9 Svukavši ga, uzeše mu glavu i oružje te poslaše po filistejskoj zemlji unaokolo javljajući veselu vijest svojim idolima i narodu.
- 10 Potom su oružje metnuli u hram svoga boga, a lubanju mu izložili u Dagonovu hramu.
- 11 Kad su čuli svi Jabeš-Gileađani što su Filistejci učinili od Šaula,
- 12 ustali su svi hrabri ljudi i uzeli Šaulovo mrtvo tijelo i tjelesa njegovih sinova i, donijevši ih u Jabeš, pokopali su njihove kosti pod tamarisom u Jabešu; i postiše sedam dana.
- 13 Tako je poginuo Šaul za svoju nevjeru kojom se iznevjerio Jahvi: nije držao Jahvine zapovijedi i povrh toga je pitao za savjet bajačicu,
- 14 a nije pitao Jahvu; zato ga je ubio i prenio kraljevstvo na Jišajeva sina Davida.
-
-
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...
-
-
Croatian (croatia - 1)
2003-05-07Croatian (hr)
Croatian Bible
- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible. Croatian.
- Distribution Abbreviation: croatia
License
Public Domain
Source (ThML)
http://unbound.biola.edu/
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.