-
WORD Research this...Colossians 4
- 1 ܡܪܝܐ ܥܒܕܘ ܫܘܝܘܬܐ ܘܟܐܢܘܬܐ ܠܘܬ ܥܒܕܝܟܘܢ ܘܗܘܝܬܘܢ ܝܕܥܝܢ ܕܐܦ ܠܟܘܢ ܐܝܬ ܗܘ ܡܪܐ ܒܫܡܝܐ ܀
- 2 ܒܨܠܘܬܐ ܐܬܐܡܢܘ ܘܗܘܝܬܘܢ ܥܝܪܝܢ ܐܢܬܘܢ ܒܗ ܘܡܘܕܝܢ ܀
- 3 ܘܡܨܠܝܢ ܐܦ ܥܠܝܢ ܕܐܠܗܐ ܢܦܬܚ ܠܢ ܬܪܥܐ ܕܡܠܬܐ ܠܡܡܠܠܘ ܐܪܙܐ ܕܡܫܝܚܐ ܕܡܛܠܬܗ ܐܤܝܪ ܐܢܐ ܀
- 4 ܕܐܓܠܝܘܗܝ ܘܐܡܠܠܝܘܗܝ ܐܝܟܢܐ ܕܘܠܐ ܠܝ ܀
- 5 ܒܚܟܡܬܐ ܗܠܟܘ ܠܘܬ ܒܪܝܐ ܘܙܒܢܘ ܩܐܪܤܟܘܢ ܀
- 6 ܘܡܠܬܟܘܢ ܒܟܠܙܒܢ ܒܛܝܒܘܬܐ ܐܝܟ ܕܒܡܠܚܐ ܬܗܘܐ ܡܡܕܟܐ ܘܗܘܝܬܘܢ ܝܕܥܝܢ ܠܐܢܫ ܐܢܫ ܐܝܟܢܐ ܘܠܐ ܠܟܘܢ ܠܡܬܒܘ ܦܬܓܡܐ ܀
- 7 ܡܕܡ ܕܠܘܬܝ ܕܝܢ ܢܘܕܥܟܘܢ ܛܘܟܝܩܘܤ ܐܚܐ ܚܒܝܒܐ ܘܡܫܡܫܢܐ ܡܗܝܡܢܐ ܘܟܢܬܢ ܒܡܪܝܐ ܀
- 8 ܗܢܐ ܕܫܕܪܬ ܠܘܬܟܘܢ ܥܠܝܗ ܥܠ ܗܕܐ ܕܢܕܥ ܡܐ ܕܠܘܬܟܘܢ ܘܢܒܝܐ ܠܒܘܬܟܘܢ ܀
- 9 ܥܡ ܐܢܤܝܡܘܤ ܐܚܐ ܡܗܝܡܢܐ ܘܚܒܝܒܐ ܗܘ ܕܐܝܬܘܗܝ ܡܢܟܘܢ ܗܢܘܢ ܢܘܕܥܘܢܟܘܢ ܡܕܡ ܕܠܘܬܢ ܀
- 10 ܫܐܠ ܒܫܠܡܟܘܢ ܐܪܤܛܪܟܘܤ ܫܒܝܐ ܕܥܡܝ ܘܡܪܩܘܤ ܒܪ ܕܕܗ ܕܒܪܢܒܐ ܗܘ ܕܐܬܦܩܕܬܘܢ ܥܠܘܗܝ ܕܐܢ ܐܬܐ ܠܘܬܟܘܢ ܬܩܒܠܘܢܝܗܝ ܀
- 11 ܘܝܫܘܥ ܗܘ ܕܡܬܩܪܐ ܝܘܤܛܘܤ ܗܠܝܢ ܕܐܝܬܝܗܘܢ ܡܢ ܓܙܘܪܬܐ ܘܗܢܘܢ ܒܠܚܘܕ ܥܕܪܘܢܝ ܒܡܠܟܘܬܗ ܕܐܠܗܐ ܘܗܢܘܢ ܗܘܘ ܠܝ ܒܘܝܐܐ ܀
- 12 ܫܐܠ ܒܫܠܡܟܘܢ ܐܦܦܪܐ ܗܘ ܕܡܢܟܘܢ ܥܒܕܐ ܕܡܫܝܚܐ ܟܕ ܒܟܠܙܒܢ ܥܡܠ ܚܠܦܝܟܘܢ ܒܨܠܘܬܐ ܕܬܩܘܡܘܢ ܓܡܝܪܐ ܘܡܫܡܠܝܐ ܒܟܠܗ ܨܒܝܢܗ ܕܐܠܗܐ ܀
- 13 ܤܗܕ ܐܢܐ ܓܝܪ ܥܠܘܗܝ ܕܛܢܢܐ ܤܓܝܐܐ ܐܝܬ ܠܗ ܚܠܦܝܟܘܢ ܘܚܠܦ ܗܢܘܢ ܕܒܠܕܝܩܝܐ ܘܕܒܐܝܪܦܘܠܝܤ ܀
- 14 ܫܐܠ ܒܫܠܡܟܘܢ ܠܘܩܐ ܐܤܝܐ ܚܒܝܒܢ ܘܕܡܐ ܀
- 15 ܫܐܠܘ ܒܫܠܡܐ ܕܐܚܐ ܕܒܠܕܝܩܝܐ ܘܕܢܘܡܦܐ ܘܕܥܕܬܐ ܕܒܒܝܬܗ ܀
- 16 ܘܡܐ ܕܐܬܩܪܝܬ ܐܓܪܬܐ ܗܕܐ ܠܘܬܟܘܢ ܥܒܕܘ ܕܐܦ ܒܥܕܬܐ ܕܠܕܝܩܝܐ ܬܬܩܪܐ ܘܗܝ ܕܐܬܟܬܒܬ ܡܢ ܠܕܝܩܝܐ ܩܪܐܘܗ ܐܢܬܘܢ ܀
- 17 ܘܐܡܪܘ ܠܐܪܟܝܦܘܤ ܕܐܙܕܗܪ ܒܬܫܡܫܬܐ ܗܝ ܕܩܒܠܬ ܒܡܪܢ ܕܬܗܘܐ ܡܫܡܠܐ ܠܗ ܀
- 18 ܫܠܡܐ ܗܢܐ ܒܐܝܕܐ ܕܝܠܝ ܕܦܘܠܘܤ ܗܘܝܬܘܢ ܥܗܕܝܢ ܠܐܤܘܪܝ ܛܝܒܘܬܐ ܥܡܟܘܢ ܐܡܝܢ ܀
-
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...
-
-
Peshitta NT (peshitta - 2)
2020-02-08Syriac (syr)
The Peshitta (Classical Syriac: ܦܫܺܝܛܬܳܐ or ܦܫܝܼܛܬܵܐ pšīṭtā) is the standard version of the Bible for churches in the Syriac tradition. The text is that published by the British and Foreign Bible Society in 1905
Public Domain
Courtesy John Richards.- Encoding: UTF-8
- Direction: RTL
- LCSH: Bible.Syriac
- Distribution Abbreviation: peshitta
License
Public Domain
Source (OSIS)
http://www.tertullian.org/rpearse/thesyriaclibrary/new_testament.htm or http://madenkha.net/holy_bible/
- history_1.1
- (2002-01-01) tagged as right to left
- history_2.0
- (2020-02-08) New TextSource, fix emptyvss issues
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.