aboutsummaryrefslogtreecommitdiff
path: root/zh_TW.UTF-8/articles
diff options
context:
space:
mode:
authorWarren Block <wblock@FreeBSD.org>2015-10-31 21:42:35 +0000
committerWarren Block <wblock@FreeBSD.org>2015-10-31 21:42:35 +0000
commit92dcfec3bfd332bc93b7bf876dc190c0ff23546e (patch)
tree4b3b6b18573345204bb2d9dd0129180fe9eb2151 /zh_TW.UTF-8/articles
parent4f25f34ddde1b52238574033851c042a23d251e4 (diff)
downloaddoc-92dcfec3bfd332bc93b7bf876dc190c0ff23546e.tar.gz
doc-92dcfec3bfd332bc93b7bf876dc190c0ff23546e.zip
Add a zh_TW translation of the leap seconds article by RayCherng Yu.
Submitted by: RayCherng Yu <raycherng@gmail.com>
Notes
Notes: svn path=/head/; revision=47717
Diffstat (limited to 'zh_TW.UTF-8/articles')
-rw-r--r--zh_TW.UTF-8/articles/leap-seconds/Makefile19
-rw-r--r--zh_TW.UTF-8/articles/leap-seconds/article.xml71
-rw-r--r--zh_TW.UTF-8/articles/leap-seconds/zh_TW.po240
3 files changed, 330 insertions, 0 deletions
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 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd">
+<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="leapseconds" xml:lang="zh_TW">
+
+ <info>
+ <title>FreeBSD 對潤秒的支援</title>
+
+ <pubdate>$FreeBSD$</pubdate>
+ </info>
+
+ <sect1 xml:id="leapseconds-definition">
+ <title>說明</title>
+
+ <para><emphasis>潤秒</emphasis>是為了同步地球自轉,與原子鐘所做的特定一秒的修正。本文描述FreeBSD 如何處理潤秒。</para>
+
+ <para>本文寫作時,下一個潤秒會發生在2015年6月30日23:59:60 CST。下一次潤秒會發生在南北美洲和亞太地區的工作日。</para>
+
+ <para>潤秒是由 <link xlink:href="http://datacenter.iers.org/"><acronym>IERS</acronym></link> 在 <link xlink:href="http://datacenter.iers.org/web/guest/bulletins/-/somos/5Rgv/product/16">Bulletin C</link>所發表。</para>
+
+ <para>標準的潤秒行為描述在<link xlink:href="https://tools.ietf.org/html/rfc7164#section-3">RFC 7164</link>.。也可見 <citerefentry><refentrytitle>time2posix</refentrytitle><manvolnum>3</manvolnum></citerefentry>。</para>
+ </sect1>
+
+ <sect1 xml:id="leapseconds-posix">
+ <title>FreeBSD預設的潤秒處理</title>
+
+ <para>The easiest way to handle leap seconds is with the
+ <acronym>POSIX</acronym> time rules FreeBSD uses by default,
+ combined with <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/network-ntp.html"><acronym>NTP</acronym></link>.
+ When <citerefentry><refentrytitle>ntpd</refentrytitle><manvolnum>8</manvolnum></citerefentry> is running and the time is synchronized with
+ upstream <acronym>NTP</acronym> 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.</para>
+
+ <para>如果上游的 <acronym>NTP</acronym> 伺服器無法正確地處理潤秒, <citerefentry><refentrytitle>ntpd</refentrytitle><manvolnum>8</manvolnum></citerefentry> 會在錯誤的上游伺服器發現錯誤並跳一秒後,跟著把時間跳一秒。</para>
+
+ <para>如果位使用 <acronym>NTP</acronym> ,將需要在潤秒過後,手動調整系統時鐘。</para>
+ </sect1>
+
+ <sect1 xml:id="leapseconds-cautions">
+ <title>警告</title>
+
+ <para>潤秒的插入在全世界是在同一個瞬間: <acronym>UTC</acronym> 午夜。在日本,是在上午九點,在太平洋,是正午,在美洲,是傍晚,在歐洲,是晚上。</para>
+
+ <para>我們相信和預期,如果提供正確和穩定的<acronym>NTP</acronym> 服務,FreeBSD會如設計地在這次潤秒正確運作,就像在之前遇到潤秒時一樣。</para>
+
+ <para>然而我們要警告,實務上沒有應用程式曾經要求核心關於潤秒的事。我們的經驗是,如同設計,潤秒本質上是潤秒前一秒的重播,這對大部份應用程式設計師來說是意想不到的事。</para>
+
+ <para>其他作業系統或電腦可能會或可能不會像FreeBSD用同樣方法處理潤秒,沒有正確和穩定<acronym>NTP</acronym> 服務的系統一點也不會知道潤秒的發生。</para>
+
+ <para>電腦因為潤秒而當機並不是沒有聽聞,經驗上也顯示,有大量公用的<acronym>NTP</acronym> 伺服器沒有正確地處理和公告潤秒。</para>
+
+ <para>請試著確定不會因為潤秒而發生任何可怕的事情。</para>
+ </sect1>
+
+ <sect1 xml:id="leapseconds-testing">
+ <title>測試</title>
+
+ <para>測試是否有使用潤秒是有可能的。由於 <acronym>NTP</acronym>的性質,測試可能要運作到潤秒前24小時。有些主要的參考時鐘來源只在潤秒前一個小時公告。詢問<acronym>NTP</acronym>行程:</para>
+
+ <screen><prompt>%</prompt> <userinput>ntpq -c 'rv 0 leap'</userinput></screen>
+
+ <para>包含<literal>leap_add_sec</literal> 的輸出指出對於潤秒的支援。潤秒前24小時,或是潤秒已經過了,會顯示<literal>leap_none</literal>。</para>
+ </sect1>
+
+ <sect1 xml:id="leapseconds-conclusion">
+ <title>結論</title>
+
+ <para>實務上,FreeBSD 的潤秒通常不是個問題。我們希望這篇概述能幫助釐清預期會遇到什麼狀況,如何使潤秒事件進行的更順利。</para>
+ </sect1>
+</article>
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 <EMAIL>, 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 <emphasis>leap second</emphasis> is an ad-hoc one-second correction to "
+"synchronize atomic timescales with Earth rotation. This article describes "
+"how FreeBSD interacts with leap seconds."
+msgstr ""
+"<emphasis>潤秒</emphasis>是為了同步地球自轉,與原子鐘所做的特定一秒的修正。本"
+"文描述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 <link xlink:href=\"http://datacenter.iers.org/"
+"\"><acronym>IERS</acronym></link> on <link xlink:href=\"http://datacenter."
+"iers.org/web/guest/bulletins/-/somos/5Rgv/product/16\">Bulletin C</link>."
+msgstr ""
+"潤秒是由 <link xlink:href=\"http://datacenter.iers.org/\"><acronym>IERS</"
+"acronym></link> 在 <link xlink:href=\"http://datacenter.iers.org/web/guest/"
+"bulletins/-/somos/5Rgv/product/16\">Bulletin C</link>所發表。"
+
+#. (itstool) path: sect1/para
+#: article.translate.xml:28
+msgid ""
+"Standard leap second behavior is described in <link xlink:href=\"https://"
+"tools.ietf.org/html/rfc7164#section-3\">RFC 7164</link>. Also see "
+"<citerefentry><refentrytitle>time2posix</refentrytitle><manvolnum>3</"
+"manvolnum></citerefentry>."
+msgstr ""
+"標準的潤秒行為描述在<link xlink:href=\"https://tools.ietf.org/html/"
+"rfc7164#section-3\">RFC 7164</link>.。也可見 "
+"<citerefentry><refentrytitle>time2posix</refentrytitle><manvolnum>3</"
+"manvolnum></citerefentry>。"
+
+#. (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 <acronym>POSIX</acronym> "
+"time rules FreeBSD uses by default, combined with <link xlink:href="
+"\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/network-ntp.html"
+"\"><acronym>NTP</acronym></link>. When <citerefentry><refentrytitle>ntpd</"
+"refentrytitle><manvolnum>8</manvolnum></citerefentry> is running and the "
+"time is synchronized with upstream <acronym>NTP</acronym> 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預設的 <acronym>POSIX</acronym> 時間規則,並使"
+"用 <link xlink:href=\"../../../../doc/zh_TW.UTF-8/books/handbook/network-ntp."
+"html\"><acronym>NTP</acronym></link>。如果 "
+"<citerefentry><refentrytitle>ntpd</refentrytitle><manvolnum>8</manvolnum></"
+"citerefentry> 在執行,而且時間和上游正確處理潤秒的 <acronym>NTP</acronym> 伺"
+"服器同步,潤秒會使系統時間自動重複當天的最後一秒。不需要其他調整。"
+
+#. (itstool) path: sect1/para
+#: article.translate.xml:44
+msgid ""
+"If the upstream <acronym>NTP</acronym> servers do not handle leap seconds "
+"correctly, <citerefentry><refentrytitle>ntpd</refentrytitle><manvolnum>8</"
+"manvolnum></citerefentry> will step the time by one second after the errant "
+"upstream server has noticed and stepped itself."
+msgstr ""
+"如果上游的 <acronym>NTP</acronym> 伺服器無法正確地處理潤秒, "
+"<citerefentry><refentrytitle>ntpd</refentrytitle><manvolnum>8</manvolnum></"
+"citerefentry> 會在錯誤的上游伺服器發現錯誤並跳一秒後,跟著把時間跳一秒。"
+
+#. (itstool) path: sect1/para
+#: article.translate.xml:49
+msgid ""
+"If <acronym>NTP</acronym> is not being used, manual adjustment of the system "
+"clock will be required after the leap second has passed."
+msgstr ""
+"如果位使用 <acronym>NTP</acronym> ,將需要在潤秒過後,手動調整系統時鐘。"
+
+#. (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: "
+"<acronym>UTC</acronym> midnight. In Japan that is mid-morning, in the "
+"Pacific mid-day, in the Americas late afternoon, and in Europe at night."
+msgstr ""
+"潤秒的插入在全世界是在同一個瞬間: <acronym>UTC</acronym> 午夜。在日本,是在"
+"上午九點,在太平洋,是正午,在美洲,是傍晚,在歐洲,是晚上。"
+
+#. (itstool) path: sect1/para
+#: article.translate.xml:62
+msgid ""
+"We believe and expect that FreeBSD, if provided correct and stable "
+"<acronym>NTP</acronym> service, will work as designed during this leap "
+"second, as it did during the previous ones."
+msgstr ""
+"我們相信和預期,如果提供正確和穩定的<acronym>NTP</acronym> 服務,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 "
+"<acronym>NTP</acronym> service will not know anything about leap seconds at "
+"all."
+msgstr ""
+"其他作業系統或電腦可能會或可能不會像FreeBSD用同樣方法處理潤秒,沒有正確和穩定"
+"<acronym>NTP</acronym> 服務的系統一點也不會知道潤秒的發生。"
+
+#. (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 <acronym>NTP</"
+"acronym> servers might handle and announce the leap second incorrectly."
+msgstr ""
+"電腦因為潤秒而當機並不是沒有聽聞,經驗上也顯示,有大量公用的<acronym>NTP</"
+"acronym> 伺服器沒有正確地處理和公告潤秒。"
+
+#. (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 <acronym>NTP</acronym>, 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 <acronym>NTP</acronym> daemon:"
+msgstr ""
+"測試是否有使用潤秒是有可能的。由於 <acronym>NTP</acronym>的性質,測試可能要運"
+"作到潤秒前24小時。有些主要的參考時鐘來源只在潤秒前一個小時公告。詢問"
+"<acronym>NTP</acronym>行程:"
+
+#. (itstool) path: sect1/screen
+#: article.translate.xml:96
+#, no-wrap
+msgid "<prompt>%</prompt> <userinput>ntpq -c 'rv 0 leap'</userinput>"
+msgstr "<prompt>%</prompt> <userinput>ntpq -c 'rv 0 leap'</userinput>"
+
+#. (itstool) path: sect1/para
+#: article.translate.xml:98
+msgid ""
+"Output that includes <literal>leap_add_sec</literal> indicates proper "
+"support of the leap second. Before the 24 hours leading up to the leap "
+"second, or after the leap second has passed, <literal>leap_none</literal> "
+"will be shown."
+msgstr ""
+"包含<literal>leap_add_sec</literal> 的輸出指出對於潤秒的支援。潤秒前24小時,"
+"或是潤秒已經過了,會顯示<literal>leap_none</literal>。"
+
+#. (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$"