-
WORD Research this...Jeremiah 39
- 1 Efter at Jerusalem var indtaget — i Kong Zedekias af Judas niende Regeringsaar i den tiende Maaned, kom Kong Nebukadrezar af Babel med hele sin Hær til Jerusalem og belejrede det;
- 2 i Zedekias's ellevte Aar paa den niende Dag i den fjerde Maaned blev Byen stormet —
- 3 da kom alle Babels Konges Fyrster og satte sig i Midterporten: Overhofmanden Nebusjazban, Magernes Øverste Nergal-Sar'ezer og alle Babels Konges andre Fyrster.
- 4 Da Kong Zedekias af Juda og alle hans Krigsmænd saa dem, flygtede de om Natten fra Byen ad Vejen til Kongens Have gennem Porten mellem de to Mure og tog Vejen ad Araba til.
- 5 Men Kaldæernes Hær satte efter dem og indhentede Zedekias paa Jerikos Lavslette; og de tog ham med og bragte ham op til Kong Nebukadnezar af Babel i Ribla i Hamats Land; og han fældede hans Dom.
- 6 Babels Konge lod i Ribla Zedekias's Sønner dræbe i hans Paasyn; ogsaa alle de ypperste i Juda lod Babels Konge dræbe;
- 7 derpaa lod han Øjnene stikke ud paa Zedekias og lod ham lægge i Kobberlænker for at føre ham til Babel.
- 8 Kaldæerne satte Ild paa Kongens Palads og Folkets Huse og nedbrød Jerusalems Mure.
- 9 Resten af Folket, der var levnet i Byen, Overløberne, der var løbet over til ham, og Resten af Haandværkerne førte Livvagtsøversten Nebuzar'adan som Fanger til Babel,
- 10 og kun nogle af den fattigste Befolkning, der intet ejede, lod Livvagtsøversten Nebuzar'adan blive tilbage i Judas Land, idet han samtidig gav dem Vingaarde og Agre.
- 11 Men om Jeremias bød Kong Nebukadrezar af Babel Livvagtsøversten Nebuzar'adan:
- 12 »Tag ham og hav Øje med ham og gør ham ingen Men; gør med ham, som han selv ønsker!«
- 13 Saa sendte Livvagtsøversten Nebuzar'adan, Overhofmanden Nebusjazban og Magernes Øverste Nergal-Sar'ezer og alle Babels Konges andre Stormænd
- 14 Bud og lod Jeremias hente i Vagtforgaarden og overgav ham til Gedalja, en Søn af Sjafans Søn Ahikam, for at han skulde føre ham til hans Hjem; og han boede iblandt Folket.
- 15 Medens Jeremias sad fængslet i Vagtforgaarden, kom HERRENS Ord til ham saaledes:
- 16 Gaa hen og sig til Ætioperen Ebed-Melek: Saa siger Hærskarers HERRE, Israels Gud: Se, jeg lader mine Ord gaa i Opfyldelse paa denne By til Ulykke og ikke til Lykke, og du skal have dem i Tankerne paa hin Dag.
- 17 Men paa hin Dag redder jeg dig, lyder det fra HERREN, og du skal ikke gives i de Mænds Haand, for hvem du frygter;
- 18 thi jeg vil frelse dig, saa du ikke falder for Sværdet, og du skal vinde dit Liv som Bytte, fordi du stolede paa mig, lyder det fra HERREN.
-
-
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 (danish - 1.0.2)
2017-05-22Danish (da)
Danish translation of the Old Testament authorized in 1931 by the Danish King, with the New Testment being the authorized Danish version from 1907.
The NT is based on an entirely new OCR-scanning of an edition with Latin typographic (not Fraktur). The NT has subsequently been thoroughly proof-read and hand-corrected, and footnotes
as well as tables of contents for each chapter have been added.
The OT is based on an OCR-scan from the late 1980s, scanned from a typographically deficient
edition from 1933. OCR-scanning done and proof-read by a Danish pioneering couple with a heart
for media-missions. It was placed on the Internet by Søren Horn in the early 1990s, from
where it was picked up by Projekt Runeberg at Linköping University. Ulrik Sandborg-Petersen picked
up the text in the mid-2000's, and has since then hand-corrected literally thousands of OCR-mistakes
and paragraphing issues.
Both the OT and the NT retain the original orthography.
Errors and corrections should be sent to Ulrik Sandborg-Petersen via:
https://github.com/emg/- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible.Danish
- Distribution Abbreviation: danish
License
Public Domain
Source (OSIS)
https://github.com/emg/
- history_1.0
- (2017-05-20) Initial Release
- history_1.0.1
- (2017-5-21) added obsoletion notice to conf file for older module with same text from different source
- history_1.0.2
- (2022-08-09) Conf file corrections
- history_1..01
- (2017-05-22) Conf file corrections
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.