aboutsummaryrefslogtreecommitdiff
path: root/zh_CN.UTF-8/articles
diff options
context:
space:
mode:
authorRuey-Cherng Yu <rcyu@FreeBSD.org>2017-07-27 15:12:33 +0000
committerRuey-Cherng Yu <rcyu@FreeBSD.org>2017-07-27 15:12:33 +0000
commit366e6251c0c610d7feca3ee2abfa2edbb0b6fbc5 (patch)
treec5886972311a3616d63946a58678630fd8fd4d38 /zh_CN.UTF-8/articles
parent1d182cc3afd047ac5306bb806658262f126537e9 (diff)
downloaddoc-366e6251c0c610d7feca3ee2abfa2edbb0b6fbc5.tar.gz
doc-366e6251c0c610d7feca3ee2abfa2edbb0b6fbc5.zip
Simplified Chinese Translation of the leap seconds article
Submitted by: Guangyuan (Charlie) Yang <cyang@freebsdfoundation.org> Reviewed by: delphij Differential Revision: https://reviews.freebsd.org/D11739
Notes
Notes: svn path=/head/; revision=50588
Diffstat (limited to 'zh_CN.UTF-8/articles')
-rw-r--r--zh_CN.UTF-8/articles/leap-seconds/Makefile19
-rw-r--r--zh_CN.UTF-8/articles/leap-seconds/article.xml64
-rw-r--r--zh_CN.UTF-8/articles/leap-seconds/zh_CN.po236
3 files changed, 319 insertions, 0 deletions
diff --git a/zh_CN.UTF-8/articles/leap-seconds/Makefile b/zh_CN.UTF-8/articles/leap-seconds/Makefile
new file mode 100644
index 0000000000..890b94f26e
--- /dev/null
+++ b/zh_CN.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_CN.UTF-8/articles/leap-seconds/article.xml b/zh_CN.UTF-8/articles/leap-seconds/article.xml
new file mode 100644
index 0000000000..aebd3c643a
--- /dev/null
+++ b/zh_CN.UTF-8/articles/leap-seconds/article.xml
@@ -0,0 +1,64 @@
+<?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_CN">
+
+ <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 UTC。这个闰秒将会发生在南北美洲和亚太地区的一个工作日里。</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>处理闰秒最简单的方法是使用 FreeBSD 预设的 <acronym>POSIX</acronym> 时间规则, 以及 <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/network-ntp.html"><acronym>NTP</acronym></link>。如果 <citerefentry><refentrytitle>ntpd</refentrytitle><manvolnum>8</manvolnum></citerefentry> 正在运行,并且时间和正确处理闰秒的上游 <acronym>NTP</acronym> 服务器同步,闰秒将使系统时间自动重复当天的最后一秒。不需要进行其它调整。</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> 的输出表明了对于闰秒的正确支持。<literal>leap_none</literal> 会在闰秒前24小时或闰秒过后显示。</para>
+ </sect1>
+
+ <sect1 xml:id="leapseconds-conclusion">
+ <title>结论</title>
+
+ <para>在实践中,FreeBSD 中的闰秒通常不是个问题。我们希望这篇文章能解释清楚这方面可能出现的状况,以及如何使闰秒事件进行得更顺利。</para>
+ </sect1>
+</article>
diff --git a/zh_CN.UTF-8/articles/leap-seconds/zh_CN.po b/zh_CN.UTF-8/articles/leap-seconds/zh_CN.po
new file mode 100644
index 0000000000..4f9f630209
--- /dev/null
+++ b/zh_CN.UTF-8/articles/leap-seconds/zh_CN.po
@@ -0,0 +1,236 @@
+# $FreeBSD$
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"POT-Creation-Date: 2017-07-27 01:48-0400\n"
+"PO-Revision-Date: 2017-07-27 01:47-0400\n"
+"Last-Translator: \n"
+"Language-Team: \n"
+"Language: zh_CN\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: Poedit 1.8.4\n"
+
+#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
+msgctxt "_"
+msgid "translator-credits"
+msgstr ""
+
+#. (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 UTC。这个闰秒将会发"
+"生在南北美洲和亚太地区的一个工作日里。"
+
+#. (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
+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=\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/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> 的输出表明了对于闰秒的正确支持。"
+"<literal>leap_none</literal> 会在闰秒前24小时或闰秒过后显示。"
+
+#. (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 中的闰秒通常不是个问题。我们希望这篇文章能解释清楚这方面可"
+"能出现的状况,以及如何使闰秒事件进行得更顺利。"