[svnbook] r5803 committed - branches/1.8/zh/book/ ch06-server-configuration.xml

[wuzhouhui at users.sourceforge.net]

Revision: 5803
          http://sourceforge.net/p/svnbook/source/5803
Author:   wuzhouhui
Date:     2018-10-17 14:57:24 +0000 (Wed, 17 Oct 2018)
Log Message:
-----------
1.8/zh: translation of chapter 6 in progress

Modified Paths:
--------------
    branches/1.8/zh/book/ch06-server-configuration.xml

Modified: branches/1.8/zh/book/ch06-server-configuration.xml
===================================================================
--- branches/1.8/zh/book/ch06-server-configuration.xml	2018-10-15 05:02:18 UTC (rev 5802)
+++ branches/1.8/zh/book/ch06-server-configuration.xml	2018-10-17 14:57:24 UTC (rev 5803)
@@ -7159,15 +7159,24 @@
       目录, 但允许少数用户读取. 访问规则的精细程度甚至可以细致到单个文件.
     </para>
 
+      <!--
     <para>Both Subversion servers use a common file format to describe
       these path-based access rules.  In this section, we will
       explain that file format, as well how to configure your
       Subversion server to use it for managing path-based
       authorization.</para>
+      -->
+    <para>Apache 和 <command>svnserve</command> 使用相同的文件格式描述基于
+      路径的访问规则. 本节我们将介绍文件的格式, 以及如何配置 Subversion 服务
+      器, 以便利用规则文件管理基于路径的授权.</para>
 
     <sidebar>
+      <!--
       <title>Do You Really Need Path-Based Access Control?</title>
+      -->
+      <title>你是否真得需要基于路径的访问控制?</title>
 
+      <!--
       <para>A lot of administrators setting up Subversion for the
         first time tend to jump into path-based access control without
         giving it a lot of thought.  The administrator usually knows
@@ -7176,6 +7185,11 @@
         directories and not others.  It seems like a natural thing,
         and it appeases the administrator's desire to maintain tight
         control of the repository.</para>
+      -->
+      <para>很多管理员在第一次配置 Subversion 时, 就急不可待地开始设置基于
+        路径的授权. 管理员通常知道团队成员与项目的对应关系, 所以很容易就能
+        决定应该把特定目录的权限授予给哪些人, 不授予给哪些人. 乍看起来非常
+        自然, 还可以缓解管理员过度控制仓库的欲望.</para>
 
       <para>Note, though, that there are often invisible (and
         visible!) costs associated with this feature.  In the visible