-
历代志下 17
- 1 亚撒的儿子约沙法接续他作王,奋勇自强,防备以色列人,
- 2 安置军兵在犹大一切坚固城里,又安置防兵在犹大地和他父亚撒所得以法莲的城邑中。
- 3 耶和华与约沙法同在;因为他行他祖大卫初行的道,不寻求巴力,
- 4 只寻求他父亲的 神,遵行他的诫命,不效法以色列人的行为。
- 5 所以耶和华坚定他的国,犹大众人给他进贡;约沙法大有尊荣资财。
- 6 他高兴遵行耶和华的道,并且从犹大除掉一切邱坛和木偶。
- 7 他作王第三年,就差遣臣子便亥伊勒、俄巴底、撒迦利雅、拿坦业、米该亚往犹大各城去教训百姓。
- 8 同着他们有利未人示玛雅、尼探雅、西巴第雅、亚撒黑、示米拉末、约拿单、亚多尼雅、多比雅、驼巴多尼雅,又有祭司以利沙玛、约兰同着他们。
- 9 他们带着耶和华的律法书,走遍犹大各城教训百姓。
- 10 耶和华使犹大四围的列国都甚恐惧,不敢与约沙法争战。
- 11 有些非利士人与约沙法送礼物,纳贡银。阿拉伯人也送他公绵羊七千七百只,公山羊七千七百只。
- 12 约沙法日渐强大,在犹大建造营寨和积货城。
- 13 他在犹大城邑中有许多工程,又在耶路撒冷有战士,就是大能的勇士。
- 14 他们的数目,按着宗族,记在下面:犹大族的千夫长押拿为首率领大能的勇士―三十万;
- 15 其次是,千夫长约哈难率领大能的勇士―二十八万;
- 16 其次是,细基利的儿子亚玛斯雅〈他为耶和华牺牲自己〉率领大能的勇士―二十万。
- 17 便雅悯族,是大能的勇士以利雅大率领拿弓箭和盾牌的―二十万;
- 18 其次是,约萨拔率领预备打仗的―十八万。
- 19 这都是伺候王的,还有王在犹大全地坚固城所安置的不在其内。
-
-
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.