[svnbook] r6010 committed - branches/1.8/zh
wuzhouhui at users.sourceforge.net
wuzhouhui at users.sourceforge.net
Mon Nov 4 14:51:11 UTC 2019
Revision: 6010
http://sourceforge.net/p/svnbook/source/6010
Author: wuzhouhui
Date: 2019-11-04 14:51:11 +0000 (Mon, 04 Nov 2019)
Log Message:
-----------
1.8/zh: merge and translate changes from trunk
Modified Paths:
--------------
branches/1.8/zh/book/appa-quickstart.xml
branches/1.8/zh/book/appb-svn-for-cvs-users.xml
branches/1.8/zh/book/appc-webdav.xml
branches/1.8/zh/book/appd-berkeley-db.xml
branches/1.8/zh/book/ch02-basic-usage.xml
branches/1.8/zh/book/ch03-advanced-topics.xml
branches/1.8/zh/book/ch05-repository-admin.xml
branches/1.8/zh/book/ref-reposhooks.xml
branches/1.8/zh/book/ref-svn.xml
branches/1.8/zh/book/ref-svnlook.xml
branches/1.8/zh/book/ref-svnmucc.xml
branches/1.8/zh/book/ref-svnrdump.xml
branches/1.8/zh/book/ref-svnserve.xml
branches/1.8/zh/book/ref-svnsync.xml
Property Changed:
----------------
branches/1.8/zh/
Index: branches/1.8/zh
===================================================================
--- branches/1.8/zh 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh 2019-11-04 14:51:11 UTC (rev 6010)
Property changes on: branches/1.8/zh
___________________________________________________________________
Modified: svn:mergeinfo
## -1 +1 ##
-/trunk/en:5303-5932
\ No newline at end of property
+/trunk/en:5303-6009
\ No newline at end of property
Modified: branches/1.8/zh/book/appa-quickstart.xml
===================================================================
--- branches/1.8/zh/book/appa-quickstart.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/appa-quickstart.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -47,27 +47,35 @@
APR—the Apache Portable Runtime library. The APR library
provides all the interfaces that Subversion needs to function on
different operating systems: disk access, network access, memory
- management, and so on. While Subversion is able to use Apache
- HTTP Server (or, <command>httpd</command>) as one of its network
- server programs, its dependence on APR <emphasis>does
- not</emphasis> mean that <command>httpd</command> is a required
- component. APR is a standalone library usable by any
- application. It does mean, however, that Subversion clients and
- servers run on any operating system
- that <command>httpd</command> runs on: Windows, Linux, all
- flavors of BSD, Mac OS X, NetWare, and others.</para>
+ management, and so on.
+ The abstraction layer provided by APR enables Subversion clients and
+ servers to run on any operating system that other APR-based applications
+ run on: Windows, Linux, all flavors of BSD, Mac OS X, NetWare, and
+ others.</para>
-->
<para>Subversion 构建在一个可移植函数库之上, 这个函数库叫做
APR (Apache Portable Runtime, Apache 可移植运行库). APR 提供了
Subversion 在不同操作系统平台上运行所需的各种接口: 磁盘访问, 网络访问,
- 内存管理等. 虽然 Apache HTTP 服务器 (或者说 <command>httpd</command>)
- 可以作为 Subversion 的网络服务器之一, 但是 Subversion 对 APR 的依赖并
- 不表明 <command>httpd</command> 也是它的必要组件. 然而这确实意味着只
- 要是能运行 <command>httpd</command> 的操作系统—例如 Windows,
- Linux, 所有的 BSD, Mac OS X 和 NetWare 等—都能运行
- Subversion.</para>
+ 内存管理等. 利用 APR 提供的抽象层, 只要是能运行基于 APR 的应用程序的
+ 操作系统—例如 Windows, Linux, 所有的 BSD, Mac OS X 和 NetWare 等
+ —都能运行 Subversion.</para>
+ <note>
<!--
+ <para>Although the APR library is part of the Apache HTTP Server (or,
+ <command>httpd</command>), and <command>httpd</command> can be
+ configured to serve Subversion repositories, <command>httpd</command>
+ is <emphasis>not</emphasis> a required component of a Subversion
+ installation.</para>
+ -->
+ <para>虽然 APR 函数库是 Apache HTTP 服务器 (即 <command>httpd</command>)
+ 的一部分, 并且 <command>httpd</command> 也可以作为 Subversion
+ 仓库的托管服务器, 但 <command>httpd</command> 并不是 Subversion 的
+ 必要组件, 即使你没有 <command>httpd</command>, 仍然可以安装
+ Subversion.</para>
+ </note>
+
+ <!--
<para>The easiest way to get Subversion is to download a binary
package built for your operating system. Subversion's web site
(<ulink url="http://subversion.apache.org"/>) often has these
@@ -240,7 +248,7 @@
linkend="svn.reposadmin"/>.</para>
<!--
- <para>Subversion has no concept of a <quote>project.</quote> The
+ <para>Subversion has no concept of a <quote>project</quote>. The
repository is just a virtual versioned filesystem, a large tree
that can hold anything you wish. Some administrators prefer to
store only one project in a repository, and others prefer to
@@ -249,7 +257,7 @@
in <xref linkend="svn.reposadmin.projects.chooselayout"/>.
Either way, the repository manages only files and directories,
so it's up to humans to interpret particular directories as
- <quote>projects.</quote> So while you might see references to
+ <quote>projects</quote>. So while you might see references to
projects throughout this book, keep in mind that we're only ever
talking about some directory (or collection of directories) in
the repository.</para>
Modified: branches/1.8/zh/book/appb-svn-for-cvs-users.xml
===================================================================
--- branches/1.8/zh/book/appb-svn-for-cvs-users.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/appb-svn-for-cvs-users.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -89,15 +89,15 @@
<para>Similarly, in CVS, a tag or branch is an annotation on the
file or on the version information for that individual file,
whereas in Subversion, a tag or branch is a copy of an entire
- tree (by convention, into the <filename>/branches</filename>
- or <filename>/tags</filename> directories that appear at the top
- level of the repository, beside <filename>/trunk</filename>). In
+ tree (by convention, into the <filename>branches/</filename>
+ or <filename>tags/</filename> directories that appear at the top
+ level of the repository, beside <filename>trunk/</filename>). In
the repository as a whole, many versions of each file may be
visible: the latest version on each branch, every tagged
version, and of course the latest version on the trunk
itself. So, to refine the terms even further, one would often
say <quote><filename>foo.c</filename> as it appears in
- <filename>/branches/REL1</filename> in revision
+ <filename>branches/REL1</filename> in revision
5.</quote></para>
-->
<para>类似的, 在 CVS 中, 标签和目录只不过是文件或文件版本信息上的注释,
@@ -616,7 +616,7 @@
组合, 它们可以被关联到工作副本的文件与目录上.</para>
<!--
- <para>To set or get a property name, use the <command>svn
+ <para>To set or get a property value, use the <command>svn
propset</command> and <command>svn propget</command>
subcommands. To list all properties on an object, use
<command>svn proplist</command>.</para>
Modified: branches/1.8/zh/book/appc-webdav.xml
===================================================================
--- branches/1.8/zh/book/appc-webdav.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/appc-webdav.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -75,7 +75,7 @@
committee was left with the responsibility of writing RFC 3253 a
few years later. The new RFC adds versioning concepts to
WebDAV, placing the <quote>V</quote> back in
- <quote>DAV</quote>—hence the term <quote>DeltaV.</quote>
+ <quote>DAV</quote>—hence the term <quote>DeltaV</quote>.
WebDAV/DeltaV clients and servers are often called just
<quote>DeltaV</quote> programs, since DeltaV implies the
existence of basic WebDAV.</para>
@@ -173,7 +173,7 @@
<!--
<para>A long-held debate in the Subversion developer community
- about whether it was worthfile to remedy either of these
+ about whether it was worthwhile to remedy either of these
situations eventually reached closure, with the Subversion
developers officially deciding to abandon plans to fully support
DeltaV. As of Subversion 1.7, Subversion clients and servers
@@ -935,7 +935,7 @@
system registry to turn off this behavior. Just change the
value of the <literal>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\BasicAuthLevel</literal>
key from <userinput>1</userinput> to <userinput>2</userinput>. A final warning: be sure to set up the Web
- Folder to point to the repository's root directory
+ Folders to point to the repository's root directory
(<filename>/</filename>), rather than some subdirectory
such as <filename>/trunk</filename>. Vista Web Folders
seems to work only against repository roots.</para>
@@ -1133,7 +1133,7 @@
<!--
<para>Linux davfs2 is a filesystem module for the Linux
kernel, whose development is organized at
- <ulink url="http://dav.sourceforge.net/"/>. Once you
+ <ulink url="http://savannah.nongnu.org/projects/davfs2"/>. Once you
install davfs2, you can mount a WebDAV network share using
the usual Linux mount command:</para>
-->
Modified: branches/1.8/zh/book/appd-berkeley-db.xml
===================================================================
--- branches/1.8/zh/book/appd-berkeley-db.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/appd-berkeley-db.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -685,7 +685,7 @@
<para>For more information on the Berkeley DB tool chain,
visit the documentation section of the Berkeley DB section
of Oracle's web site, located at <ulink
- url="http://www.oracle.com/technology/documentation/berkeley-db/db/"
+ url="https://docs.oracle.com/cd/E17275_01/html/api_reference/C/utilities.html"/>.
/>.</para>
-->
<para>关于 Berkeley DB 工具链的更多信息, 见 Oracle 维护的 Berkeley DB
Modified: branches/1.8/zh/book/ch02-basic-usage.xml
===================================================================
--- branches/1.8/zh/book/ch02-basic-usage.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/ch02-basic-usage.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -3209,7 +3209,7 @@
<!--
<para>Retrieves a human-readable file as it existed in a
particular revision number, displaying its contents in a
- tabular form with last-changed information attributed to
+ tabular form with last-changed information added to
each line of the file</para>
-->
<para>根据给定的版本号, 查看该版本下的文件的每一行的最后一
@@ -3565,7 +3565,7 @@
<command>svn commit</command> and the default behavior of
<command>svn log</command>. First, when you commit changes
to the repository, <command>svn</command> bumps only the
- revision of files (and directories) that it commits, so
+ revision number of files (and directories) that it commits, so
usually the parent directory remains at the older revision
(See
<xref linkend="svn.basic.in-action.mixedrevs.update-commit"/>
Modified: branches/1.8/zh/book/ch03-advanced-topics.xml
===================================================================
--- branches/1.8/zh/book/ch03-advanced-topics.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/ch03-advanced-topics.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -9250,7 +9250,7 @@
</blockquote>
<!--
- <para>Inherent in working-copy-less modifications is the loss of
+ <para>Inherent in modifications without a working copy is the loss of
the very conflict detection safeguards which make the use of a
working copy so valuable. When using <command>svn</command>
in the typical way, changes are committed to the server
Modified: branches/1.8/zh/book/ch05-repository-admin.xml
===================================================================
--- branches/1.8/zh/book/ch05-repository-admin.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/ch05-repository-admin.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -1116,8 +1116,8 @@
<!--
<para>The syntax of the <filename>hooks-env</filename> file is
pretty straightforward: each section name is the name of a
- hook script (such as <literal>pre-commit</literal>
- or <literal>post-revprop-change</literal>), and the
+ hook script (such as <literal>[pre-commit]</literal>
+ or <literal>[post-revprop-change]</literal>), and the
configuration items inside that section are treated as
mappings of environment variable names to desired values.
Additionally, there is a
Modified: branches/1.8/zh/book/ref-reposhooks.xml
===================================================================
--- branches/1.8/zh/book/ref-reposhooks.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/ref-reposhooks.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -249,7 +249,7 @@
<title>描述</title>
<!--
- <para>The <literal>pre-commit</literal> hook is run just
+ <para>The pre-commit hook is run just
before a commit transaction is promoted to a new revision.
Typically, this hook is used to protect against commits that
are disallowed due to content or location (e.g., your
@@ -263,7 +263,7 @@
能为空).</para>
<!--
- <para>If the <literal>pre-commit</literal> hook program
+ <para>If the pre-commit hook program
returns a nonzero exit value, the commit is aborted, the
commit transaction is removed, and anything printed to
<filename>stderr</filename> is marshalled back to the client.</para>
@@ -368,7 +368,7 @@
<title>描述</title>
<!--
- <para>The <literal>post-commit</literal> hook is run after the
+ <para>The post-commit hook is run after the
transaction is committed and a new revision is created. Most
people use this hook to send out descriptive emails about
the commit or to notify some other tool (such as an issue
@@ -381,7 +381,7 @@
生成. 有些管理员还会用 post-commit 触发备份操作.</para>
<!--
- <para>If the <literal>post-commit</literal> hook returns a
+ <para>If the post-commit hook returns a
nonzero exit status, the commit <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
@@ -480,7 +480,7 @@
<title>描述</title>
<!--
- <para>The <literal>pre-revprop-change</literal> hook is run
+ <para>The pre-revprop-change hook is run
immediately prior to the modification of a revision property
when performed outside the scope of a normal commit. Unlike
the other hooks, the default state of this one is to deny
@@ -494,7 +494,7 @@
版本号属性, pre-revprop-change 必须显式地以零作为退出值.</para>
<!--
- <para>If the <literal>pre-revprop-change</literal> hook doesn't
+ <para>If the pre-revprop-change hook doesn't
exist, isn't executable, or returns a nonzero exit value, no
change to the property will be made, and anything printed
to <filename>stderr</filename> is marshalled back to the
@@ -614,13 +614,13 @@
<title>描述</title>
<!--
- <para>The <literal>post-revprop-change</literal> hook is run
+ <para>The post-revprop-change hook is run
immediately after the modification of a revision property
when performed outside the scope of a normal commit. As you can
derive from the description of its counterpart, the
- <literal>pre-revprop-change</literal> hook, this hook will
+ pre-revprop-change hook, this hook will
not run at all unless
- the <literal>pre-revprop-change</literal> hook is
+ the pre-revprop-change hook is
implemented. It is typically used to send email
notification of the property change.</para>
-->
@@ -631,7 +631,7 @@
这个钩子的典型用途是发邮件通知版本号属性被修改了.</para>
<!--
- <para>If the <literal>post-revprop-change</literal> hook returns a
+ <para>If the post-revprop-change hook returns a
nonzero exit status, the change <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
@@ -751,7 +751,7 @@
<title>描述</title>
<!--
- <para>The <literal>pre-lock</literal> hook runs whenever
+ <para>The pre-lock hook runs whenever
someone attempts to lock a path. It can be used to prevent
locks altogether or to create a more complex policy
specifying exactly which users are allowed to lock
@@ -765,7 +765,7 @@
<quote>窃取</quote> 其他人的锁.</para>
<!--
- <para>If the <literal>pre-lock</literal> hook program returns
+ <para>If the pre-lock hook program returns
a nonzero exit value, the lock action is aborted and
anything printed to <filename>stderr</filename> is
marshalled back to the client.</para>
@@ -786,7 +786,7 @@
<warning>
<!--
- <para>If the <literal>pre-lock</literal> script takes
+ <para>If the pre-lock script takes
advantage of lock token dictation feature, the
responsibility of generating a <emphasis>unique</emphasis>
lock token falls to the script itself. Failure to
@@ -897,7 +897,7 @@
<title>描述</title>
<!--
- <para>The <literal>post-lock</literal> hook runs after one or
+ <para>The post-lock hook runs after one or
more paths have been locked. It is typically used to send
email notification of the lock event.</para>
-->
@@ -905,7 +905,7 @@
是发送路径被锁定的通知邮件.</para>
<!--
- <para>If the <literal>post-lock</literal> hook returns a
+ <para>If the post-lock hook returns a
nonzero exit status, the lock <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
@@ -1004,7 +1004,7 @@
<title>描述</title>
<!--
- <para>The <literal>pre-unlock</literal> hook runs whenever
+ <para>The pre-unlock hook runs whenever
someone attempts to remove a lock on a file. It can be used
to create policies that specify which users are allowed to
unlock particular paths. It's particularly important for
@@ -1019,7 +1019,7 @@
持有一周了呢? 这些考虑都可以放在钩子 pre-unlock 里实现.</para>
<!--
- <para>If the <literal>pre-unlock</literal> hook program
+ <para>If the pre-unlock hook program
returns a nonzero exit value, the unlock action is aborted
and anything printed to <filename>stderr</filename> is marshalled back to the
client.</para>
@@ -1124,7 +1124,7 @@
<title>描述</title>
<!--
- <para>The <literal>post-unlock</literal> hook runs after one
+ <para>The post-unlock hook runs after one
or more paths have been unlocked. It is typically used to
send email notification of the unlock event.</para>
-->
@@ -1132,7 +1132,7 @@
是发送路径被解锁的通知邮件.</para>
<!--
- <para>If the <literal>post-unlock</literal> hook returns a
+ <para>If the post-unlock hook returns a
nonzero exit status, the unlock <emphasis>will
not</emphasis> be aborted since it has already
completed. However, anything that the hook printed
Modified: branches/1.8/zh/book/ref-svn.xml
===================================================================
--- branches/1.8/zh/book/ref-svn.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/ref-svn.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -395,8 +395,8 @@
<replaceable>FILE</replaceable>:<replaceable>SECTION</replaceable>:<replaceable>OPTION</replaceable>=[<replaceable>VALUE</replaceable>].
In this syntax, <replaceable>FILE</replaceable>
and <replaceable>SECTION</replaceable> are the runtime
- configuration file (either <literal>config</literal>
- or <literal>servers</literal>) and the section thereof,
+ configuration file (either <filename>config</filename>
+ or <filename>servers</filename>) and the section thereof,
respectively, which contain the option whose value you
wish to change. <replaceable>OPTION</replaceable> is,
of course, the option itself,
Modified: branches/1.8/zh/book/ref-svnlook.xml
===================================================================
--- branches/1.8/zh/book/ref-svnlook.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/ref-svnlook.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -11,7 +11,7 @@
<para><command>svnlook</command> is a command-line utility for
examining different aspects of a Subversion repository. It
does not make any changes to the repository—it's just
- used for <quote>peeking.</quote>
+ used for <quote>peeking</quote>.
<command>svnlook</command> is typically used by the
repository hooks, but a repository administrator might find it
useful for diagnostic purposes.</para>
@@ -161,7 +161,7 @@
<para>The default value is <literal>-u</literal>.</para>
<para>Note that when Subversion is configured to invoke an
external diff command, the value of
- the <option>- -extension</option> (<option>-x</option>)
+ the <option>- -extensions</option> (<option>-x</option>)
option isn't restricted to the previously mentioned
options, but may be <emphasis>any</emphasis> additional
arguments which Subversion should pass to that command.
@@ -1080,13 +1080,15 @@
<!--
<para>Print the file size (in bytes) of the file located
- at <replaceable>PATH_IN_REPOS</replaceable> in the HEAD
+ at <replaceable>PATH_IN_REPOS</replaceable> in the
+ <literal>HEAD</literal>
revision of the repository identified
by <replaceable>REPOS_PATH</replaceable> as a base-10
integer followed by an end-of-line character. Use
the <option>- -revision</option> (<option>-r</option>)
and <option>- -transaction</option> (<option>-t</option>)
- options to specify a version of the file other than HEAD
+ options to specify a version of the file other than
+ <literal>HEAD</literal>
whose file size you wish to display.</para>
-->
<para>以字节为单位输出文件的大小, 文件位于仓库
@@ -1162,7 +1164,8 @@
<refsynopsisdiv>
<!--
- <para><literal>Also svnlook -h and svnlook -?.</literal></para>
+ <para>Also <literal>svnlook -h</literal> and <literal>svnlook
+ -?</literal>.</para>
-->
<para>还可以使用 <literal>svnlook -h</literal> 和
<literal>svnlook -?</literal> 这两种调用方式.</para>
@@ -1924,8 +1927,7 @@
<refnamediv>
<refname>svnlook uuid</refname>
<!--
- <refpurpose>Print the repository's
- <literal>UUID</literal>.</refpurpose>
+ <refpurpose>Print the repository's UUID.</refpurpose>
-->
<refpurpose>打印仓库的 UUID.</refpurpose>
</refnamediv>
@@ -1942,8 +1944,7 @@
<title>描述</title>
<!--
- <para>Print the <literal>UUID</literal> for the repository.
- The <literal>UUID</literal> is the repository's
+ <para>Print the UUID for the repository. The UUID is the repository's
<emphasis>u</emphasis>niversal <emphasis>u</emphasis>nique
<emphasis>id</emphasis>entifier. The Subversion client
uses this identifier to differentiate between one
Modified: branches/1.8/zh/book/ref-svnmucc.xml
===================================================================
--- branches/1.8/zh/book/ref-svnmucc.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/ref-svnmucc.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -17,9 +17,9 @@
offered by the Subversion command-line client itself. For
example, <command>svnmucc</command> is not limited to performing
only a single type of change in a given commit. It is also able
- to perform working-copy-less file content and versioned property
- modifications, which is functionality not currently offered
- by <command>svn</command>.</para>
+ to modify file content and versioned properties without a
+ working copy, which is functionality not currently offered by
+ <command>svn</command>.</para>
-->
<para>Subversion 多 URL 命令行客户端 (<command>svnmucc</command>)
允许用户在没有工作副本的情况下, 向仓库提交任意地修改. 对于远程提交
@@ -290,8 +290,8 @@
<replaceable>FILE</replaceable>:<replaceable>SECTION</replaceable>:<replaceable>OPTION</replaceable>=[<replaceable>VALUE</replaceable>].
In this syntax, <replaceable>FILE</replaceable>
and <replaceable>SECTION</replaceable> are the runtime
- configuration file (either <literal>config</literal>
- or <literal>servers</literal>) and the section
+ configuration file (either <filename>config</filename>
+ or <filename>servers</filename>) and the section
thereof, respectively, which contain the option whose
value you wish to
change. <replaceable>OPTION</replaceable> is, of
Modified: branches/1.8/zh/book/ref-svnrdump.xml
===================================================================
--- branches/1.8/zh/book/ref-svnrdump.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/ref-svnrdump.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -60,8 +60,8 @@
a runtime configuration
option. <replaceable>FILE</replaceable>
and <replaceable>SECTION</replaceable> are the runtime
- configuration file (either <literal>config</literal>
- or <literal>servers</literal>) and the section thereof,
+ configuration file (either <filename>config</filename>
+ or <filename>servers</filename>) and the section thereof,
respectively, which contain the option whose value you
wish to change. <replaceable>OPTION</replaceable> is,
of course, the option itself,
Modified: branches/1.8/zh/book/ref-svnserve.xml
===================================================================
--- branches/1.8/zh/book/ref-svnserve.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/ref-svnserve.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -321,7 +321,7 @@
<term><option>--prefer-ipv6</option> (<option>-6</option>)</term>
<listitem>
<!--
- <para>When resolving the listen hostname, prever an IPv6
+ <para>When resolving the listen hostname, prefer an IPv6
answer over an IPv4 one. IPv4 is preferred by
default.</para>
-->
Modified: branches/1.8/zh/book/ref-svnsync.xml
===================================================================
--- branches/1.8/zh/book/ref-svnsync.xml 2019-11-03 09:43:33 UTC (rev 6009)
+++ branches/1.8/zh/book/ref-svnsync.xml 2019-11-04 14:51:11 UTC (rev 6010)
@@ -107,8 +107,8 @@
<replaceable>FILE</replaceable>:<replaceable>SECTION</replaceable>:<replaceable>OPTION</replaceable>=[<replaceable>VALUE</replaceable>].
In this syntax, <replaceable>FILE</replaceable>
and <replaceable>SECTION</replaceable> are the runtime
- configuration file (either <literal>config</literal>
- or <literal>servers</literal>) and the section thereof,
+ configuration file (either <filename>config</filename>
+ or <filename>servers</filename>) and the section thereof,
respectively, which contain the option whose value you
wish to change. <replaceable>OPTION</replaceable> is,
of course, the option itself,
@@ -761,7 +761,7 @@
<!--
<para>Initialize a repository as a mirror, having already
- created a <literal>pre-revprop-change</literal> hook that
+ created a pre-revprop-change hook that
permits all revision property changes:</para>
-->
<para>把一个仓库初始化镜像仓库, 该仓库已经通过钩子脚本
More information about the svnbook-dev
mailing list