-
列王纪上 7
- 1 所罗门为自己建造宫殿花了十三年才完成。
- 2 他又建造黎巴嫩林宫,长四十四公尺,宽二十二公尺,高十三公尺半。有四行香柏木的柱子,柱子上有香柏木的横梁。
- 3 柱子每行十五根,共四十五根;柱子上有厢房,是用香柏木盖屋顶的。
- 4 有窗框三行,窗与窗相对,共有三层。
- 5 所有的门和窗都有四方的框子,有窗三层,窗与窗相对。
- 6 他又建造柱廊,长二十二公尺,宽十三公尺半。在柱廊前有廊子,在廊子前又有柱子和台阶。
- 7 又建造王室座廊,就是审判廊,他在这里执行审判。由地板到天花板,都贴上香柏木板。
- 8 所罗门自己住的宫殿,是在廊后的另一个院内,建造法相同。他又为他娶法老的女儿建造一座宫院,建法与这廊子一样。
- 9 从根基到屋檐,从外院到大院,这一切都是用贵重的石块,按尺寸凿好,用锯子内外锯齐的石块建成的。
- 10 根基也都是用贵重的大石块;有长四公尺的,也有长三公尺半的。
- 11 上面有按着尺寸凿好的贵重石块和香柏木。
- 12 大院的周围有凿好的石头三层,香柏木一层,与耶和华的内院和殿廊一样。
- 13 所罗门王派人去把户兰从推罗接来。
- 14 户兰是拿弗他利支派中一个寡妇的儿子;他父亲是推罗人,是个铜匠。户兰满有智慧、聪明和知识,能作各样铜工;他来到所罗门王那里,作王的一切工作。
- 15 他铸造了两根铜柱,每根高八公尺,圆周五公尺三公寸。
- 16 他又用铜铸造了两个柱顶,安放在柱头上,每个柱顶高两公尺两公寸。
- 17 他又为柱头上的柱头顶做了两块网子和辫结成的链子,每个柱顶有七块。
- 18 他又做了两行石榴围绕在柱头上,柱顶的网子上,两个柱顶都是这样。
- 19 廊子里柱头上的柱顶,刻有百合花细工。
- 20 两根柱子上柱顶的鼓肚上,网子旁边,各有石榴二百个,分两行环绕着。
- 21 他把这两根柱子竖立在殿廊的前面。竖立在南边的柱子,他起名叫雅斤;竖立在北面的柱子,起名叫波阿斯。
- 22 在柱子的上头刻有百合花的细工。这样,做柱子的工作就完成了。
- 23 他又铸造了一座圆形的铜海,从这边到那边四公尺四公寸,高两公尺两公寸,圆周十三公尺两公寸。
- 24 在铜海边缘以下有匏瓜围绕着,每四十五公分十个。匏瓜共有两行,是铸造铜海的时候,一并铸造上去的。
- 25 铜海安放在十二头铜牛背上,三头向北,三头向西,三头向南,三头向东,铜海是在铜牛之上,牛尾都向内。
- 26 铜海厚七公分半,边缘好像杯子的边缘,又好像百合花蕾,能盛水四万公升。
- 27 他又做了十个铜盆座;每个长一公尺八公寸,宽一公尺八公寸,高一公尺三公寸。
- 28 盆座的做法是这样:盆座有数边,各边都连接在盆架中。
- 29 在盆架间的各边上,有狮子、牛和基路伯。盆架上有座,狮子和牛的上下都有花纹的浮雕。
- 30 每个盆座都有四个铜轮和铜轴,在盆座以下的四脚上有铸成的支架,各边都刻有花纹。
- 31 盆座的口从内缘到顶,高四十五公分。盆口作圆形,照盆架上那座的样式,直径六十六公分。盆口的边上也有雕刻,盆座的边是四方形,不是圆形的。
- 32 盆座的四个轮子是在盆边的下面,轮座与轴相接,每个轮子高六十六公分。
- 33 轮子的形状,好像车轮的做法,轮轴、轮辋、轮辐、轮毂都是铸成的。
- 34 每一个盆座的四角都有四个支架;支架是与盆座一块铸成的。
- 35 盆座顶上有一个圆圈,高二十二公分;在盆座顶的座的撑子和边缘是与座一块铸成的。
- 36 又在撑子和边缘的上面刻有基路伯、狮子和棕树,又在各空处,周围刻上花纹。
- 37 他这样做了十个盆座,铸法、尺寸和样式都是相同的。
- 38 他又做了十个铜盆,每个铜盆能盛水八百公升;每个铜盆的直径都是一公尺八公寸。在十个盆座上,每个都安放一个铜盆。
- 39 他把五个盆座放在殿的南边,五个放在殿的北边,又把铜海放在殿的南边,就是靠东南角的地方。
- 40 户兰又做了盆子、铲子和碗。这样,户兰为所罗门王完成了在耶和华的殿里所要作的一切工程。
- 41 所做的就是两根柱子和在柱子顶上碗形的柱顶;两块遮盖柱子顶上碗形柱顶的网子;
- 42 在两块网子上的四百个石榴,每块网子上有两行石榴,遮盖在柱子上头两个碗形的柱顶;
- 43 十个盆座和盆座上的十个铜盆;
- 44 一个铜海和铜海下的十二头铜牛;
- 45 锅、铲子和盘子。以上这一切器皿都是户兰为所罗门在耶和华的殿里用磨亮的铜做成的。
- 46 是王在约旦平原,在疏割与撒拉之间用泥模铸造的。
- 47 这一切器皿所罗门都没有称算过;由于数量太多,铜的重量也无法估计。
- 48 所罗门又做了耶和华殿里的一切器具,就是金坛和放陈设饼的桌子,
- 49 内殿前面的精金灯台,右边五行,左边五行;还有金花、金灯盏,
- 50 精金的碗盆、烛剪、盘子、调羹和火鼎,内殿至圣所的门框和外殿的门枢。
- 51 这样,所罗门为耶和华的殿所作的一切工程都完成了。所罗门把他父亲大卫分别为圣的金银和器皿,都运了来,存放在耶和华殿的库房里。
-
-
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
-
NCV Simplified (cns - 1.1.1)
2020-12-20Chinese (zh-Hans)
新译本 Chinese New Version (simplified) copyright © 1976, 1992, 1999, 2001, 2005, 2010 The Worldwide Bible Society Limited Language: 中文 (Chinese) Dialect: Mandarin, simplified script Translation by: The Worldwide Bible Society Ltd. 2014-02-07
- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible.Chinese (Subform "hans")
- Distribution Abbreviation: NCVs
License
Copyrighted; Permission to distribute granted to CrossWire
Source (OSIS)
https://www.worldbiblesociety.org
- history_1.0
- First release
- history_1.1
- (2020-12-28) New release. Fix MOD-?
- history_1.1.1
- (2022-08-02) Fix typos in configuration file
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.