-
民數記 36
- 1 約瑟後裔的家族中,有瑪拿西的孫子、瑪吉的兒子基列的子孫,他們族中的首領都前來,在摩西面前,在各家族作首領的領袖面前,和在以色列人面前說:
- 2 “耶和華曾經吩咐我主要憑抽籤把地分給以色列人為業;我主也受了耶和華的吩咐,要把我們兄弟西羅非哈的產業分給他的眾女兒。
- 3 但是,如果她們嫁給以色列中別的支派的人,她們的產業就必從我們祖宗的產業中被取去,加在他們丈夫支派的產業上;這樣,我們抽籤所得的產業就失去了。
- 4 到了以色列人的禧年,她們的產業就要加在她們丈夫支派的產業上;這樣,她們的產業就要從我們祖宗支派的產業中被拿去了。”
- 5 摩西照著耶和華的話,吩咐以色列說:“約瑟支派的人說得對。
- 6 論到西羅非哈的眾女兒,耶和華吩咐的話是這樣:‘她們可以隨意嫁自己喜歡的人,但是,只能嫁給同族同支派的人作妻子。
- 7 這樣,以色列人的產業,就不會從一個支派轉到另一個支派去;因為以色列人要各自守住自己祖宗支派的產業。
- 8 從以色列支派中得了產業的女子,要嫁給自己祖宗支派的人作妻子,好使以色列人可以各自承受自己祖宗的產業。
- 9 這樣,以色列人的產業,就不會從一個支派轉到另一個支派去;因為以色列人的支派要各自守住自己的產業。’”
- 10 耶和華怎樣吩咐摩西,西羅非哈的眾女兒就怎樣行。
- 11 西羅非哈的女兒瑪拉、得撒、曷拉、密迦、挪阿,都嫁給了自己叔伯的兒子作妻子。
- 12 她們嫁給了約瑟的兒子瑪拿西子孫家族的人作妻子;她們的產業仍然留在自己的支派中。
- 13 這是耶和華在耶利哥對面,約旦河邊的摩押平原,藉著摩西向以色列人吩咐的命令和典章。
-
-
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.