[svnbook] r5920 committed - branches/1.8/zh/book/ref-svn.xml

wuzhouhui at users.sourceforge.net wuzhouhui at users.sourceforge.net
Sun May 19 22:24:06 CDT 2019


Revision: 5920
          http://sourceforge.net/p/svnbook/source/5920
Author:   wuzhouhui
Date:     2019-05-20 03:24:04 +0000 (Mon, 20 May 2019)
Log Message:
-----------
1.8/zh: svn reference translated, but review needed

Modified Paths:
--------------
    branches/1.8/zh/book/ref-svn.xml

Modified: branches/1.8/zh/book/ref-svn.xml
===================================================================
--- branches/1.8/zh/book/ref-svn.xml	2019-05-19 13:25:12 UTC (rev 5919)
+++ branches/1.8/zh/book/ref-svn.xml	2019-05-20 03:24:04 UTC (rev 5920)
@@ -9296,9 +9296,11 @@
           命令 <command>svn cat</command>—它不会修改工作副本.</para>
       </tip>
 
+      <!--
       <para><command>svn update</command> is also the primary
         mechanism used to configure sparse working copies.  When
-        used with the <option>--set-depth</option>, the update
+        used with the <option>- -set-depth</option>, the update
+                               ### TODO
         operation will omit or reenlist individual working copy
         members by modifying their recorded ambient depth to the
         depth you specify (fetching information from the
@@ -9305,12 +9307,23 @@
         repository as necessary).  See
         <xref linkend="svn.advanced.sparsedirs" /> for more about
         sparse directories.</para>
+      -->
+      <para><command>svn update</command> 还是配置稀疏工作副本的主要命令.
+        如果指定了选项 <option>--set-depth</option>, 命令将会把工作副本路径
+        的周围深度修改成用户指定的深度, 从而忽略或延伸工作副本路径 (必要时
+        将从仓库中抓取数据). 关于稀疏目录的更多信息, 见
+        <xref linkend="svn.advanced.sparsedirs" />.</para>
       
+      <!--
       <para>You can update multiple targets with a single
         invocation, and Subversion will not only gracefully skip
         any unversioned targets you provide it, but as of
         Subversion 1.7 will also include a post-update summary of
         all the updates it performed:</para>
+      -->
+      <para>用户可以只调用一次 <command>svn update</command> 就能更新多个
+        目录, Subversion 不仅会忽略不被版本控制的目标, 如果是 Subversion 1.7,
+        它还会在最后打印一段总结信息:</para>
 
       <informalexample>
         <screen>
@@ -9353,8 +9366,11 @@
 
     <refnamediv>
       <refname>svn upgrade</refname>
+      <!--
       <refpurpose>Upgrade the metadata storage format for a
         working copy.</refpurpose>
+      -->
+      <refpurpose>更新工作副本的元数据格式.</refpurpose>
     </refnamediv>
 
     <refsynopsisdiv>
@@ -9363,8 +9379,12 @@
 
     <!-- =============================================================== -->
     <refsect1>
+      <!--
       <title>Description</title>
+      -->
+      <title>描述</title>
 
+      <!--
       <para>As new versions of Subversion are released, the format
         used for the working copy metadata changes to accomodate
         new features or fix bugs.  Older versions of Subversion
@@ -9374,11 +9394,21 @@
         working copy upgrades must be explicitly performed at the
         user's request.  <command>svn upgrade</command> is the
         subcommand used to trigger that upgrade process.</para>
+      -->
+      <para>随着新版 Subversion 的发布, 为了适应新版所添加的特性或为了修复
+        问题, 工作副本的元数据格式可能会发生变化. 在 Subversion 1.7 之前,
+        新版 Subversion 在首次使用旧版 Subversion 所创建的工作副本时, 将会
+        自动升级工作副本的元数据格式. 但是从 Subversion 1.7 开始, 用户必须
+        通过执行命令 <command>svn upgrade</command> 来显式地请求 Subversion
+        去更新工作副本的元数据格式.</para>
     </refsect1>
 
     <!-- =============================================================== -->
     <refsect1>
+      <!--
       <title>Options</title>
+      -->
+      <title>选项</title>
 
       <informalexample>
         <screen>
@@ -9389,11 +9419,18 @@
 
     <!-- =============================================================== -->
     <refsect1>
+      <!--
       <title>Examples</title>
+      -->
+      <title>示例</title>
 
+      <!--
       <para>If you attempt to use Subversion 1.7 on a working copy
         created with an older version of Subversion, you will see
         an error:</para>
+      -->
+      <para>如果你试图在一个版本较旧的工作副本中使用 Subversion 1.7, Subversion
+        将会报告:</para>
 
       <informalexample>
         <screen>
@@ -9405,9 +9442,13 @@
 </screen>
       </informalexample>
 
+      <!--
       <para>Use the <command>svn upgrade</command> command to
         upgrade the working copy to the most recent metadata
         format supported by your version of Subversion.</para>
+      -->
+      <para>这时候就需要执行 <command>svn upgrade</command> 把工作副本的元数据
+        格式升级到当前 Subversion 所支持的格式:</para>
 
       <informalexample>
         <screen>
@@ -9429,17 +9470,26 @@
 </screen>
       </informalexample>
 
+      <!--
       <para>Notice that <command>svn upgrade</command> preserved
         the local modifications present in the working copy at the
         time of the upgrade, which were introduced by the version
         of Subversion previously used to manipulate this working
         copy.</para>
+      -->
+      <para>注意, <command>svn upgrade</command> 会保留工作副本的本地修改,
+        即使这些修改是由旧版 Subversion 引入的 (例如 <command>svn
+          mv</command>).</para>
 
       <warning>
+      <!--
         <para>As was the case with automatically upgraded working
           copies in the past, explicitly upgraded working copies
           will be unusable by older versions of Subversion,
           too.</para>
+      -->
+        <para>和过去自动升级工作副本元数据的行为相比, 显式地升级工作副本
+          元数据后, 旧的 Subversion 将不再支持升级后的工作副本.</para>
       </warning>
       
     </refsect1>




More information about the svnbook-dev mailing list