[svnbook commit] r1649 - trunk/src/ru/book
dmitriy
svnbook-dev at red-bean.com
Sun Aug 28 13:17:52 CDT 2005
Author: dmitriy
Date: Sun Aug 28 13:17:50 2005
New Revision: 1649
Modified:
trunk/src/ru/book/appa.xml (contents, props changed)
trunk/src/ru/book/appb.xml (props changed)
trunk/src/ru/book/appc.xml (props changed)
trunk/src/ru/book/book.xml (props changed)
trunk/src/ru/book/ch05.xml (contents, props changed)
trunk/src/ru/book/ch06.xml (contents, props changed)
trunk/src/ru/book/ch07.xml (contents, props changed)
trunk/src/ru/book/ch08.xml (props changed)
trunk/src/ru/book/copyright.xml (props changed)
trunk/src/ru/book/foreword.xml (props changed)
trunk/src/ru/book/styles.css (props changed)
Log:
Book Russian. Sync all not (yet) translated parts of the book with en/
Modified: trunk/src/ru/book/appa.xml
==============================================================================
--- trunk/src/ru/book/appa.xml (original)
+++ trunk/src/ru/book/appa.xml Sun Aug 28 13:17:50 2005
@@ -31,9 +31,9 @@
<title>Revision Numbers Are Different Now</title>
<para>In CVS, revision numbers are per-file. This is because CVS
- uses RCS as a backend; each file has a corresponding RCS file in
- the repository, and the repository is roughly laid out according
- to the structure of your project tree.</para>
+ stores its data in RCS files; each file has a corresponding RCS
+ file in the repository, and the repository is roughly laid out
+ according to the structure of your project tree.</para>
<para>In Subversion, the repository looks like a single
filesystem. Each commit results in an entirely new filesystem
Modified: trunk/src/ru/book/ch05.xml
==============================================================================
--- trunk/src/ru/book/ch05.xml (original)
+++ trunk/src/ru/book/ch05.xml Sun Aug 28 13:17:50 2005
@@ -1194,16 +1194,16 @@
</varlistentry>
<varlistentry>
- <term><literal>log</literal></term>
+ <term><literal>lock</literal></term>
<listitem>
- <para>Print the tree's log message.</para>
+ <para>If a path is locked, describe the lock attributes.</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>lock</literal></term>
+ <term><literal>log</literal></term>
<listitem>
- <para>If a path is locked, describe the lock attributes.</para>
+ <para>Print the tree's log message.</para>
</listitem>
</varlistentry>
@@ -2025,7 +2025,7 @@
equal to the size of the original data, it only takes up
enough space to say, <quote>I look just like this other
piece of data over here, except for the following couple of
- changes.</quote> Specifically, each time a new version of a
+ changes</quote>. Specifically, each time a new version of a
file is committed to the repository, Subversion encodes the
previous version (actually, several previous versions) as a
delta against the new version. The result is that most of
@@ -2242,7 +2242,7 @@
requested range of revisions. Note that <command>svnadmin
dump</command> is reading revision trees from the repository
just like any other <quote>reader</quote> process would
- (<command>svn checkout</command>, for example.) So it's safe
+ (<command>svn checkout</command>, for example). So it's safe
to run this command at any time.</para>
<para>The other subcommand in the pair, <command>svnadmin
@@ -2456,7 +2456,7 @@
<command>cvs2svn</command> utility (see <xref
linkend="svn.forcvs.convert"/>) uses the dump format to represent the
contents of a CVS repository so that those contents can be
- moved in a Subversion repository.</para>
+ copied into a Subversion repository.</para>
</sect2>
Modified: trunk/src/ru/book/ch06.xml
==============================================================================
--- trunk/src/ru/book/ch06.xml (original)
+++ trunk/src/ru/book/ch06.xml Sun Aug 28 13:17:50 2005
@@ -404,7 +404,7 @@
<para>If the client successfully authenticates by any of the
methods listed above, it will attempt to cache the credentials
on disk (unless the user has disabled this behavior, as
- mentioned earlier.)</para>
+ mentioned earlier).</para>
</sect2>
@@ -518,7 +518,7 @@
repository directly needs to have proper read and write
permissions on the entire repository. If you're not
careful, this can lead to a number of headaches, especially
- if you're using a BerkeleyDB database rather than FSFS. Be
+ if you're using a Berkeley DB database rather than FSFS. Be
sure to read <xref linkend="svn.serverconfig.multimethod"/>.</para>
<para>Secondly, when configuring <command>svnserve</command>,
@@ -651,7 +651,7 @@
client displays it in the authentication prompt, and uses it
as a key (along with the server's hostname and port) for
caching credentials on disk (see <xref
- linkend="svn.serverconfig.netmodel.credcache"/>.) The
+ linkend="svn.serverconfig.netmodel.credcache"/>). The
<literal>password-db</literal> variable points to a separate
file that contains a list of usernames and passwords, using
the same familiar format. For example:</para>
@@ -829,7 +829,7 @@
<para>You'd think that the story of SSH tunneling would end
here, but it doesn't. Subversion allows you to create custom
tunnel behaviors in your run-time <filename>config</filename>
- file (see <xref linkend="svn.advanced.confarea"/>.) For example,
+ file (see <xref linkend="svn.advanced.confarea"/>). For example,
suppose you want to use RSH instead of SSH. In the
<literal>[tunnels]</literal> section of your
<filename>config</filename> file, simply define it like
@@ -848,7 +848,7 @@
scenes. If you include a username in the URL (for example,
<literal>svn+rsh://username@host/path</literal>) the client
will also include that in its command (<command>rsh
- username at host svnserve -t</command>.) But you can define new
+ username at host svnserve -t</command>). But you can define new
tunneling schemes to be much more clever than that:</para>
<screen>
@@ -1022,7 +1022,7 @@
available to clients via the WebDAV/DeltaV protocol, which is an
extension to HTTP 1.1
(see <systemitem class="url">http://www.webdav.org/</systemitem>
- for more information.) This protocol takes the ubiquitous HTTP
+ for more information). This protocol takes the ubiquitous HTTP
protocol that is the core of the World Wide Web, and adds
writing—specifically, versioned
writing—capabilities. The result is a standardized,
@@ -1503,9 +1503,9 @@
will be cached in your private run-time
<filename>auth/</filename> area in just the same way your
username and password are cached (see <xref
- linkend="svn.serverconfig.netmodel.credcache"/>.) If cached, Subversion will
- automatically remember to trust this certificate in future
- negotiations.</para>
+ linkend="svn.serverconfig.netmodel.credcache"/>). If cached,
+ Subversion will automatically remember to trust this certificate
+ in future negotiations.</para>
<para>Your run-time <filename>servers</filename> file also gives
you the ability to make your Subversion client automatically
@@ -2254,7 +2254,7 @@
</screen>
<para>Another common problem is often encountered on Unix-like
- systems. As a repository is used, BerkeleyDB occasionally
+ systems. As a repository is used, Berkeley DB occasionally
creates new log files to journal its actions. Even if the
repository is wholly owned by the <command>svn</command> group,
these newly created files won't necessarily be owned by that
Modified: trunk/src/ru/book/ch07.xml
==============================================================================
--- trunk/src/ru/book/ch07.xml (original)
+++ trunk/src/ru/book/ch07.xml Sun Aug 28 13:17:50 2005
@@ -1675,10 +1675,11 @@
an ordinary file. However, when a client sees this property
during checkouts or updates, it interprets the contents of
the file and translates the item back into the special type
- of object. In Subversion 1.1, only versioned symbolic links
- have this property attached, but in future versions of
- Subversion other special types of nodes will probably use
- this property as well.</para>
+ of object. In versions of Subversion current at the time of
+ writing, only versioned symbolic links have this property
+ attached, but in future versions of Subversion other special
+ types of nodes will probably use this property as
+ well.</para>
<para>Note: Windows clients don't have symbolic links, and
thus ignore any <literal>svn:special</literal> files coming
More information about the svnbook-dev
mailing list