-
歷代志下 16
- 1 亞撒在位第三十六年,以色列王巴沙上來攻打猶大,修築拉瑪,不許人離開或進入猶大王亞撒的國境。
- 2 於是亞撒從耶和華的殿和王宮的庫房裡取出金銀來,送給住在大馬士革的亞蘭王便.哈達,說:
- 3 “你父親和我父親曾經立約,你和我也要立約。現在我把金銀送給你,請你去廢除你和以色列王巴沙訂立的約,好使他離開我而去。”
- 4 便.哈達聽從了亞撒王的話,就派遣他屬下的眾軍長去攻擊以色列的城市,他們攻陷了以雲、但、亞伯.瑪音和拿弗他利一切貯藏貨物的城市。
- 5 巴沙聽見了,就停止修築拉瑪,把工程都停止了。
- 6 於是亞撒王帶領猶大眾人,把巴沙修築拉瑪所用的石頭和木材都搬走,用來修築迦巴和米斯巴。
- 7 那時,先見哈拿尼來見猶大王亞撒,對他說:“因你倚靠亞蘭王,沒有倚靠耶和華你的 神,所以亞蘭王的軍隊才可以脫離你的手。
- 8 古實人和路比人不是有強大的軍隊嗎?戰車和馬兵不是極多嗎?只因你倚靠耶和華,耶和華就把他們交在你手裡。
- 9 耶和華的眼目遍察全地,一心歸向他的,他必以大能扶助他們;你作這事太愚昧了。從今以後,你必常有戰爭。”
- 10 於是亞撒對先見發怒,把他囚在監裡。同時亞撒也壓迫人民。
- 11 亞撒所行的事蹟,一生的始末,都記在猶大和以色列諸王記上。
- 12 亞撒在位第三十九年,患了腳病,病情嚴重;可是,連他患病的時候,也沒有尋求耶和華,只管尋求醫生。
- 13 亞撒作王四十一年以後死了,和他的列祖同睡。
- 14 人把他埋葬在大衛城裡他為自己所鑿的墳墓中。他們把他放在堆滿按著作香的方法調和的各樣香料的床上,又為他燒了很多香料。
-
-
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.