-
WORD Research this...Joshua 16
- 1 Den lodd som tilfalt Josefs barn, gikk fra Jordan ved Jeriko, østenom vannet ved Jeriko, gjennem ørkenen som stiger fra Jeriko opover fjellene til Betel.
- 2 Fra Betel gikk grensen frem til Luz og videre bort til arkittenes land, til Atarot,
- 3 tok så vestover ned til jafletittenes land, til Nedre-Bet-Horons landemerke og til Geser og endte ute ved havet.
- 4 Dette var den arv som Josefs barn, Manasse og Efra'im, fikk.
- 5 Efra'ims barns land efter deres ætter lå således til: Mot øst gikk grensen for deres arvelodd over Atrot-Addar frem til Øvre-Bet-Horon
- 6 og endte ute ved havet. Mot nord gikk grensen over Mikmetat og bøide sig mot øst til Ta'anat-Silo og holdt frem østover til Janoah.
- 7 Fra Janoah tok den så ned til Atarot og Na'ara, rørte ved Jeriko og endte ved Jordan.
- 8 Fra Tappuah gikk grensen vestover til Kana-bekken og endte ute ved havet. Dette var den arvelodd som Efra'ims barns stamme fikk efter sine ætter,
- 9 dessuten de byer som blev utskilt for Efra'ims barn inne i Manasses barns arvelodd, både byene og de tilhørende landsbyer.
- 10 Men de drev ikke bort de kana'anitter som bodde i Geser; kana'anittene blev boende blandt Efra'ims barn, som de gjør den dag idag, men blev arbeidspliktige træler.
-
-
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...
-
-
Det Norsk Bibelselskap (1930) (bibelselskap - 2)
2020-02-08Norwegian bokmal (nb)
Denne er det Norsk Bibelselskapets 1930 utgave av Bibelen på Norsk (Bokmål)
This is the Norwegian Bible Society’s 1930 edition of the Bible in Bokmål Norwegian
Text scanned and proofed by H. Priebe and co-workers. Based on the version prepared by Tore Vamraak.- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible.Norwegian Bokmal
- Distribution Abbreviation: Bibelen på Norsk
License
Public Domain
Source (OSIS)
http://unbound.biola.edu/
- history_1.0
- initial release
- history_1.1
- Compressed the module
- history_1.5
- Updated to new source, OSIS encoding
- history_2.0
- (2020-02-08) New module, added notes and crossreferences
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.