-
WORD Research this...4 Mosebog 36
- 1 Og de Øverste for Fædrenehusene i Gileads Børns Slægt, hans, som var en Søn af Makir, Manasse Søn, af Josefs Børns Slægt, gik frem, og de talede for Mose Ansigt og for Fyrsternes Ansigt, dem, som vare de Øverste for Fædrenehusene blandt Israels Børn,
- 2 og de sagde: Herren har budet min Herre at give Israels Børn Landet til Arv ved Lod; og min Herre er befalet af Herren at give vor Broder Zelafehads Arv til hans Døtre;
- 3 men blive de en af de Sønner, som høre til de andre Israels Børns Stammer, til Hustruer, da vil deres Arv gaa bort fra vore Fædres Arv og lægges til den Stamme, som de gaa over til, og gaa bort fra vor Arvs Lod;
- 4 og naar det bliver Jubelaar for Israels Børn, da lægges deres Arv til den Stammes Arv, som de gik over til; og dermed vil deres Arv gaa bort fra vore Fædres Stammes Arv.
- 5 Og Mose bød Israels Børn efter Herrens Mund og sagde: Josefs Børns Stamme taler ret.
- 6 Dette er det Ord, som Herren byder om Zelafehads Døtre og siger: De maa vorde dem til Hustruer, som synes gode for deres Øjne, kun at de vorde dem til Hustruer, som ere af deres Fædres Stammes Slægtskab,
- 7 at Israels Børns Arv ej skal komme omkring fra en Stamme til en anden; men hver iblandt Israels Børn skal hænge ved sine Fædres Stammes Arv.
- 8 Og hver Datter af Israels Børns Stammer, som arver nogen Arv, skal vorde en af sin Faders Stammes Slægtskab til Hustru, paa det Israels Børn kunne arve hver sine Fædres Arv,
- 9 og at en Arv ikke skal komme omkring fra en Stamme til en anden Stamme; men Israels Børns Stammer skulle hænge hver ved sin Arv.
- 10 Som Herren havde befalet Mose, saa gjorde Zelafehads Døtre.
- 11 Og Mahela, Tirza og Hogla og Milka og Noa, Zelafehads Døtre, bleve deres Farbroders Sønners Hustruer.
- 12 Dem, som vare af Manasse Børns, Josefs Søns, Slægter, bleve de til Hustruer, og deres Arv blev hos deres Faders Slægtskabs Stamme.
- 13 Disse ere de Bud og de Love, som Herren bød ved Mose for Israels Børn paa Moabiternes slette Marker, ved Jordanen over for Jeriko.
-
-
King James Version (kjv)
- Afrikaans
- Arabic
- Armenian
- Basque
- Breton
- Chamorro
- Cherokee
- Chinese
- Coptic
- Croatian
- Czech
- Danish
- 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)
- Esperanto
- Estonian
- Finnish
- French
- German
- Gothic
- Greek
- Greek Modern
- Hebrew
- Hungarian
- Italian
- Japanese
- Korean
- Latin
- Latvian
- Lithuanian
- Malayalam
- Manx Gaelic
- Maori
- Myanmar Burmse
- Norwegian bokmal
- Portuguese
- Potawatomi
- Romanian
- Russian
- Scottish Gaelic
- Slavonic Elizabeth
- Spanish
- Swahili
- Swedish
- Syriac
- Tagalog
- Thai
- Turkish
- Ukrainian
- Uma
- Vietnamese
-
-
Active Persistent Session:
To use a different persistent session key, simply add it above, and click the button below.
How This All Works
Your persistent session key, together with your favourite verse, authenticates you. It links to all your notes and tags in the Bible. You can share it with loved ones so they can see your notes and tags.
However, to modify your notes and tags, you need both the persistent session key and your favourite verse.
Please Keep Your Favourite Verse Private
Your persistent session key and favourite verse provide you exclusive access to edit your notes and tags. Think of your persistent session key as a username and your favourite verse as a password. Therefore, ensure your favourite verse is kept private.
The persistent session key allows viewing, while editing is only possible when the correct favourite verse is provided.
-
Loading...
-
-
Danish OT1871 + NT1907 with original orthography (danish1871 - 1)
2017-05-20Danish (da)
Danish translation of the Old Testament authorized in 1871 by the Danish King, and the Danish
authorized translation of the New Testament from 1907. The text is based on entirely new
OCR-scans of editions typeset in Latin fonts, not Fraktur, followed by thorough
proof-reading
as well as addition of footnotes and tables of contents for each chapter. The original
orthography has been kept unchanged.
Public Domain. Copy freely.
OCR-scanning and postprocessing done by Dr. Ulrik Sandborg-Petersen from Scripture Systems ApS,
Denmark.
Errors and corrections should be directed to Ulrik via: https://github.com/emg/- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible.Danish
- Distribution Abbreviation: danish1871
License
Public Domain
Source (OSIS)
https://github.com/emg/
- history_1.0
- (2017-05-20) Initial Release
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.