[svnbook] r5322 committed - branches/1.8/zh/book
wuzhouhui at users.sourceforge.net
wuzhouhui at users.sourceforge.net
Fri Jun 9 21:00:51 CDT 2017
Revision: 5322
http://sourceforge.net/p/svnbook/source/5322
Author: wuzhouhui
Date: 2017-06-10 02:00:50 +0000 (Sat, 10 Jun 2017)
Log Message:
-----------
Branch 1.8/zh: cover and foreword translated.
Modified Paths:
--------------
branches/1.8/zh/book/book.xml
branches/1.8/zh/book/foreword.xml
Modified: branches/1.8/zh/book/book.xml
===================================================================
--- branches/1.8/zh/book/book.xml 2017-06-08 10:18:27 UTC (rev 5321)
+++ branches/1.8/zh/book/book.xml 2017-06-10 02:00:50 UTC (rev 5322)
@@ -42,15 +42,24 @@
]>
<book id="svn">
+ <!--
<title>Version Control with Subversion [DRAFT]</title>
+ -->
+ <title>Subversion 版本控制 [草稿]</title>
<bookinfo>
+ <!--
<subtitle>For Subversion 1.8</subtitle>
+ -->
+ <subtitle>针对 Subversion 1.8</subtitle>
<!-- Using revnumber would be more appropriate, but our stylesheets -->
<!-- don't seem to render it. -->
+ <!--
<subtitle>(Compiled from &svn.l10n_revision;&svn.version;)</subtitle>
+ -->
+ <subtitle>(编译自 &svn.l10n_revision;&svn.version;)</subtitle>
<!--
<edition>Second</edition>
@@ -107,12 +116,23 @@
<holder>C. Michael Pilato</holder>
</copyright>
+ <!--
<legalnotice><para>This work is licensed under the Creative
Commons Attribution License. To view a copy of this license,
visit <ulink url="http://creativecommons.org/licenses/by/2.0/"/>
or send a letter to Creative Commons, 559 Nathan Abbott Way,
Stanford, California 94305, USA.</para></legalnotice>
+ -->
+ <legalnotice><para>本书使用创作共享署名授权协议 (Creative Commons
+ Attribution License), 访问网站
+ <ulink url="http://creativecommons.org/licenses/by/2.0/"/> 或写信到
+ Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305,
+ USA, 阅读协议的副本.</para>
+ <para> 本书英文版和中文版的源代码托管在
+ <ulink url="https://sourceforge.net/projects/svnbook/"/>.
+ </para></legalnotice>
+
</bookinfo>
<!-- External entity refs -->
Modified: branches/1.8/zh/book/foreword.xml
===================================================================
--- branches/1.8/zh/book/foreword.xml 2017-06-08 10:18:27 UTC (rev 5321)
+++ branches/1.8/zh/book/foreword.xml 2017-06-10 02:00:50 UTC (rev 5322)
@@ -7,22 +7,37 @@
<firstname>Karl</firstname>
<surname>Fogel</surname>
</author>
+ <!--
<pubdate>Chicago, March 14, 2004.</pubdate>
+ -->
+ <pubdate>2004 年 3 月 14 日, 芝加哥</pubdate>
</prefaceinfo>
+ <!--
<title>Foreword</title>
+ -->
+ <title>写在前面</title>
+ <!--
<para>A bad Frequently Asked Questions (FAQ) sheet is one that is
composed not of the questions people actually ask, but of the
questions the FAQ's author <emphasis>wishes</emphasis> people
would ask. Perhaps you've seen the type before:</para>
+ -->
+ <para>一个差劲的常见问题列表 (Frequently Asked Questions, FAQ) 总是充斥着
+ 作者希望听到的问题, 而不是人们真正想问的问题. 读者可能遇到过下面这种类型
+ 的问题:</para>
<blockquote>
+ <!--
<para>Q: How can I use Glorbosoft XYZ to maximize team
productivity?</para>
+ -->
+ <para>Q: 如何使用 Glorbosoft XYZ 才能最大程序地提高团队效率?</para>
</blockquote>
<blockquote>
+ <!--
<para>A: Many of our customers want to know how they can
maximize productivity through our patented office groupware
innovations. The answer is simple. First, click on the
@@ -29,8 +44,13 @@
<literal>File</literal> menu, scroll down to
<literal>Increase Productivity</literal>,
then…</para>
+ -->
+ <para>A: 很多客户想知道如何利用我们的革命性办公套件最大程序地提高
+ 效率, 答案非常简单, 首先, 点击菜单项 <literal>File</literal>, 滚动到
+ <literal>Increase Productivity</literal>, 然后 …</para>
</blockquote>
+ <!--
<para>The problem with such FAQs is that they are not, in a
literal sense, FAQs at all. No one ever called the tech support
line and asked, <quote>How can we maximize
@@ -47,7 +67,18 @@
observant attitude of a field naturalist. No grand
hypothesizing, no visionary pronouncements here—open eyes
and accurate note-taking are what's needed most.</para>
+ -->
+ <para>这种问题完全不符合 FAQ 的精神. 没人会打电话给技术支持中心询问 <quote>
+ 怎么提交生产效率</quote>, 相反, 人们经常问一些非常具体的问题, 例如
+ <quote>怎样做才能让日历系统提前两天—而不是一天—提醒相关用户
+ </quote>, 但是编撰 FAQ 比发现真正的问题要容易得多. 构建一张真实的 FAQ 列
+ 表需要持之以恒的辛勤工作: 在软件的整个生命周期中, 需要跟踪每一个收到的
+ 问题, 监控反馈信息, 所有的问题要整理成一个统一的, 可查询的整体, 并且能
+ 够真实地反映出用户的感受. 这个过程非常需要耐心, 如自然学家一样严谨的态度,
+ 没有浮华的假设, 没有虚幻的断言—最重要的是要有开放的视野和精确的记录.
+ </para>
+ <!--
<para>What I love about this book is that it grew out of just such
a process, and shows it on every page. It is the direct result
of the authors' encounters with users. It began with Ben
@@ -56,7 +87,14 @@
what are the standard workflows to use with Subversion? Do
branches and tags work the same way as in other version control
systems? How can I find out who made a particular change?</para>
+ -->
+ <para>我喜欢这本书的原因是它正是按照这种过程写出来的. 本书是作者和用户直接
+ 交互的结果, 而这一切是源于 Ben Collins-Sussman 对于 Subversion 邮件列表
+ 中常见问题的研究, 他发现人们总是在邮件列表中重复询问基本问题: 使用
+ Subversion 的标准流程是什么? 分支 (branch) 与标签 (tag) 的工作方式同其他
+ 版本控制系统一样吗? 我怎么才能知道某处修改是谁做的?</para>
+ <!--
<para>Frustrated at seeing the same questions day after day, Ben
worked intensely over a month in the summer of 2002 to write
<citetitle>The Subversion Handbook</citetitle>, a 60-page
@@ -67,7 +105,15 @@
publish a full-length Subversion book, the path of least
resistance was obvious: just expand the Subversion
handbook.</para>
+ -->
+ <para>日复一日看到相同问题的烦闷, 促使 Ben 在 2002 年的夏天努力了一个月,
+ 写了一本 <citetitle>The Subversion Handbook</citetitle>, 这是一本 60 页
+ 厚的, 涵盖了 Subversion 所有的基础使用知识. 手册没有说明定稿的最终时间,
+ 但它随着 Subversion 的每个版本一起发布, 帮助过很多用户跨过学习之初的艰难.
+ 当 O'Reilly 决定出版一本详尽的 Subversion 图书时, 扩充手册是最快的捷径.
+ </para>
+ <!--
<para>The three coauthors of the new book were thus presented
with an unusual opportunity. Officially, their task was to
write a book top-down, starting from a table of contents and an
@@ -77,7 +123,13 @@
thousands of early adopters, and those users were giving tons of
feedback, not only about Subversion, but also about its existing
documentation.</para>
+ -->
+ <para>新书的三位作者面临着一个不寻常的机会, 从职责上讲, 他们的任务是以目录
+ 和草稿为基础, 自上而下地写出一部著. 但事实上, 他们的灵感来自一些非常具体
+ 的内容, 稳定却难以组织—Subversion 被数以千计早期用户使用, 他们提供
+ 了大量的反馈, 这些反馈不仅仅针对 Subversion, 还包括它的文档.</para>
+ <!--
<para>During the entire time they wrote this book, Ben, Mike, and
Brian haunted the Subversion mailing lists and chat rooms
incessantly, carefully noting the problems users were having in
@@ -98,7 +150,19 @@
with the unexpected, the examples honed from genuine use cases,
and most of all the sensitivity to the user's needs and the
user's point of view.</para>
+ -->
+ <para>在本书的写作过程中, Ben, Mike 和 Brian 像鬼魂一样游荡在 Subversion
+ 的邮件列表和聊天室里, 仔细地研究用户遇到的实际问题, 监控反馈信息也是他
+ 们在 CollabNet 的工作内容之一, 这给他们撰写 Subversion 文档提供了巨大的便
+ 利. 本书建立在丰富的使用经验上, 而不是流水般脆弱的想像, 它结合了用户手册
+ 和 FAQ 的优点, 初次阅读时, 这种二元性的优势可能并不明显. 从表面上看,
+ 本书只是从头到尾地描述了软件的细节, 书中的内容包括一章概述, 一章不可或缺
+ 的快速指南, 一章关于管理配置, 一些高级主题, 当然还包括命令参考手册和故障
+ 排除指南. 当你过一段时间后, 再次翻开本书查找一些特定问题的答案时, 这种二
+ 元性才得以显现: 书中生动的细节一定是来自不可预测的实际用例的提炼, 大多数
+ 内容是源于用户的需求和视点.</para>
+ <!--
<para>Of course, no one can promise that this book will answer
every question you have about Subversion. Sometimes the
precision with which it anticipates your questions will seem
@@ -117,8 +181,20 @@
because you can help them. With Subversion, as with all active
free software projects, <emphasis>you are not
alone</emphasis>.</para>
+ -->
+ <para>当然, 没人可以承诺本书可以回答你的所有问题. 尽管有时候一些前人提问
+ 的惊人一致性让你感觉是心灵感应, 你仍有可能在社区的知识库里摔跤, 空手而
+ 归. 如果有这种情况发生, 最好的办法是把问题发送到
+ <email>users at subversion.apache.org</email>, 作者还在那里关注着社区, 不
+ 仅仅是本书的三位作者, 还包括许多曾经作出修正与提供原始材料的人. 从社区
+ 的视角看, 帮你解决问题也是为了改进本书和 Subversion. 他们渴望你的信息,
+ 不仅仅可以帮助你, 也可以帮助他们. 与 Subversion 这样活跃的自由软件项目
+ 在一起, 你不会孤军奋战.</para>
+ <!--
<para>Let this book be your first companion.</para>
+ -->
+ <para>希望本书能成为你的好伙伴.</para>
</preface>
More information about the svnbook-dev
mailing list