[svnbook] r5430 committed - branches/1.8/zh/book/ch03-advanced-topics.xml

[wuzhouhui at users.sourceforge.net]

Revision: 5430
          http://sourceforge.net/p/svnbook/source/5430
Author:   wuzhouhui
Date:     2017-09-19 13:49:19 +0000 (Tue, 19 Sep 2017)
Log Message:
-----------
1.8/zh: translation of chapter 3 in progress

Modified Paths:
--------------
    branches/1.8/zh/book/ch03-advanced-topics.xml

Modified: branches/1.8/zh/book/ch03-advanced-topics.xml
===================================================================
--- branches/1.8/zh/book/ch03-advanced-topics.xml	2017-09-18 12:51:56 UTC (rev 5429)
+++ branches/1.8/zh/book/ch03-advanced-topics.xml	2017-09-19 13:49:19 UTC (rev 5430)
@@ -8931,6 +8931,7 @@
           --message</option> (<option>-m</option>), 如果这两个选项都没有指定,
         客户端就会提示用户输入日志消息.</para>
 
+      <!--
       <para>Finally, there are a number of operations related to
         unversioned revision properties which can be performed
         directly against the repository.  In fact, revision properties
@@ -8939,13 +8940,23 @@
         modified without working copy interaction.  See
         <xref linkend="svn.advanced.props" /> for a more detailed
         description of how to manage properties in Subversion.</para>
+      -->
+      <para>最后, 很多与版本号属性相关的操作都可以直接对仓库发起. 实际上, 这
+        里谈到的版本号属性比较独特, 因为它们不是存放在工作副本里, 所以它们
+        <emphasis>必须</emphasis> 在不与工作副本交互的情况下修改. 关于如何管理
+        Subversion 属性的更多信息, 见 <xref linkend="svn.advanced.props"/>.
+      </para>
 
     </sect2>
 
     <!-- =============================================================== -->
     <sect2 id="svn.advanced.working-without-a-wc.svnmucc">
+      <!--
       <title>Using svnmucc</title>
+      -->
+      <title>使用 svnmucc</title>
 
+      <!--
       <para>One shortcoming of the remote commit operation support
         offered in the command-line client is that you are essentially
         limited to one operation—or, really, one type of
@@ -8964,12 +8975,27 @@
         new revision that removed the directory; <command>svn
         mkdir <replaceable>URL</replaceable></command> would generate
         a second revision for the directory's re-creation.</para>
+      -->
+      <para>客户端命令行工具的远程提交操作的一个缺点是用户每次提交只能执行一
+        个操作—或者说一种类型的操作. 比如说在一个工作副本内, 为了用一个
+        全新的目录替换掉旧目录, 先执行 <command>svn delete</command>, 再执行
+        <command>svn mkdir</command>—是一个很自然的操作. 当用户提交这两
+        个操作的执行结果时, 仓库将创建一个新的版本号, 该版本号完整地记录了这两
+        个操作. 但是客户端命令行的远程操作不能在单个版本号中完成这两步操作
+        —<command>svn delete <replaceable>URL</replaceable></command>
+        会创建一个新的版本号并删除目录; <command>svn mkdir <replaceable>URL
+      </replaceable></command> 会在第二个版本号中完成目录的创建.</para>
 
+      <!--
       <para>Fortunately, Subversion provides a separate tool which
         exists solely to allow users to string together a set of
         remote operations and commit them as one atomic change.  That
         tool is the <command>svnmucc</command> tool—the
         Subversion Multiple URL Command Client:</para>
+      -->
+      <para>幸运的是, Subversion 另外提供了一个工具, 用于把多个远程操作放在一
+        个提交中完成, 这个工具是 <command>svnmucc</command>—Subversion
+        多 URL 命令客户端 (Multiple URL Command Client):</para>
 
       <informalexample>
         <screen>