From 92dcfec3bfd332bc93b7bf876dc190c0ff23546e Mon Sep 17 00:00:00 2001 From: Warren Block Date: Sat, 31 Oct 2015 21:42:35 +0000 Subject: [PATCH] Add a zh_TW translation of the leap seconds article by RayCherng Yu. Submitted by: RayCherng Yu --- zh_TW.UTF-8/articles/leap-seconds/Makefile | 19 ++ zh_TW.UTF-8/articles/leap-seconds/article.xml | 71 ++++++ zh_TW.UTF-8/articles/leap-seconds/zh_TW.po | 240 ++++++++++++++++++ 3 files changed, 330 insertions(+) create mode 100644 zh_TW.UTF-8/articles/leap-seconds/Makefile create mode 100644 zh_TW.UTF-8/articles/leap-seconds/article.xml create mode 100644 zh_TW.UTF-8/articles/leap-seconds/zh_TW.po diff --git a/zh_TW.UTF-8/articles/leap-seconds/Makefile b/zh_TW.UTF-8/articles/leap-seconds/Makefile new file mode 100644 index 0000000000..890b94f26e --- /dev/null +++ b/zh_TW.UTF-8/articles/leap-seconds/Makefile @@ -0,0 +1,19 @@ +# +# $FreeBSD$ +# +# Article: Leap Seconds + +DOC?= article + +FORMATS?= html +WITH_ARTICLE_TOC?= YES + +INSTALL_COMPRESSED?= gz +INSTALL_ONLY_COMPRESSED?= + +SRCS= article.xml + +URL_RELPREFIX?= ../../../.. +DOC_PREFIX?= ${.CURDIR}/../../.. + +.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/zh_TW.UTF-8/articles/leap-seconds/article.xml b/zh_TW.UTF-8/articles/leap-seconds/article.xml new file mode 100644 index 0000000000..04d76af3f6 --- /dev/null +++ b/zh_TW.UTF-8/articles/leap-seconds/article.xml @@ -0,0 +1,71 @@ + + +
+ + + FreeBSD 對潤秒的支援 + + $FreeBSD$ + + + + 說明 + + 潤秒是為了同步地球自轉，與原子鐘所做的特定一秒的修正。本文描述FreeBSD 如何處理潤秒。 + + 本文寫作時，下一個潤秒會發生在2015年6月30日23:59:60 CST。下一次潤秒會發生在南北美洲和亞太地區的工作日。 + + 潤秒是由 IERS 在 Bulletin C所發表。 + + 標準的潤秒行為描述在RFC 7164.。也可見 time2posix3。 + + + + FreeBSD預設的潤秒處理 + + The easiest way to handle leap seconds is with the + POSIX time rules FreeBSD uses by default, + combined with NTP. + When ntpd8 is running and the time is synchronized with + upstream NTP servers that handle leap seconds + correctly, the leap second will cause the system time to + automatically repeat the last second of the day. No other + adjustments are necessary. + + 如果上游的 NTP 伺服器無法正確地處理潤秒， ntpd8 會在錯誤的上游伺服器發現錯誤並跳一秒後，跟著把時間跳一秒。 + + 如果位使用 NTP ，將需要在潤秒過後，手動調整系統時鐘。 + + + + 警告 + + 潤秒的插入在全世界是在同一個瞬間： UTC 午夜。在日本，是在上午九點，在太平洋，是正午，在美洲，是傍晚，在歐洲，是晚上。 + + 我們相信和預期，如果提供正確和穩定的NTP 服務，FreeBSD會如設計地在這次潤秒正確運作，就像在之前遇到潤秒時一樣。 + + 然而我們要警告，實務上沒有應用程式曾經要求核心關於潤秒的事。我們的經驗是，如同設計，潤秒本質上是潤秒前一秒的重播，這對大部份應用程式設計師來說是意想不到的事。 + + 其他作業系統或電腦可能會或可能不會像FreeBSD用同樣方法處理潤秒，沒有正確和穩定NTP 服務的系統一點也不會知道潤秒的發生。 + + 電腦因為潤秒而當機並不是沒有聽聞，經驗上也顯示，有大量公用的NTP 伺服器沒有正確地處理和公告潤秒。 + + 請試著確定不會因為潤秒而發生任何可怕的事情。 + + + + 測試 + + 測試是否有使用潤秒是有可能的。由於 NTP的性質，測試可能要運作到潤秒前24小時。有些主要的參考時鐘來源只在潤秒前一個小時公告。詢問NTP行程： + + % ntpq -c 'rv 0 leap' + + 包含leap_add_sec 的輸出指出對於潤秒的支援。潤秒前24小時，或是潤秒已經過了，會顯示leap_none。 + + + + 結論 + + 實務上，FreeBSD 的潤秒通常不是個問題。我們希望這篇概述能幫助釐清預期會遇到什麼狀況，如何使潤秒事件進行的更順利。 + +
diff --git a/zh_TW.UTF-8/articles/leap-seconds/zh_TW.po b/zh_TW.UTF-8/articles/leap-seconds/zh_TW.po new file mode 100644 index 0000000000..e31c5436d7 --- /dev/null +++ b/zh_TW.UTF-8/articles/leap-seconds/zh_TW.po @@ -0,0 +1,240 @@ +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: 2015-10-31 11:25-0600\n" +"PO-Revision-Date: 2015-10-12 19:26+0800\n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: zh_TW\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 1.7.5\n" + +#. Put one translator per line, in the form NAME , YEAR1, YEAR2 +msgctxt "_" +msgid "translator-credits" +msgstr "translator-credits" + +#. (itstool) path: info/title +#: article.translate.xml:6 +msgid "FreeBSD Support for Leap Seconds" +msgstr "FreeBSD 對潤秒的支援" + +#. (itstool) path: info/pubdate +#: article.translate.xml:8 +msgid "" +"$FreeBSD: head/en_US.ISO8859-1/articles/leap-seconds/article.xml 46895 " +"2015-06-29 16:41:41Z wblock $" +msgstr "" + +#. (itstool) path: sect1/title +#: article.translate.xml:12 +msgid "Introduction" +msgstr "說明" + +#. (itstool) path: sect1/para +#: article.translate.xml:14 +msgid "" +"A leap second is an ad-hoc one-second correction to " +"synchronize atomic timescales with Earth rotation. This article describes " +"how FreeBSD interacts with leap seconds." +msgstr "" +"潤秒是為了同步地球自轉，與原子鐘所做的特定一秒的修正。本" +"文描述FreeBSD 如何處理潤秒。" + +#. (itstool) path: sect1/para +#: article.translate.xml:19 +msgid "" +"As of this writing, the next leap second will occur at 2015-Jun-30 23:59:60 " +"UTC. This leap second will occur during a business day for North and South " +"America and the Asia/Pacific region." +msgstr "" +"本文寫作時，下一個潤秒會發生在2015年6月30日23:59:60 CST。下一次潤秒會發生在南" +"北美洲和亞太地區的工作日。" + +#. (itstool) path: sect1/para +#: article.translate.xml:24 +msgid "" +"Leap seconds are announced by IERS on Bulletin C." +msgstr "" +"潤秒是由 IERS 在 Bulletin C所發表。" + +#. (itstool) path: sect1/para +#: article.translate.xml:28 +msgid "" +"Standard leap second behavior is described in RFC 7164. Also see " +"time2posix3." +msgstr "" +"標準的潤秒行為描述在RFC 7164.。也可見 " +"time2posix3。" + +#. (itstool) path: sect1/title +#: article.translate.xml:33 +msgid "Default Leap Second Handling on FreeBSD" +msgstr "FreeBSD預設的潤秒處理" + +#. (itstool) path: sect1/para +#: article.translate.xml:35 +#, fuzzy +msgid "" +"The easiest way to handle leap seconds is with the POSIX " +"time rules FreeBSD uses by default, combined with NTP. When ntpd8 is running and the " +"time is synchronized with upstream NTP servers that " +"handle leap seconds correctly, the leap second will cause the system time to " +"automatically repeat the last second of the day. No other adjustments are " +"necessary." +msgstr "" +"最簡單的處理潤秒方法使用FreeBSD預設的 POSIX 時間規則，並使" +"用 NTP。如果 " +"ntpd8 在執行，而且時間和上游正確處理潤秒的 NTP 伺" +"服器同步，潤秒會使系統時間自動重複當天的最後一秒。不需要其他調整。" + +#. (itstool) path: sect1/para +#: article.translate.xml:44 +msgid "" +"If the upstream NTP servers do not handle leap seconds " +"correctly, ntpd8 will step the time by one second after the errant " +"upstream server has noticed and stepped itself." +msgstr "" +"如果上游的 NTP 伺服器無法正確地處理潤秒， " +"ntpd8 會在錯誤的上游伺服器發現錯誤並跳一秒後，跟著把時間跳一秒。" + +#. (itstool) path: sect1/para +#: article.translate.xml:49 +msgid "" +"If NTP is not being used, manual adjustment of the system " +"clock will be required after the leap second has passed." +msgstr "" +"如果位使用 NTP ，將需要在潤秒過後，手動調整系統時鐘。" + +#. (itstool) path: sect1/title +#: article.translate.xml:55 +msgid "Cautions" +msgstr "警告" + +#. (itstool) path: sect1/para +#: article.translate.xml:57 +msgid "" +"Leap seconds are inserted at the same instant all over the world: " +"UTC midnight. In Japan that is mid-morning, in the " +"Pacific mid-day, in the Americas late afternoon, and in Europe at night." +msgstr "" +"潤秒的插入在全世界是在同一個瞬間： UTC 午夜。在日本，是在" +"上午九點，在太平洋，是正午，在美洲，是傍晚，在歐洲，是晚上。" + +#. (itstool) path: sect1/para +#: article.translate.xml:62 +msgid "" +"We believe and expect that FreeBSD, if provided correct and stable " +"NTP service, will work as designed during this leap " +"second, as it did during the previous ones." +msgstr "" +"我們相信和預期，如果提供正確和穩定的NTP 服務，FreeBSD會如" +"設計地在這次潤秒正確運作，就像在之前遇到潤秒時一樣。" + +#. (itstool) path: sect1/para +#: article.translate.xml:67 +msgid "" +"However, we caution that practically no applications have ever asked the " +"kernel about leap seconds. Our experience is that, as designed, leap seconds " +"are essentially a replay of the second before the leap second, and this is a " +"surprise to most application programmers." +msgstr "" +"然而我們要警告，實務上沒有應用程式曾經要求核心關於潤秒的事。我們的經驗是，如" +"同設計，潤秒本質上是潤秒前一秒的重播，這對大部份應用程式設計師來說是意想不到" +"的事。" + +#. (itstool) path: sect1/para +#: article.translate.xml:73 +msgid "" +"Other operating systems and other computers may or may not handle the leap-" +"second the same way as FreeBSD, and systems without correct and stable " +"NTP service will not know anything about leap seconds at " +"all." +msgstr "" +"其他作業系統或電腦可能會或可能不會像FreeBSD用同樣方法處理潤秒，沒有正確和穩定" +"NTP 服務的系統一點也不會知道潤秒的發生。" + +#. (itstool) path: sect1/para +#: article.translate.xml:78 +msgid "" +"It is not unheard of for computers to crash because of leap seconds, and " +"experience has shown that a large fraction of all public NTP servers might handle and announce the leap second incorrectly." +msgstr "" +"電腦因為潤秒而當機並不是沒有聽聞，經驗上也顯示，有大量公用的NTP 伺服器沒有正確地處理和公告潤秒。" + +#. (itstool) path: sect1/para +#: article.translate.xml:83 +msgid "" +"Please try to make sure nothing horrible happens because of the leap second." +msgstr "請試著確定不會因為潤秒而發生任何可怕的事情。" + +#. (itstool) path: sect1/title +#: article.translate.xml:88 +msgid "Testing" +msgstr "測試" + +#. (itstool) path: sect1/para +#: article.translate.xml:90 +msgid "" +"It is possible to test whether a leap second will be used. Due to the nature " +"of NTP, the test might work up to 24 hours before the " +"leap second. Some major reference clock sources only announce leap seconds " +"one hour ahead of the event. Query the NTP daemon:" +msgstr "" +"測試是否有使用潤秒是有可能的。由於 NTP的性質，測試可能要運" +"作到潤秒前24小時。有些主要的參考時鐘來源只在潤秒前一個小時公告。詢問" +"NTP行程：" + +#. (itstool) path: sect1/screen +#: article.translate.xml:96 +#, no-wrap +msgid "% ntpq -c 'rv 0 leap'" +msgstr "% ntpq -c 'rv 0 leap'" + +#. (itstool) path: sect1/para +#: article.translate.xml:98 +msgid "" +"Output that includes leap_add_sec indicates proper " +"support of the leap second. Before the 24 hours leading up to the leap " +"second, or after the leap second has passed, leap_none " +"will be shown." +msgstr "" +"包含leap_add_sec 的輸出指出對於潤秒的支援。潤秒前24小時，" +"或是潤秒已經過了，會顯示leap_none。" + +#. (itstool) path: sect1/title +#: article.translate.xml:105 +msgid "Conclusion" +msgstr "結論" + +#. (itstool) path: sect1/para +#: article.translate.xml:107 +msgid "" +"In practice, leap seconds are usually not a problem on FreeBSD. We hope that " +"this overview helps clarify what to expect and how to make the leap second " +"event proceed more smoothly." +msgstr "" +"實務上，FreeBSD 的潤秒通常不是個問題。我們希望這篇概述能幫助釐清預期會遇到什" +"麼狀況，如何使潤秒事件進行的更順利。" + +#~ msgid "$FreeBSD$" +#~ msgstr "$FreeBSD$"