-
約伯記 32
- 1 因為約伯自以為義,於是這三個人就不再回答他。
- 2 那時,布西人蘭族巴拉迦的兒子以利戶發怒了;他向約伯發怒,因為他在 神面前自以為義。
- 3 他又向約伯的三個朋友發怒,因為他們雖然仍以約伯為有罪,卻找不到回答的話來。
- 4 以利戶等待著要向約伯說話,因為他們的年紀都比以利戶大。
- 5 以利戶一見這三個人的口裡無話回答,他就發怒了。
- 6 布西人巴拉迦的兒子以利戶回答說:“我年紀輕,你們年紀大,因此我拘束畏懼,不敢向你們表達我的意見。
- 7 我心裡想:‘年長的當先說話,壽高的當以智慧教訓人。’
- 8 但是在人心裡面有靈,全能者的氣息使人有聰明。
- 9 年紀大的不都有智慧,年老的不都能明白是非,
- 10 因此我說:‘你們要聽我說話,我也要說出我的意見。’
- 11 你們砌詞說話的時候,我等待著你們的話,留心聽你們的理論。
- 12 我留意聽你們,不料,你們中間沒有人能駁倒約伯,駁回他所說的話。
- 13 你們不要說:‘我們尋得了智慧;能勝過他的,是 神,不是人。’
- 14 約伯沒有用他的話攻擊我,我也不用你們的話回答他。
- 15 他們驚惶失措,不再回應,他們沒有甚麼可說的話了。
- 16 因為他們不說話,因為他們站著不再回應,我就等待嗎?
- 17 我也要回答我的一份話,我也要表達我的意見,
- 18 因為我充滿了要說的話,我裡面的靈催逼我說出來。
- 19 我裡面如盛酒的囊,沒有出氣的地方,又如新酒袋,快要破裂。
- 20 我要說話,使我可以舒暢,我要開口回答。
- 21 我必不徇人的情面,也不奉承人,
- 22 因為我不曉得怎樣奉承。不然,我的創造主很快就把我除去。”
-
-
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.