Typos in the English book
Jens Seidel
jensseidel at users.sf.net
Wed Nov 30 14:42:51 CST 2005
On Wed, Nov 30, 2005 at 12:52:14AM +0000, Max Bowsher wrote:
> Jens Seidel wrote:
> > svnbook-dev <svnbook-dev at red-bean.com> schrieb am 28.11.05 23:09:05:
> The principal authors of the book are American, but there are British
> contributors - which explains what you have found.
>
> I think, in this case, the right thing to do is to follow along with the
> dominant American style.
>
> > Please add this information to HACKING or the source code (in a comment).
>
> I'll let one of the primary authors do this.
OK.
> > A native reader can check this better than I.
>
> And a properly configured spelling checker can outdo us all :-)
>
> Perhaps we can set up aspell for the English source too. The Spanish
> translation already uses it.
I ran aspell and attached a new small path.
> > PS: I will try to generate also a few more patches, especially for the
> German
> > translation.
>
> Before you spend too much time on it, you need to know that the German
> translation is incomplete and abandoned. We have had no contact from the
> book German translators for months, and no additional work has been done
> on the translation in over a year.
OK, incomplete and abandoned text is the best argument to send patches,
right? I'm aware that there is a lot to do. Since I do not have
sufficient spare time it's unlikely that I will complete the translation
but I can try my best ...
Jens
-------------- next part --------------
Index: appb.xml
===================================================================
--- appb.xml (Revision 1871)
+++ appb.xml (Arbeitskopie)
@@ -37,7 +37,7 @@
universal read/write medium. The basic idea is that a
WebDAV-compliant web server can act like a generic file
server; clients can mount shared folders that behave much like
- NFS or SMB filesystems..</para>
+ NFS or SMB filesystems.</para>
<para>The tragedy, though, is that the RFC 2518 WebDAV
specification does not provide any sort of model for version
Index: ch01.xml
===================================================================
--- ch01.xml (Revision 1871)
+++ ch01.xml (Arbeitskopie)
@@ -101,7 +101,7 @@
he'd already come up with not only the name
<quote>Subversion</quote>, but also with the basic design of the
Subversion repository. When CollabNet called, Karl immediately
- agreed to work on the project, and Jim got his employer, RedHat
+ agreed to work on the project, and Jim got his employer, Red Hat
Software, to essentially donate him to the project for an
indefinite period of time. CollabNet hired Karl and Ben
Collins-Sussman, and detailed design work began in May. With
Index: ch03.xml
===================================================================
--- ch03.xml (Revision 1871)
+++ ch03.xml (Arbeitskopie)
@@ -1294,7 +1294,7 @@
<command>svn revert</command>) can be used without any
network access. This makes it easy to manage your
changes-in-progress when you are somewhere without a network
- connection, such as travelling on an airplane, riding a
+ connection, such as traveling on an airplane, riding a
commuter train or hacking on the beach.</para>
<para>Subversion does this by keeping private caches of
Index: ch05.xml
===================================================================
--- ch05.xml (Revision 1871)
+++ ch05.xml (Arbeitskopie)
@@ -672,7 +672,7 @@
program returns a non-zero exit value, the commit is
stopped before the transaction is even created. If the
hook program writes data to stderr, it will be
- marshalled back to the client.</para>
+ marshaled back to the client.</para>
</listitem>
</varlistentry>
@@ -690,7 +690,7 @@
and the name of the transaction being committed. If the
program returns a non-zero exit value, the commit is
aborted and the transaction is removed. If the hook
- program writes data to stderr, it will be marshalled
+ program writes data to stderr, it will be marshaled
back to the client.</para>
<para>The Subversion distribution includes some access
@@ -811,7 +811,7 @@
locked, and the user attempting to perform the lock. If
the program returns a non-zero exit value, the lock
action is aborted and anything printed to stderr is
- marshalled back to the client.</para>
+ marshaled back to the client.</para>
</listitem>
</varlistentry>
@@ -843,7 +843,7 @@
the path being unlocked, and the user attempting to
remove the lock. If the program returns a non-zero exit
value, the unlock action is aborted and anything printed
- to stderr is marshalled back to the client.</para>
+ to stderr is marshaled back to the client.</para>
</listitem>
</varlistentry>
Index: ch06.xml
===================================================================
--- ch06.xml (Revision 1871)
+++ ch06.xml (Arbeitskopie)
@@ -1490,7 +1490,7 @@
(R)eject, accept (t)emporarily or accept (p)ermanently?
</screen>
- <para>This dialogue should look familiar; it's essentially the
+ <para>This dialog should look familiar; it's essentially the
same question you've probably seen coming from your web
browser (which is just another HTTP client like Subversion!).
If you choose the (p)ermanent option, the server certificate
Index: ch07.xml
===================================================================
--- ch07.xml (Revision 1871)
+++ ch07.xml (Arbeitskopie)
@@ -1361,7 +1361,7 @@
order for the keyword to be expanded. You should consider the
value of the <literal>svn:keywords</literal> property to be
case-sensitive too—certain keyword names will be recognized
- regardless of case, but this behaviour is deprecated.</para>
+ regardless of case, but this behavior is deprecated.</para>
<para>Subversion defines the list of keywords available for
substitution. That list contains the following five keywords,
@@ -2357,7 +2357,7 @@
manipulating your unversioned ones. But that flexibility means
that across the lifetime of your repository, a given versioned
resource might have many paths, and a given path might represent
- serveral entirely different versioned resources.</para>
+ several entirely different versioned resources.</para>
<para>Subversion is pretty smart about noticing when an object's
version history includes such <quote>changes of address</quote>.
@@ -2455,8 +2455,8 @@
</footnote>
we can think of <quote>Main Street</quote> as our path and
<quote>Wheaton</quote> as our peg revision. These two pieces of
- information identify a unique path which can travelled (north or
- south on Main Street), and will keep us from travelling up and
+ information identify a unique path which can traveled (north or
+ south on Main Street), and will keep us from traveling up and
down the wrong Main Street in search of our destination. Now we
throw in <quote>606 N.</quote> as our operative revision, of
sorts, and we know <emphasis>exactly</emphasis> where to
@@ -3316,7 +3316,7 @@
non-trivial.</para>
<para>The interface between Subversion and external diff and merge
- tools harkens back to a time when Subversion's only contextual
+ tools hearkens back to a time when Subversion's only contextual
differencing capabilities were built around invocations of the
GNU diffutils toolchain, specifically the
<command>diff</command> and <command>diff3</command> utilities.
Index: ch08.xml
===================================================================
--- ch08.xml (Revision 1871)
+++ ch08.xml (Arbeitskopie)
@@ -495,7 +495,7 @@
<para>If the Subversion Repository Layer is at <quote>the other
end of the line</quote>, the Repository Access Layer is the
- line itself. Charged with marshalling data between the client
+ line itself. Charged with marshaling data between the client
libraries and the repository, this layer includes the
libsvn_ra module loader library, the RA modules themselves
(which currently includes libsvn_ra_dav, libsvn_ra_local, and
Index: ch09.xml
===================================================================
--- ch09.xml (Revision 1871)
+++ ch09.xml (Arbeitskopie)
@@ -3888,7 +3888,7 @@
<refnamediv>
<refname>svn unlock</refname>
<refpurpose>Unlock working copy paths or
- URLs..</refpurpose>
+ URLs...</refpurpose>
</refnamediv>
<refsect1>
<title>Synopsis</title>
More information about the svnbook-dev
mailing list