-
歷代志上 14
- 1 泰爾 王 希蘭 將香 柏木 運到大衛那裡,又差遣 使者 和石匠、木匠 給 大衛 建造 宮殿。
- 2 大衛 就知道 耶和華 堅立他 作 以色列 王,又為 自己的民 以色列, 使他的國 興 旺。
- 3 大衛 在耶路撒冷 又 立 后妃, 又 生 兒 女。
- 4 在耶路撒冷 所 生的眾子 是沙母亞、朔罷、拿單、所羅門、
- 5 益轄、以利書亞、以法列、
- 6 挪迦、尼斐、雅非亞、
- 7 以利沙瑪、比利雅大、以利法列。
- 8 非利士人 聽見 大衛 受膏 作 以色列 眾人 的王,非利士 眾人 就上來 尋索 大衛。大衛 聽見,就出去 迎敵。
- 9 非利士人 來了,布散 在利乏音 谷。
- 10 大衛 求問 神,說:「我可以上去 攻打 非利士人嗎?你將他們交 在我手裡嗎?」耶和華 說:「你可以上去,我必將他們交 在你手裡。」
- 11 非利士人來到巴力‧毘拉心,大衛 在那裡 殺敗他們。大衛 說:「 神 藉我的手 沖破 敵人,如同水 沖去一般」;因 此 稱 那 地方為巴力‧毘拉心。
- 12 非利士人將 神像 撇 在那裡,大衛 吩咐 人用火 焚燒了。
- 13 非利士人 又 布散 在利乏音谷。
- 14 大衛 又 求問 神。 神 說:「不要 一直地 上去,要轉 到 他們後頭,從桑林 對面 攻打 他們。
- 15 你聽見 桑樹 梢上 有腳步 的聲音,就 要出 戰,因為 神 已經在你前頭 去 攻打 非利士人 的軍隊。」
- 16 大衛 就遵著 神 所 吩咐的,攻打 非利士人 的軍隊,從基遍 直到 基色。
- 17 於是大衛 的名 傳揚 到列 國,耶和華 使 列 國都 懼怕他。
-
-
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.