-
利未記 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.