-
2 Chroniques 27
- 1 *Jotham était âgé de 25 ans lorsqu’il commença de régner ; et il régna 16 ans à Jérusalem ; et le nom de sa mère était Jerusha, fille de Tsadok.
- 2 Et il fit ce qui est droit aux yeux de l’Éternel, selon tout ce qu’avait fait Ozias, son père ; seulement il n’entra pas dans le temple de l’Éternel ; et le peuple se corrompait encore.
- 3 Ce fut lui qui bâtit la porte supérieure de la maison de l’Éternel ; et il fit beaucoup de constructions sur la muraille d’Ophel.
- 4 Et il bâtit des villes dans la montagne de Juda, et il bâtit dans les forêts des châteaux et des tours.
- 5 Et il fit la guerre contre le roi des fils d’Ammon, et l’emporta sur eux ; et les fils d’Ammon lui donnèrent cette année-là 100 talents d’argent, et 10 000 cors de froment, et 10 000 d’orge ; les fils d’Ammon lui payèrent cela aussi la seconde année et la troisième.
- 6 Et Jotham devint fort, car il régla ses voies devant l’Éternel, son Dieu.
- 7 Et le reste des actes de Jotham, et toutes ses guerres, et ses voies, voici, ces choses sont écrites dans le livre des rois d’Israël et de Juda.
- 8 Il était âgé de 25 ans quand il commença de régner ; et il régna 16 ans à Jérusalem.
- 9 Et Jotham s’endormit avec ses pères, et on l’enterra dans la ville de David ; et Achaz, son fils, régna à sa place.
-
-
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
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.