-
Ensimmäinen kuningasten kirja 4
- 1 Kuningas Salomo oli koko Israelin hallitsija.
- 2 Nämä olivat hänen korkeimmat virkamiehensä: ylipappina oli Asarja, Sadokin poika,
- 3 kirjureina Sisan pojat Elihoref ja Ahia, sihteerinä Josafat, Ahiludin poika,
- 4 sotaväen päällikkönä Benaja, Jojadan poika, pappeina Sadok ja Abjatar,
- 5 ylimaaherrana Asarja, Natanin poika, kuninkaan uskottuna pappi Sabud, Natanin poika,
- 6 hovin päällikkönä Ahisar ja verotöiden valvojana Adoniram, Abdan poika.
- 7 Salomolla oli Israelissa kaksitoista maaherraa, jotka vastasivat kuninkaan ja hänen hovinsa ylläpidosta, kukin vuosittain kuukauden ajan.
- 8 He olivat: Ben-Hur Efraimin vuoristossa;
- 9 Ben-Deker Makasissa, Saalbimissa, Bet-Semesissä ja Elon-Bet- Hananissa;
- 10 Ben-Hesed Arubbotissa Sokon ja koko Heferin alueen päällikkönä;
- 11 Dorin ylängön maaherrana Ben-Abinadab, jolla oli vaimona Salomon tytär Tafat;
- 12 Baana, Ahiludin poika, jolla oli hallinnassaan Taanak ja Megiddon seutu aina Jokmeamin toiselle puolen sekä Jisreelin alapuolella oleva alue Bet-Seanista Saretanin tienoille Abel- Meholaan asti;
- 13 Ramot-Gileadissa Ben-Geber, joka Gileadissa hallitsi Manassesta polveutuvan Jairin leirikyliä sekä Basanissa Argobin aluetta, kuuttakymmentä suurta kaupunkia, jotka oli varustettu muurein ja pronssisalpaisin portein;
- 14 Mahanaimissa Ahinadab, Iddon poika;
- 15 Naftalin heimon alueella Ahimaas, jolla hänelläkin oli vaimona Salomon tytär, Basemat;
- 16 Asserin heimon alueella ja Bealotissa Baana, Husain poika;
- 17 Isaskarin heimon alueella Paruahin poika Josafat;
- 18 Benjaminin heimon alueella Simei, Elan poika;
- 19 Gileadin alueella Urin poika Geber, jonka maita ennen olivat hallinneet amorilaisten kuningas Sihon ja Basanin kuningas Og. Vielä oli yksi maaherra Juudan alueella.
- 20 Juudan ja Israelin kansaa oli paljon, niin paljon kuin on meren rannalla hiekkaa. Heillä riitti ruokaa ja juomaa, ja he elivät tyytyväisinä.
-
-
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.