-
利未记 3
- 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.