[svnbook commit] r1335 - trunk/src/en/book

cmpilato svnbook-dev at red-bean.com
Wed May 25 01:30:07 CDT 2005


Author: cmpilato
Date: Wed May 25 01:30:06 2005
New Revision: 1335

Modified:
   trunk/src/en/book/ch07.xml
Log:
* src/en/book/ch07.xml
  (Subversion Repository URLs): Was 'URL Construction'.  Massage the
    text to not refer to Chapter 2 (*especially* as plain text instead
    of an <xref>).  Also fix a spelling oops.


Modified: trunk/src/en/book/ch07.xml
==============================================================================
--- trunk/src/en/book/ch07.xml	(original)
+++ trunk/src/en/book/ch07.xml	Wed May 25 01:30:06 2005
@@ -2636,30 +2636,28 @@
   </sect1>
 
   <!-- ******************************************************************* -->
-  <!-- *** SECTION 6:  URL Construction                                *** -->
+  <!-- *** SECTION 6:  SUBVERSION REPOSITORY URLS                      *** -->
   <!-- ******************************************************************* -->
   <sect1 id="svn-ch-7-sect-6">
-    <title>URL Construction</title>
+    <title>Subversion Repository URLs</title>
 
-    <para>In Chapter 2, you saw a table that listed the different URL
-      schemes available to a Subversion client.  That wasn't the
-      entire story.  Complex setups or server locations sometimes
-      demand more complex URLs.  Here we explain a few important
-      edge-cases in the way Subversion parses URLs.</para>
-
-    <para>For the most part, Subversion's URLs use the standard
-      syntax, allowing for server names and port numbers to be
-      specified as part of the URL:</para>
+    <para>As illustrated throughout this book, Subversion uses URLs to
+      identify versioned resources in Subversion repositories.  For
+      the most part, these URLs use the standard syntax, allowing for
+      server names and port numbers to be specified as part of the
+      URL:</para>
 
     <screen>
 $ svn checkout http://svn.example.com:9834/repos
 …
 </screen>
 
-    <para>Remember that the <literal>file:</literal> access method is
-      valid only for local repositories—in fact, in accordance
-      with convention, the server name portion of the URL is required
-      to be either absent or <literal>localhost</literal>:</para>
+    <para>But there are some nuances in Subversion's handling of URLs
+      that are notable.  For example, URLs containing the
+      <literal>file:</literal> access method (used for local
+      repositories) must, in accordance with convention, have either a
+      server name of <literal>localhost</literal> or no server name at
+      all:</para>
  
     <screen>
 $ svn checkout file:///path/to/repos
@@ -2689,7 +2687,7 @@
       that a URL uses ordinary slashes even though the native
       (non-URL) form of a path on Windows uses backslashes.</para>
     
-    <para>Finally, it should be noted that the Subverison client will
+    <para>Finally, it should be noted that the Subversion client will
       automatically encode URLs as necessary, just like a web browser
       does.  For example, if a URL contains a space or upper-ASCII
       character:</para>



More information about the svnbook-dev mailing list