-
WORD Research this...1 Chronicles 13
- 1 καὶ ἐβουλεύσατο Δαυιδ μετὰ τῶν χιλιάρχων καὶ τῶν ἑκατοντάρχων παντὶ ἡγουμένῳ
- 2 καὶ εἶπεν Δαυιδ τῇ πάσῃ ἐκκλησίᾳ Ισραηλ εἰ ἐφ’ ὑμῖν ἀγαθὸν καὶ παρὰ κυρίου θεοῦ ἡμῶν εὐοδωθῇ ἀποστείλωμεν πρὸς τοὺς ἀδελφοὺς ἡμῶν τοὺς ὑπολελειμμένους ἐν πάσῃ γῇ Ισραηλ καὶ μετ’ αὐτῶν οἱ ἱερεῖς οἱ Λευῖται ἐν πόλεσιν κατασχέσεως αὐτῶν καὶ συναχθήσονται πρὸς ἡμᾶς
- 3 καὶ μετενέγκωμεν τὴν κιβωτὸν τοῦ θεοῦ ἡμῶν πρὸς ἡμᾶς ὅτι οὐκ ἐζήτησαν αὐτὴν ἀφ’ ἡμερῶν Σαουλ
- 4 καὶ εἶπεν πᾶσα ἡ ἐκκλησία τοῦ ποιῆσαι οὕτως ὅτι εὐθὴς ὁ λόγος ἐν ὀφθαλμοῖς παντὸς τοῦ λαοῦ
- 5 καὶ ἐξεκκλησίασεν Δαυιδ τὸν πάντα Ισραηλ ἀπὸ ὁρίων Αἰγύπτου καὶ ἕως εἰσόδου Ημαθ τοῦ εἰσενέγκαι τὴν κιβωτὸν τοῦ θεοῦ ἐκ πόλεως Ιαριμ
- 6 καὶ ἀνήγαγεν αὐτὴν Δαυιδ καὶ πᾶς Ισραηλ ἀνέβη εἰς πόλιν Δαυιδ ἣ ἦν τοῦ Ιουδα τοῦ ἀναγαγεῖν ἐκεῖθεν τὴν κιβωτὸν τοῦ θεοῦ κυρίου καθημένου ἐπὶ χερουβιν οὗ ἐπεκλήθη ὄνομα αὐτοῦ
- 7 καὶ ἐπέθηκαν τὴν κιβωτὸν τοῦ θεοῦ ἐπὶ ἅμαξαν καινὴν ἐξ οἴκου Αμιναδαβ καὶ Οζα καὶ οἱ ἀδελφοὶ αὐτοῦ ἦγον τὴν ἅμαξαν
- 8 καὶ Δαυιδ καὶ πᾶς Ισραηλ παίζοντες ἐναντίον τοῦ θεοῦ ἐν πάσῃ δυνάμει καὶ ἐν ψαλτῳδοῖς καὶ ἐν κινύραις καὶ ἐν νάβλαις ἐν τυμπάνοις καὶ ἐν κυμβάλοις καὶ ἐν σάλπιγξιν
- 9 καὶ ἤλθοσαν ἕως τῆς ἅλωνος καὶ ἐξέτεινεν Οζα τὴν χεῖρα αὐτοῦ τοῦ κατασχεῖν τὴν κιβωτόν ὅτι ἐξέκλινεν αὐτὴν ὁ μόσχος
- 10 καὶ ἐθυμώθη ὀργῇ κύριος ἐπὶ Οζα καὶ ἐπάταξεν αὐτὸν ἐκεῖ διὰ τὸ ἐκτεῖναι τὴν χεῖρα αὐτοῦ ἐπὶ τὴν κιβωτόν καὶ ἀπέθανεν ἐκεῖ ἀπέναντι τοῦ θεοῦ
- 11 καὶ ἠθύμησεν Δαυιδ ὅτι διέκοψεν κύριος διακοπὴν ἐν Οζα καὶ ἐκάλεσεν τὸν τόπον ἐκεῖνον Διακοπὴ Οζα ἕως τῆς ἡμέρας ταύτης
- 12 καὶ ἐφοβήθη Δαυιδ τὸν θεὸν ἐν τῇ ἡμέρᾳ ἐκείνῃ λέγων πῶς εἰσοίσω πρὸς ἐμαυτὸν τὴν κιβωτὸν τοῦ θεοῦ
- 13 καὶ οὐκ ἀπέστρεψεν Δαυιδ τὴν κιβωτὸν πρὸς ἑαυτὸν εἰς πόλιν Δαυιδ καὶ ἐξέκλινεν αὐτὴν εἰς οἶκον Αβεδδαρα τοῦ Γεθθαίου
- 14 καὶ ἐκάθισεν ἡ κιβωτὸς τοῦ θεοῦ ἐν οἴκῳ Αβεδδαρα τρεῖς μῆνας καὶ εὐλόγησεν ὁ θεὸς Αβεδδαραμ καὶ πάντα τὰ αὐτοῦ
-
-
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...
-
-
OT LXX Accented (lxx - 3)
2022-08-23Greek (grc)
d The Analytic Septuagint was prepared by Steve Amato of the Boston Christian Bible Study Resources http://www.bcbsr.com
Morphology was included from the LXXM (see below)
The The Analytic Septuagint is not to be used, either directly or indirectly, for commercial purposes without prior written consent of Steve Amato and the legal authors and developers of the morphology of the LXXM identified below.
The LXXM = The morphologically analyzed text of CATSS LXX prepared by CATSS under the direction of R. Kraft (Philadelphia team)
The CATSS LXX = The computer form prepared by the TLG (Thesaurus Linguae Graecae) Project directed by T. Brunner at the University of California, Irvine, with further verification and adaptation (in process) by CATSS towards conformity with the individual Göttingen editions that have appeared since 1935.
The LXX = Septuaginta, ed. A. Rahlfs (Stuttgart: Württembergische Bibelanstalt, 1935; repr. in 9th ed., 1971).
Greek Septuagint Version 270 BC- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible.Ancient Greek (to 1453).O.T.
- Distribution Abbreviation: lxx
License
Copyrighted; Free non-commercial distribution
Source (OSIS)
http://ccat.sas.upenn.edu/gopher/text/religion/biblical/lxxmorph/
- history_1.1
- Replaced missing sections of Isaiah and switched to more descriptive tags for morphology
- history_1.2
- changed to book granularity, which makes module about half as large and removed some extraneous verse references
- history_2.0
- replaced LXX with LXXM and obsoleted old LXX module
- history_2.5
- updated to latest version of LXXM from Steve Amato, migrated to OSIS, converted .conf to UTF-8
- history_2.6
- new module with new v11n
- history_2.7
- new module from scratch
- history_3.0
- (2022-08-23) : This version uses again Pierre build. It comes with small corrections in conf. According to MOD-415. The version grow to 3.0. We have also to decide what we want to do with the lex entries.
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.