-
Joshua 16
- 1 約瑟後裔掣籤而得之地、自近耶利哥之約但、耶利哥水東之野、由耶利哥而上、越乎山地、至伯特利、
- 2 自伯特利至路斯、沿亞基界、至亞他綠、
- 3 西至押利提界、延及下伯和崙界、至基色、極於海、
- 4 此乃約瑟子瑪拿西以法蓮所得之業、
- 5 以法蓮裔循其室家、所得之地、其東界、沿亞他綠亞達、至上伯和崙、
- 6 西通北方之密米他、轉東至他納示羅、延及雅挪哈之東、
- 7 自雅挪哈、下至亞他綠與拿拉、延及耶利哥、極於約但、
- 8 自他普亞而西、至加拿溪、極於海、此乃以法蓮支派循其室家、所得之業、
- 9 又有數邑、與其鄉里、在瑪拿西人業中、分歸以法蓮人、
- 10 居基色之迦南人、以法蓮人未逐之、仍居以法蓮人中、爲僕服役、至於今日、
-
-
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
-
聖經 (文理和合) (chiunl - 1)
2012-07-25Chinese (zh)
譯者:湛約翰、艾約瑟、惠志道、謝衛樓、沙伯
文理和合本新約全書於1906年出版,新舊約全書於1919年出版。隨後新約略加修訂,潤飾譯文,庶使文筆能追及舊約。修訂新約後的新舊約全書,於1923年出版,至1934年印行最後一版- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible. Chinese.
- Distribution Abbreviation: chiunl
License
Public Domain
Source (OSIS)
http://zh.wikisource.org/zh-hant/聖經%20(文理和合)
- history_1.0
- Initial release (2012-07-25)
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.