-
WORD Research this...Deuteronomy 34
- 1 So gjekk Moses frå Moabmoarne upp på Nebo, som er den høgste tinden på Pisgafjellet, og ligg midt for Jeriko, og Herren synte honom heile landet: Gilead alt til Dan,
- 2 og heile Naftali og Efraims- og Manasselandet, og heile Judalandet radt til Vesterhavet,
- 3 og Sudlandet og Jordan-kverven, dalen kring Jeriko, som dei kallar Palmebyen, alt til Soar;
- 4 Og Herren sagde til honom: «Dette er det landet eg lova Abraham og Isak og Jakob at eg vilde gjeva ætti deira. No hev du set det for augo dine, men sjølv skal ikkje få koma dit.»
- 5 So døydde Moses, Herrens tenar, der i Moablandet, som Herren hadde sagt.
- 6 Han jorda honom i dalen midt for Bet-Peor, i Moablandet, og ingen hev til denne dag visst um gravi hans.
- 7 Moses var hundrad og tjuge år gamall då han døydde; men endå hadde han ikkje dimst på syni eller veikna i åndi.
- 8 Israels-sønerne gret yver honom på Moabmoarne i tretti dagar; då fyrst var det ende på syrgjehøgtidi.
- 9 Moses hadde lagt henderne på Josva, son åt Nun, so han og var full av visdomsånd, og Israels-sønerne lydde honom, og gjorde som Herren hadde sagt med Moses.
- 10 Men aldri sidan steig det fram i Israel ein profet som Moses, som var so vel kjend med Herren at dei talast ved andlit til andlit.
- 11 Kom i hug alle dei teikn og under Herren sette honom til å gjera i Egyptarland med Farao og alle mennarne og heile landet hans,
- 12 og kom i hug alle dei store verk og agelege gjerningar han gjorde for augo åt heile Israel!
-
-
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
-
-
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...
-
-
Studentmållagsbibelen frå 1921 (norsmb - 1)
2012-01-25Norwegian nynorsk (nn)
Den første komplette Bibel på nynorsk, utgitt av Studentmållaget i Oslo i 1921
- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible. Norwegian.
- Distribution Abbreviation: SMB
License
Public Domain
Source (OSIS)
http://gamal.nynorsk.no/mu/smio/bibelen/
- history_1.0
- First version (2012-01-25)
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.