-
民数记 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.