-
WORD Research this...Zechariah 9
- 1 ¶ Hevi bilong tok bilong BIKPELA long hap bilong Hadrak, na Damaskas bai stap malolo bilong en, taim ol ai bilong ol man, olsem bilong olgeta lain bilong Isrel, bai go long BIKPELA.
- 2 Na Hemat tu bai stap hap arere bilong en, Tairas, na Saidon, maski dispela i gat save tru tru.
- 3 Na Tairas i bin wokim bilong em yet wanpela strongpela ples hait, na hipim i go antap silva olsem das, na naispela gol olsem graun malumalu bilong ol rot.
- 4 Lukim, Bikpela bai tromoi em i go ausait, na Em bai paitim pawa bilong em long biksi. Na Em bai kaikai em olgeta wantaim paia.
- 5 Askelon bai lukim dispela, na pret. Gasa tu bai lukim dispela, na pilim bikpela bel hevi tru, na Ekron. Long wanem, strongpela hop bilong em bai gat sem. Na king bai dai olgeta long Gasa, na Askelon bai i no gat wanpela bilong stap long en.
- 6 Na wanpela bastat bai stap long Asdot, na Mi bai rausim hambak pasin bilong ol Filistin.
- 7 Na Mi bai tekewe blut bilong em ausait long maus bilong em, na ol sting samting bilong em ausait long namel bilong ol tit bilong em. Tasol em husat i stap yet, yes em, bai stap bilong God bilong yumi, na em bai stap olsem wanpela nambawan gavman long Juda, na Ekron olsem wanpela man Jebus.
- 8 Na Mi bai wokim kem raun nabaut long haus bilong Mi, bilong wanem, long ami, bilong wanem, long em husat i wokabaut klostu, na bilong wanem, long em husat i kam bek. Na man bilong mekim man i kisim taim bai i no inap wokabaut namel long ol moa liklik. Long wanem, nau Mi bin lukim wantaim tupela ai bilong Mi.
- 9 ¶ Wokim bikpela amamas tru, O pikinini meri bilong Saion. Singaut bikpela, O pikinini meri bilong Jerusalem. Lukim, King bilong yu i kam long yu. Em i stretpela, na i gat pasin bilong kisim bek. Em i Man i stap daunbilo, na i ran antap long wanpela donki, na antap long pikinini donki, pikinini bilong wanpela donki.
- 10 Na Mi bai rausim karis long Ifraim, na hos long Jerusalem. Na banara bilong pait bai Mi rausim, na Em bai toktok long bel isi i go long ol haiden. Na hap Em i bosim bai stat long biksi, yes, i go long biksi, na i stat long riva, yes, i go long ol pinis bilong dispela graun.
- 11 Long sait bilong yu tu, long blut bilong kontrak bilong yu Mi bin salim i go ausait ol kalabus bilong yu i go ausait long bikpela hul we wara i no stap long en.
- 12 ¶ Yupela tanim i go long strongpela ples hait, yupela ol kalabus bilong hop. Yes, tude Mi tokaut long Mi bai mekim dabol i go long yu,
- 13 Taim Mi bin pulim Juda bilong Mi, pulimapim banara wantaim Ifraim, na kirapim ol pikinini man bilong yu, O Saion, bilong birua long ol pikinini man bilong yu, O Gris, na mekim yu olsem bainat bilong wanpela strongpela man bilong pait.
- 14 Na ol bai lukim BIKPELA antap long ol, na spia bilong Em bai go ausait olsem lait bilong klaut. Na GOD Bikpela bai winim biugel, na bai go wantaim ol raunwin bilong hap saut.
- 15 BIKPELA bilong ol ami bai lukautim ol long pait. Na ol bai kaikai olgeta, na daunim wantaim ol ston bilong katapel. Na ol bai dring, na wokim wanpela nois olsem ol i mekim wantaim wain. Na ol bai stap pulap olsem ol dis, na olsem ol kona bilong alta.
- 16 Na BIKPELA, God bilong ol, bai kisim bek ol long dispela de olsem lain sipsip bilong lain manmeri bilong Em. Long wanem, ol bai stap olsem ol ston bilong wanpela hat king, stap antap olsem wanpela plek antap long hap bilong Em.
- 17 Long wanem, gutpela pasin bilong Em em i bikpela moa, na naispela tru bilong Em em i bikpela olsem wanem! Wit samting bai mekim ol yangpela man long gat amamas, na nupela wain ol yangpela meri.
-
-
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...
-
-
King Jems Pisin Baibel (tpikjpb - 1)
2022-06-07(tpi)
Dispela wok bilong tanim tok em i wok bilong David Holland na Bryan Girard. Version 1.2
- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible.Tok Pisin
- Distribution Abbreviation: King Jems Pisin
License
Creative Commons: BY-NC-ND 4.0
Source (OSIS)
- history_1.0
- (2022-06-07) Initial release
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.