[svnbook commit] r1880 - in trunk/src/nb: . book

sunny256 svnbook-dev at red-bean.com
Mon Dec 5 10:09:55 CST 2005


Author: sunny256
Date: Mon Dec  5 10:09:46 2005
New Revision: 1880

Modified:
   trunk/src/nb/LAST_UPDATED
   trunk/src/nb/book/appa.xml
   trunk/src/nb/book/appb.xml
   trunk/src/nb/book/ch03.xml
   trunk/src/nb/book/ch05.xml
   trunk/src/nb/book/ch06.xml
   trunk/src/nb/book/ch09.xml

Log:
Updates to the Norwegian book, merged r1736:1796 from the English files.

* src/nb/LAST_UPDATED
  Updated by "make sync HEAD=1796".

* src/nb/book/appa.xml
* src/nb/book/appb.xml
* src/nb/book/ch03.xml
* src/nb/book/ch05.xml
* src/nb/book/ch06.xml
* src/nb/book/ch09.xml
  Updated r1750, r1763, r1764, r1789, r1791, r1792, r1794, r1796.


Modified: trunk/src/nb/LAST_UPDATED
==============================================================================
--- trunk/src/nb/LAST_UPDATED	(original)
+++ trunk/src/nb/LAST_UPDATED	Mon Dec  5 10:09:46 2005
@@ -1 +1 @@
-1736
+1796

Modified: trunk/src/nb/book/appa.xml
==============================================================================
--- trunk/src/nb/book/appa.xml	(original)
+++ trunk/src/nb/book/appa.xml	Mon Dec  5 10:09:46 2005
@@ -754,11 +754,10 @@
     <para>In the most general sense, Subversion handles binary files
       more gracefully than CVS does.  Because CVS uses RCS, it can
       only store successive full copies of a changing binary file.
-      But internally, Subversion expresses differences between files
-      using a binary-differencing algorithm, regardless of whether they
+      Subversion, however, expresses differences between files using a
+      binary-differencing algorithm, regardless of whether they
       contain textual or binary data.  That means that all files are
-      stored differentially (compressed) in the repository, and small
-      differences are always sent over the network.</para>
+      stored differentially (compressed) in the repository.</para>
     @ENGLISH }}} -->
     <para>Generelt sett behandler Subversion binære filer mer elegant 
       enn CVS.
@@ -766,12 +765,11 @@
       filer som forandres. <!-- ###FIXME: Det der er feil, CVS lagrer 
       også diff i depotet. Og CVS bruker ikke RCS mer. Skal poste til 
       dev@ om det. -->
-      Men internt behandler Subversion forskjeller mellom filer ved 
-      hjelp av en binærdata-basert algoritme, uansett om de inneholder 
-      tekst eller binære data.
+      Subversion, derimot, behandler forskjeller mellom filer ved hjelp 
+      av en binærdata-basert algoritme, uansett om de inneholder tekst 
+      eller binære data.
       Dette betyr at alle filer er lagret differensielt (pakket) i 
-      depotet, og små forandringer blir alltid sendt over 
-      nettverket.</para>
+      depotet.</para>
     
     <!-- @ENGLISH {{{
     <para>CVS users have to mark binary files with
@@ -785,7 +783,7 @@
       Dette glemmer de noen ganger.</para>
 
     <!-- @ENGLISH {{{
-    <para>Subversion takes the more paranoid route: first, it never
+    <para>Subversion takes the more paranoid route—first, it never
       performs any kind of keyword or line-ending translation unless
       you explicitly ask it do so (see <xref
       linkend="svn.advanced.props.special.keywords"/> and <xref
@@ -794,9 +792,9 @@
       files are always stored in the repository in an untranslated
       state.</para>
     @ENGLISH }}} -->
-    <para>Subversion tar den mer paranoide ruten:
-      Til å begynne med utfører den ingen form for nøkkelordutvidelser 
-      hvis du ikke ber den spesielt om å gjøre det (Se <xref 
+    <para>Subversion tar den mer paranoide ruten – til å begynne med 
+      utfører den ingen form for nøkkelordutvidelser hvis du ikke ber 
+      den spesielt om å gjøre det (Se <xref 
       linkend="svn.advanced.props.special.keywords"/> og <xref 
       linkend="svn.advanced.props.special.eol-style"/> for flere 
       detaljer).

Modified: trunk/src/nb/book/appb.xml
==============================================================================
--- trunk/src/nb/book/appb.xml	(original)
+++ trunk/src/nb/book/appb.xml	Mon Dec  5 10:09:46 2005
@@ -153,7 +153,7 @@
         <varlistentry>
           <term>Per-resource versioning</term>
           <listitem>
-            <para> Like CVS and other version-control systems,
+            <para>Like CVS and other version-control systems,
               DeltaV assumes that each resource has a potentially
               infinite number of states. A client begins by placing
               a resource under version control using the new
@@ -228,7 +228,7 @@
         
       </variablelist>
         
-      </sect2>
+    </sect2>
       
   </sect1>
   
@@ -311,7 +311,7 @@
   <!-- ================================================================= -->
   <!-- ================================================================= -->
   <sect1 id="svn.webdav.autoversioning">
-    <title>Autoversioning </title>
+    <title>Autoversioning</title>
 
     <para>While the Subversion client is not a full DeltaV client, nor
       the Subversion server a full DeltaV server, there's still a
@@ -350,7 +350,7 @@
       directive within the <filename>httpd.conf</filename> Location
       block, like so:</para>
 
-              <screen>
+    <screen>
 <Location /repos>
   DAV svn
   SVNPath /path/to/repository
@@ -358,7 +358,6 @@
 </Location>
 </screen>
 
-
     <para>When SVNAutoversioning is active, write requests from WebDAV
       clients result in automatic commits.  A generic log message is
       auto-generated and attached to each revision.</para>
@@ -393,162 +392,99 @@
   <sect1 id="svn.webdav.clients">
     <title>Client Interoperability</title> 
 
-    <para>In this section, we'll describe the most common WebDAV clients (at
-      the time of writing), and how well they operate against an
-      autoversioning mod_dav_svn server.</para>
-
-    <para>All WebDAV clients fall into one of three categories.  These
-      categories are the main definers of what users can and cannot
-      do.</para>
-
-    <variablelist>
-
-      <varlistentry>
-        <term>Standalone application</term>
-
-        <listitem>
-          <para>The WebDAV functionality is buried within a single
-            application.  For example, Microsoft Word is able to open a
-            file directly from a URL.  It locks the file when this
-            happens, and every subsequent <quote>save</quote> command
-            results in a PUT request.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term>File-explorer extension</term>
-
-        <listitem>
-          <para>The WebDAV functionality is an extension to a GUI
-            program that is normally used to browse filesystems,
-            either local or remote.  For example, Windows Explorer is
-            able to browse a WebDAV server as a <quote>network
-            place</quote>.  Users can drag files to and from the
-            desktop, or can rename, copy, or delete files in the usual
-            way.  But because it's only a feature of the
-            file-explorer, the DAV share isn't visible to ordinary
-            applications.  All DAV interaction must happen through the
-            explorer interface.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>        
-        <term>Filesystem implementation</term>
-
-        <listitem>
-          <para>This the best sort of WebDAV client.  It's implemented
-            as a low-level filesystem (typically within the operating
-            system's kernel.)  This means that the DAV share is
-            mounted like any other network filesystem, similar to
-            mounting an NFS share on Unix, or attaching an SMB share
-            as drive-letter in Windows.  As a result, this sort of
-            client provides completely transparent read/write WebDAV
-            access to all programs.  Applications aren't even aware
-            that WebDAV requests are happening.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>There are many WebDAV clients, far too many to list.  Here
-      we provide some details about our experiences with some of the
-      more popular ones.</para>
+    <para>All WebDAV clients fall into one of three
+      categories—standalone applications, file-explorer
+      extensions, or filesystem implementations.  These categories
+      broadly define the types of WebDAV functionality available to
+      users.  <xref linkend="svn.webdav.clients.tbl-1"/> gives our
+      categorization and a quick description of some common pieces of
+      WebDAV-enabled software.  More details about these software
+      offerings, as well as their general category, can be found in
+      the sections that follow.</para>
 
     <table id="svn.webdav.clients.tbl-1">
       <title>Common WebDAV Clients</title>
-      <tgroup cols="4">
+      <tgroup cols="3">
         <thead>
           <row>
-            <entry>DAV Client</entry>
-            <entry>Standalone</entry>
-            <entry>File-explorer</entry>
-            <entry>Filesystem</entry>
+            <entry>Software</entry>
+            <entry>Category</entry>
+            <entry>Description</entry>
           </row>
         </thead>
         <tbody>
-
           <row>
-            <entry>Windows Webfolders</entry>
-            <entry></entry>
-            <entry>x</entry>
-            <entry>x</entry>
+            <entry>Adobe Photoshop</entry>
+            <entry>Standalone WebDAV applications</entry>
+            <entry>Image editing software, allowing direct opening
+              from, and writing to, WebDAV URLs</entry>
           </row>
-          
           <row>
-            <entry>WebDrive</entry>
-            <entry></entry>
-            <entry></entry>
-            <entry>x</entry>
+            <entry>Cadaver</entry>
+            <entry>Standalone WebDAV applications</entry>
+            <entry>Command-line WebDAV client supporting file
+              transfer, tree, and locking operations</entry>
           </row>
-          
           <row>
-            <entry>NetDrive</entry>
-            <entry></entry>
-            <entry></entry>
-            <entry>x</entry>
+            <entry>DAV Explorer</entry>
+            <entry>Standalone WebDAV applications</entry>
+            <entry>GUI tool for exploring WebDAV shares</entry>
           </row>
-          
           <row>
-            <entry>Mac OS X</entry>
-            <entry></entry>
-            <entry></entry>
-            <entry>x</entry>
+            <entry>davfs2</entry>
+            <entry>WebDAV filesystem implementation</entry>
+            <entry>Linux file system driver that allows you to mount a
+              WebDAV share</entry>
           </row>
-          
           <row>
             <entry>GNOME Nautilus</entry>
-            <entry></entry>
-            <entry>x</entry>
-            <entry></entry>
+            <entry>File-explorer WebDAV extensions</entry>
+            <entry>GUI file explorer able to perform tree
+              operations on a WebDAV share</entry>
           </row>
-          
           <row>
             <entry>KDE Konqueror</entry>
-            <entry></entry>
-            <entry>x</entry>
-            <entry></entry>
+            <entry>File-explorer WebDAV extensions</entry>
+            <entry>GUI file explorer able to perform tree
+              operations on a WebDAV share</entry>
           </row>
-          
           <row>
-            <entry>Linux davfs2</entry>
-            <entry></entry>
-            <entry></entry>
-            <entry>x</entry>
+            <entry>Mac OS X</entry>
+            <entry>WebDAV filesystem implementation</entry>
+            <entry>Operating system with built-in support for mounting
+              WebDAV shares locally</entry>
           </row>
-          
           <row>
-            <entry>Cadaver</entry>
-            <entry>x</entry>
-            <entry></entry>
-            <entry></entry>
+            <entry>Macromedia Dreamweaver</entry>
+            <entry>Standalone WebDAV applications</entry>
+            <entry>Web production software able to directly read from
+              and write to WebDAV URLs</entry>
           </row>
-          
           <row>
-            <entry>DAV Explorer</entry>
-            <entry>x</entry>
-            <entry></entry>
-            <entry></entry>
+            <entry>Microsoft Office</entry>
+            <entry>Standalone WebDAV applications</entry>
+            <entry>Office productivity suite with several components
+              able to directly read from and write to WebDAV
+              URLs</entry>
           </row>
-          
           <row>
-            <entry>Microsoft Office</entry>
-            <entry>x</entry>
-            <entry></entry>
-            <entry></entry>
+            <entry>Microsoft Webfolders</entry>
+            <entry>File-explorer WebDAV extensions</entry>
+            <entry>GUI file explorer program able to perform tree
+              operations on a WebDAV share</entry>
           </row>
-
           <row>
-            <entry>Dreamweaver</entry>
-            <entry>x</entry>
-            <entry></entry>
-            <entry></entry>
+            <entry>Novell NetDrive</entry>
+            <entry>WebDAV filesystem implementation</entry>
+            <entry>Drive-mapping program for assigning Windows drive
+              letters to a mounted remote WebDAV share</entry>
           </row>
-
           <row>
-            <entry>Photoshop</entry>
-            <entry>x</entry>
-            <entry></entry>
-            <entry></entry>
+            <entry>SRT WebDrive</entry>
+            <entry>WebDAV filesystem implementation</entry>
+            <entry>File transfer software which, among other things,
+              allows the assignment of Windows drive letters to a
+              mounted remote WebDAV share</entry>
           </row>
           
         </tbody>
@@ -556,196 +492,57 @@
     </table>
 
     <!-- =============================================================== -->
-    <sect2 id="svn.webdav.clients.windows">
-      <title>Windows Webfolders, WebDrive, Netdrive</title> 
-
-      <para>Microsoft was one of the original backers of the WebDAV
-        specification, and first started shipping a client in Windows
-        98, known as <quote>Webfolders</quote>.  This client was also
-        shipped in Windows NT4 and 2000.</para>
-
-      <para>The original Webfolders client was an extension to
-        Explorer, the main GUI program used to browse filesystems.  It
-        works well enough.  In Windows 98, the feature might need to
-        be explicitly installed if Webfolders aren't already visible
-        inside <quote>My Computer</quote>.  In Windows 2000, simply
-        add a new <quote>network place</quote>, enter the URL, and the
-        WebDAV share will pop up for browsing.</para>
-
-      <para>With the release of Windows XP, Microsoft started shipping
-        a new implementation of Webfolders, known as the <quote>WebDAV
-        mini-redirector</quote>.  The new implementation is a
-        filesystem-level client, allowing WebDAV shares to be mounted
-        as drive letters.  Unfortunately, this implementation is
-        incredibly buggy.  The client usually tries to convert http
-        URLs (<literal>http://host/repos</literal>) into UNC share
-        notation (<literal>\\host\repos</literal>); it also often
-        tries to use Windows Domain authentication to respond to
-        basic-auth HTTP challenges, sending usernames as
-        <literal>HOST\username</literal>.  These interoperability
-        problems are severe and documented in numerous places around
-        the web, to the frustration of many users.  Even Greg Stein,
-        the original author of Apache's WebDAV module, recommends
-        against trying to use XP Webfolders against an Apache
-        server.</para>
-
-      <para>It turns out that the original
-        <quote>Explorer-only</quote> Webfolders implementation isn't
-        dead in XP, it's just buried.  It's still possible to find it
-        by using this technique:</para>
-
-      <orderedlist>
-
-        <listitem>
-          <para>Go to 'Network Places'.</para>
-        </listitem>
-
-        <listitem>
-          <para>Add a new network place.</para>
-        </listitem>
-
-        <listitem>
-          <para>When prompted, enter the URL of the repository, but
-            <emphasis>include a port number</emphasis> in the URL.
-            For example, <literal>http://host/repos</literal> would be
-            entered as <literal>http://host:80/repos</literal> instead.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>Respond to any authentication prompts.</para>
-        </listitem>
-
-      </orderedlist>
-
-      <para>There are a number of other rumored workarounds to the
-        problems, but none of them seem to work on all versions and
-        patchlevels of Windows XP.  In our tests, only the previous
-        algorithm seems to work consistently on every system.  The
-        general consensus of the WebDAV community is:</para>
-
-      <itemizedlist>
-        <listitem>
-          <para>Avoid the new Webfolders implementation, use the old
-          one.</para>
-        </listitem>
-
-        <listitem>
-          <para>If you need real a real filesystem-level client for
-            Windows XP, then use either WebDrive or NetDrive.</para>
-        </listitem>
-      </itemizedlist>
-
-      <para>Both WebDrive and NetDrive are excellent commercial
-        products which allows a WebDAV share to be attached as drive
-        letters.  We've had nothing but success with these products.
-        At the time of writing, WebDrive can be purchased from South
-        River Technologies (<ulink
-        url="http://www.southrivertech.com"/>).  NetDrive ships with
-        Netware, is free of charge, and can be found by searching the
-        web for <quote>netdrive.exe</quote>.  (If that sounds odd to
-        you, you're not alone.  See this page on Novell's website:
-        <ulink
-        url="http://www.novell.com/coolsolutions/qna/999.html"/>)</para>
-
-    </sect2>
+    <sect2 id="svn.webdav.clients.standalone">
+      <title>Standalone WebDAV applications</title>
 
+      <para>A WebDAV application is a program which contains built-in
+        functionality for speaking WebDAV protocols with a WebDAV
+        server.  We'll cover some of the most popular programs with
+        this kind of WebDAV support.</para>
 
-    <!-- =============================================================== -->
-    <sect2 id="svn.webdav.clients.macosx">
-      <title>Mac OS X</title> 
-
-      <para>Apple's OS X operating system has an integrated
-        filesystem-level WebDAV client. From the Finder, select the
-        <guimenuitem>Connect to Server</guimenuitem> item from the
-        <guimenu>Go menu</guimenu>.  Enter a WebDAV URL, and it
-        appears as a disk on the desktop, just like any other mounted
-        volume.<footnote><para>From the Darwin terminal, one can also
-        run <literal>mount -t webdav URL
-        /mountpoint</literal></para></footnote>.</para>
-
-      <para>Note that if your mod_dav_svn is older than version 1.2,
-        OS X will refuse to mount the share as read-write; it will
-        appear as read-only.  This is because the OS X insists on
-        locking support for read-write shares, and the ability to lock
-        files first appeared in Subversion 1.2.</para>
-
-      <para>One more word of warning: OS X's WebDAV client can
-        sometimes be overly sensitive to HTTP redirects. If OS X is
-        unable to mount the repository at all, you may need to enable
-        the BrowserMatch directive in the Apache server's
-        <filename>httpd.conf</filename>:</para>
-
-      <screen>
-BrowserMatch "^WebDAVFS/1.[012]" redirect-carefully
-</screen>
-
-    </sect2>
-
-
-    <!-- =============================================================== -->
-    <sect2 id="svn.webdav.clients.linux-de">
-      <title>Nautilus, Konqueror</title> 
-
-      <para>Nautilus is the official file manager/browser for the
-        GNOME desktop (<ulink url="http://www.gnome.org"/>), and
-        Konqueror is the manager/browser for KDE desktop (<ulink
-        url="http://www.kde.org"/>).  Both of these applications have
-        an explorer-level WebDAV client built-in, and operate just
-        fine against an autoversioning repository.</para>
-
-      <para>In GNOME's Nautilus, from the <guimenu>File
-        menu</guimenu>, select <guimenuitem>Open
-        location</guimenuitem> and enter the URL.  The repository
-        should then be displayed like any other filesystem.</para>
-
-      <para>In KDE's Konqueror, you need to use the
-        <literal>webdav://</literal> scheme when entering the URL in
-        the location bar.  If you enter an <literal>http://</literal>
-        URL, Konqueror will behave like an ordinary web browser.
-        You'll likely see the generic HTML directory listing produced
-        by mod_dav_svn.  By entering
-        <literal>webdav://host/repos</literal> instead of
-        <literal>http://host/repos</literal>, Konqueror becomes a
-        WebDAV client and displays the repository as a
-        filesystem.</para>
-
-    </sect2>
-
-    <!-- =============================================================== -->
-    <sect2 id="svn.webdav.clients.linux-fs">
-      <title>Linux davfs2</title> 
-
-      <para>Linux davfs2 is a filesystem module for the Linux kernel,
-        whose development is located at <ulink
-        url="http://dav.sourceforge.net/"/>. Once installed, a WebDAV
-        network share can be mounted with the usual Linux mount
-        command:</para>
-
-      <screen>
-mount.davfs http://host/repos /mnt/dav
-</screen>
-
-    </sect2>
-
-    <!-- =============================================================== -->
-    <sect2 id="svn.webdav.clients.free-apps">
-      <title>Cadaver, DAV Explorer</title>
+      <sect3 id="svn.webdav.clients.standalone.windows">
+        <title>Microsoft Office, Dreamweaver, Photoshop</title> 
+  
+        <para>On Windows, there are several well-known applications
+          that contain integrated WebDAV client functionality, such as
+          Microsoft's Office,
+          <footnote>
+            <para>WebDAV support was removed from Microsoft Access for
+              some reason, but exists in the rest of the Office
+              suite.</para>
+          </footnote>
+          Adobe's Photoshop, and Macromedia's Dreamweaver programs.
+          They're able to directly open and save to URLs, and tend to
+          make heavy use of WebDAV locks when editing a file.</para>
+  
+        <para>Note that while many of these programs also exist for
+          the Mac OS X, they do not appear to support WebDAV directly
+          on that platform.  In fact, on Mac OS X, the
+          <guimenu>File->Open</guimenu> dialog box doesn't allow
+          one to type a path or URL at all.  It's likely that the the
+          WebDAV features were deliberately left out of Macintosh
+          versions of these programs, since OS X already provides such
+          excellent low-level filesystem support for WebDAV.</para>
+  
+      </sect3>
 
-      <para>Cadaver is a bare-bones Unix commandline program for
-        browsing and changing WebDAV shares.  Like the Subversion
-        client, it uses the neon HTTP library—not surprisingly,
-        both neon and cadaver are written by the same author.  Cadaver
-        is free sofware (GPL license) and is available at <ulink
-        url="http://www.webdav.org/cadaver/"/>.</para>
-
-      <para>Using cadaver is similar to using a commandline FTP
-        program, and thus it's extremely useful for basic WebDAV
-        debugging.  It can be used to upload or download files in a
-        pinch, and also to examine properties, copy, move, lock or
-        unlock files:</para>
-      
-      <screen>
+      <sect3 id="svn.webdav.clients.standalone.free">
+        <title>Cadaver, DAV Explorer</title>
+  
+        <para>Cadaver is a bare-bones Unix commandline program for
+          browsing and changing WebDAV shares.  Like the Subversion
+          client, it uses the neon HTTP library—not surprisingly,
+          both neon and cadaver are written by the same author.  Cadaver
+          is free sofware (GPL license) and is available at <ulink
+          url="http://www.webdav.org/cadaver/"/>.</para>
+  
+        <para>Using cadaver is similar to using a commandline FTP
+          program, and thus it's extremely useful for basic WebDAV
+          debugging.  It can be used to upload or download files in a
+          pinch, and also to examine properties, copy, move, lock or
+          unlock files:</para>
+        
+        <screen>
 $ cadaver http://host/repos
 dav:/repos/> ls
 Listing collection `/repos/': succeeded.
@@ -763,43 +560,221 @@
 Progress: [=============================>] 100.0% of 1461 bytes succeeded.
 </screen>
 
-      <para>DAV Explorer is another standalone WebDAV client, written
-        in Java.  It's under a free Apache-like license and is
-        available at <ulink url="http://www.ics.uci.edu/~webdav/"/>.
-        DAV Explorer does everything cadaver does, but has the
-        advantages of being portable and being more user-friendly GUI
-        application.  It's also one of the first clients to support
-        the new WebDAV Access Control Protocol (RFC 3744).</para>
-
-      <para>Of course, DAV Explorer's ACL support is useless in this
-        case, since mod_dav_svn doesn't support it.  The fact that
-        both Cadaver and DAV Explorer support some limited DeltaV
-        commands isn't particularly useful either, since they don't
-        allow <literal>MKACTIVITY</literal> requests.  But it's not
-        relevant anyway; we're assuming all of these clients are
-        operating against an autoversioning repository.</para>
-
+        <para>DAV Explorer is another standalone WebDAV client, written
+          in Java.  It's under a free Apache-like license and is
+          available at <ulink url="http://www.ics.uci.edu/~webdav/"/>.
+          DAV Explorer does everything cadaver does, but has the
+          advantages of being portable and being more user-friendly GUI
+          application.  It's also one of the first clients to support
+          the new WebDAV Access Control Protocol (RFC 3744).</para>
+  
+        <para>Of course, DAV Explorer's ACL support is useless in this
+          case, since mod_dav_svn doesn't support it.  The fact that
+          both Cadaver and DAV Explorer support some limited DeltaV
+          commands isn't particularly useful either, since they don't
+          allow <literal>MKACTIVITY</literal> requests.  But it's not
+          relevant anyway; we're assuming all of these clients are
+          operating against an autoversioning repository.</para>
+  
+      </sect3>
     </sect2>
-    
+
     <!-- =============================================================== -->
-    <sect2 id="svn.webdav.clients.win-apps">
-      <title>Microsoft Office, Dreamweaver, Photoshop</title> 
+    <sect2 id="svn.webdav.clients.file-explorer-extensions">
+      <title>File-explorer WebDAV extensions</title>
+
+      <para>Some popular file explorer GUI programs support WebDAV
+        extensions which allow a user to browse a DAV share as if it
+        was just another directory on the local computer, and allowing
+        basic tree editing operations on the items in that share.  For
+        example, Windows Explorer is able to browse a WebDAV server as
+        a <quote>network place</quote>.  Users can drag files to and
+        from the desktop, or can rename, copy, or delete files in the
+        usual way.  But because it's only a feature of the
+        file-explorer, the DAV share isn't visible to ordinary
+        applications.  All DAV interaction must happen through the
+        explorer interface.</para>
+
+      <sect3 id="svn.webdav.clients.file-explorer-extensions.windows">
+        <title>Microsoft Webfolders</title> 
+  
+        <para>Microsoft was one of the original backers of the WebDAV
+          specification, and first started shipping a client in Windows
+          98, known as <quote>Webfolders</quote>.  This client was also
+          shipped in Windows NT4 and 2000.</para>
+  
+        <para>The original Webfolders client was an extension to
+          Explorer, the main GUI program used to browse filesystems.  It
+          works well enough.  In Windows 98, the feature might need to
+          be explicitly installed if Webfolders aren't already visible
+          inside <quote>My Computer</quote>.  In Windows 2000, simply
+          add a new <quote>network place</quote>, enter the URL, and the
+          WebDAV share will pop up for browsing.</para>
+  
+        <para>With the release of Windows XP, Microsoft started shipping
+          a new implementation of Webfolders, known as the <quote>WebDAV
+          mini-redirector</quote>.  The new implementation is a
+          filesystem-level client, allowing WebDAV shares to be mounted
+          as drive letters.  Unfortunately, this implementation is
+          incredibly buggy.  The client usually tries to convert http
+          URLs (<literal>http://host/repos</literal>) into UNC share
+          notation (<literal>\\host\repos</literal>); it also often
+          tries to use Windows Domain authentication to respond to
+          basic-auth HTTP challenges, sending usernames as
+          <literal>HOST\username</literal>.  These interoperability
+          problems are severe and documented in numerous places around
+          the web, to the frustration of many users.  Even Greg Stein,
+          the original author of Apache's WebDAV module, recommends
+          against trying to use XP Webfolders against an Apache
+          server.</para>
+  
+        <para>It turns out that the original
+          <quote>Explorer-only</quote> Webfolders implementation isn't
+          dead in XP, it's just buried.  It's still possible to find it
+          by using this technique:</para>
+  
+        <orderedlist>
+  
+          <listitem>
+            <para>Go to 'Network Places'.</para>
+          </listitem>
+  
+          <listitem>
+            <para>Add a new network place.</para>
+          </listitem>
+  
+          <listitem>
+            <para>When prompted, enter the URL of the repository, but
+              <emphasis>include a port number</emphasis> in the URL.
+              For example, <literal>http://host/repos</literal> would be
+              entered as <literal>http://host:80/repos</literal> instead.
+            </para>
+          </listitem>
+  
+          <listitem>
+            <para>Respond to any authentication prompts.</para>
+          </listitem>
+  
+        </orderedlist>
+  
+        <para>There are a number of other rumored workarounds to the
+          problems, but none of them seem to work on all versions and
+          patchlevels of Windows XP.  In our tests, only the previous
+          algorithm seems to work consistently on every system.  The
+          general consensus of the WebDAV community is that you should
+          avoid the new Webfolders implementation and use the old one
+          instead, and that if you need real a real filesystem-level
+          client for Windows XP, then use a third-party program like
+          WebDrive or NetDrive.</para>
 
-      <para>These are large well-known applications that contain
-        integrated WebDAV client functionality.  They're able to
-        directly open a URL, save to a URL, and tend to make heavy use
-        of WebDAV locks when editing a file.</para>
-
-      <para>It appears that only the Windows versions of these
-        programs support WebDAV.  On Mac OS X, the
-        <quote>File->Open</quote> dialog box doesn't allow one to type
-        a path or URL at all.  It's likely that the the WebDAV
-        features were deliberately left out of Macintosh versions of
-        these programs, since OS X already provides such excellent
-        low-level filesystem support for WebDAV.</para>
+      </sect3>
 
+      <sect3 id="svn.webdav.clients.file-explorer-extensions.linux-de">
+        <title>Nautilus, Konqueror</title> 
+  
+        <para>Nautilus is the official file manager/browser for the
+          GNOME desktop (<ulink url="http://www.gnome.org"/>), and
+          Konqueror is the manager/browser for KDE desktop (<ulink
+          url="http://www.kde.org"/>).  Both of these applications have
+          an explorer-level WebDAV client built-in, and operate just
+          fine against an autoversioning repository.</para>
+  
+        <para>In GNOME's Nautilus, from the <guimenu>File
+          menu</guimenu>, select <guimenuitem>Open
+          location</guimenuitem> and enter the URL.  The repository
+          should then be displayed like any other filesystem.</para>
+  
+        <para>In KDE's Konqueror, you need to use the
+          <literal>webdav://</literal> scheme when entering the URL in
+          the location bar.  If you enter an <literal>http://</literal>
+          URL, Konqueror will behave like an ordinary web browser.
+          You'll likely see the generic HTML directory listing produced
+          by mod_dav_svn.  By entering
+          <literal>webdav://host/repos</literal> instead of
+          <literal>http://host/repos</literal>, Konqueror becomes a
+          WebDAV client and displays the repository as a
+          filesystem.</para>
+  
+      </sect3>
     </sect2>
 
+    <sect2 id="svn.webdav.clients.fs-impl">
+      <title>WebDAV filesystem implementation</title>
+
+      <para>The WebDAV filesystem implementation is arguably the best
+        sort of WebDAV client.  It's implemented as a low-level
+        filesystem module, typically within the operating system's
+        kernel.  This means that the DAV share is mounted like any
+        other network filesystem, similar to mounting an NFS share on
+        Unix, or attaching an SMB share as drive-letter in Windows.
+        As a result, this sort of client provides completely
+        transparent read/write WebDAV access to all programs.
+        Applications aren't even aware that WebDAV requests are
+        happening.</para>
+
+      <sect3 id="svn.webdav.clients.fs-impl.windows">
+        <title>WebDrive, NetDrive</title> 
+  
+        <para>Both WebDrive and NetDrive are excellent commercial
+          products which allows a WebDAV share to be attached as drive
+          letters in Windows.  We've had nothing but success with
+          these products.  At the time of writing, WebDrive can be
+          purchased from South River Technologies (<ulink
+          url="http://www.southrivertech.com"/>).  NetDrive ships with
+          Netware, is free of charge, and can be found by searching
+          the web for <quote>netdrive.exe</quote>.  Though it is
+          freely available online, users are required to have a
+          Netware license.  (If any of that sounds odd to you, you're
+          not alone.  See this page on Novell's website: <ulink
+          url="http://www.novell.com/coolsolutions/qna/999.html"/>)</para>
+  
+      </sect3>
+
+      <sect3 id="svn.webdav.clients.fs-impl.macosx">
+        <title>Mac OS X</title> 
+
+        <para>Apple's OS X operating system has an integrated
+          filesystem-level WebDAV client.  From the Finder, select the
+          <guimenuitem>Connect to Server</guimenuitem> item from the
+          <guimenu>Go menu</guimenu>.  Enter a WebDAV URL, and it
+          appears as a disk on the desktop, just like any other mounted
+          volume.<footnote><para>From the Darwin terminal, one can also
+          run <literal>mount -t webdav URL
+          /mountpoint</literal></para></footnote>.</para>
+  
+        <para>Note that if your mod_dav_svn is older than version 1.2,
+          OS X will refuse to mount the share as read-write; it will
+          appear as read-only.  This is because the OS X insists on
+          locking support for read-write shares, and the ability to lock
+          files first appeared in Subversion 1.2.</para>
+  
+        <para>One more word of warning: OS X's WebDAV client can
+          sometimes be overly sensitive to HTTP redirects. If OS X is
+          unable to mount the repository at all, you may need to enable
+          the BrowserMatch directive in the Apache server's
+          <filename>httpd.conf</filename>:</para>
+  
+        <screen>
+BrowserMatch "^WebDAVFS/1.[012]" redirect-carefully
+</screen>
+  
+      </sect3>
+
+      <sect3 id="svn.webdav.clients.fs-impl.linux">
+        <title>Linux davfs2</title> 
+  
+        <para>Linux davfs2 is a filesystem module for the Linux kernel,
+          whose development is located at <ulink
+          url="http://dav.sourceforge.net/"/>. Once installed, a WebDAV
+          network share can be mounted with the usual Linux mount
+          command:</para>
+  
+        <screen>
+$ mount.davfs http://host/repos /mnt/dav
+</screen>
+  
+      </sect3>
+    </sect2>
   </sect1>
 
 </appendix>

Modified: trunk/src/nb/book/ch03.xml
==============================================================================
--- trunk/src/nb/book/ch03.xml	(original)
+++ trunk/src/nb/book/ch03.xml	Mon Dec  5 10:09:46 2005
@@ -618,18 +618,115 @@
     
     <sidebar>
       <!-- @ENGLISH {{{
-      <title>Repository Layout</title>
+      <title>What's in a Name?</title>
+      @ENGLISH }}} -->
+      <!-- ¤ --><title>Hva ligger i et navn?</title>
 
-      <para>If you're wondering what <literal>trunk</literal> is all
-        about in the above URL, it's part of the way we recommend
-        you lay out your Subversion repository which we'll talk a lot
-        more about in <xref linkend="svn.branchmerge"/>.</para>
-      @ENGLISH }}} -->
-      <title>Oppbygning av depotet</title>
-      <para>Hvis du lurer på hva det er med <literal>trunk</literal> i 
-        URLen ovenfor, så er den en del av måten vi anbefaler du legger 
-        opp Subversiondepotet, noe som vi vil snakke en god del mer om i 
+      <!-- @ENGLISH {{{
+      <para>Subversion tries hard not to limit the type of data you
+        can place under version control.  The contents of files and
+        property values are stored and transmitted as binary data, and
+        the <xref linkend="svn.advanced.props.special.mime-type"/>
+        tells you how to give Subversion a hint that
+        <quote>textual</quote> operations don't make sense for a
+        particular file.  There are a few places, however, where
+        Subversion places restrictions on information it
+        stores.</para>
+      @ENGLISH }}} -->
+      <para>Subversion gjør sitt beste for å ikke begrense hvilken type 
+        data du kan plassere under versjonskontroll.
+        Innholdet av filer og egenskaper lagres og overføres som binære 
+        data, og <xref linkend="svn.advanced.props.special.mime-type"/> 
+        forteller deg hvordan du gir Subversion et hint om at 
+        <quote>tekstbaserte</quote> operasjoner ikke gir noen mening for 
+        en spesiell fil.
+        Det er imidlertid noen få steder hvor Subversion begrenser 
+        hvordan informasjonen kan lagres.</para>
+
+      <!-- @ENGLISH {{{
+      <para>Subversion handles text internally as UTF-8 encoded
+        Unicode.  As a result, certain items which are inherently
+        <quote>textual</quote>, such as property names, path names,
+        and log messages, can only contain legal UTF-8 characters.  It
+        also provides a minimum requirement for use of the
+        <literal>svn:mime-type</literal> property—if a file's
+        contents aren't compatible with UTF-8, you should mark it as a
+        binary file.  Otherwise, Subversion will attempt to merge
+        differences using UTF-8, which is likely to leave garbage in
+        the file.</para>
+      @ENGLISH }}} -->
+      <para>Internt behandler Subversion tekst som UTF-8-kodet Unicode.
+        Som et resultat av dette kan enkelte elementer som er 
+        <quote>tekstbaserte</quote>, som for eksempel loggmeldinger og 
+        navn på egenskaper og filstier, kun inneholde lovlige tegn i 
+        UTF-8.
+        Det medfører også et minimumskrav for bruken av 
+        <literal>svn:mime-type</literal>-egenskapen – hvis filinnholdet 
+        ikke er kompatibelt med UTF-8, bør du merke den som en binær 
+        fil.
+        Hvis ikke, vil Subversion prøve å flette inn forskjeller ved å 
+        bruke UTF-8, noe som kan etterlate skrot i fila.</para>
+
+      <!-- @ENGLISH {{{
+      <para>In addition, path names are used as XML attribute values
+        in WebDAV exchanges, as well in as some of Subversion's
+        housekeeping files.  This means that path names can only
+        contain legal XML (1.0) characters.  Subversion also prohibits
+        TAB, CR, and LF characters in path names, so they aren't
+        broken up in diffs, or in the output of commands like <xref
+        linkend="svn.ref.svn.c.log"/> or <xref
+        linkend="svn.ref.svn.c.status"/>.</para>
+      @ENGLISH }}} -->
+      <para>I tillegg brukes stinavn som XML-attributtverdier i 
+        WebDAV-kommunikasjonen og noen av filene som Subversion bruker 
+        til å holde rede på dataene sine i.
+        Dette betyr at stinavn kan kun inneholde tegn som er gyldige i 
+        XML (1.0).
+        Subversion forbyr også tabulatortegn, CR og LF i stinavn så de 
+        ikke blir brutt opp ved bruk av diff-funksjonen, eller i 
+        utdataene fra kommandoer som <xref linkend="svn.ref.svn.c.log"/> 
+        eller <xref linkend="svn.ref.svn.c.status"/>.</para>
+
+      <!-- @ENGLISH {{{
+      <para>While it may seem like a lot to remember, in practice
+        these limitations are rarely a problem.  As long as your
+        locale settings are compatible with UTF-8, and you don't use
+        control characters in path names, you should have no trouble
+        communicating with Subversion.  The command-line client adds
+        an extra bit of help—it will automatically escape legal
+        path characters as needed in URLs you type to create
+        <quote>legally correct</quote> versions for internal
+        use.</para>
+      @ENGLISH }}} -->
+      <para>Selv om dette ser ut som mye å huske på, er dette sjelden et 
+        problem i praksis.
+        Så lenge dine lokale innstillinger er kompatible med UTF-8 og du 
+        ikke bruker kontrolltegn i stinavn, skal du ikke oppleve 
+        problemer når du kommuniserer med Subversion.
+        Kommandolinjeklienten hjelper litt til – <!-- ¤ Krøkkete setning 
+        -->den vil automatisk beskytte lovlige tegn i stiene når det er 
+        nødvendig i URL-er som du skriver for å lage 
+        <quote>lovlige</quote> versjoner for intern bruk.</para>
+
+      <!-- @ENGLISH {{{
+      <para>Experienced users of Subversion have also developed a set
+        of best-practice conventions for laying out paths in the
+        repository.  While these aren't strict requirements like the
+        syntax described above, they help to organize frequently
+        performed tasks.  The <literal>/trunk</literal> part of URLs
+        you'll find throughout this book is one of these conventions;
+        we'll talk a lot more about it and related recommendations in
         <xref linkend="svn.branchmerge"/>.</para>
+      @ENGLISH }}} -->
+      <para>Erfarne Subversion-brukere har også utviklet et sett 
+        <quote>gyldne regler</quote> for å sette opp stier i depotet.
+        Selv om disse reglene ikke er nødvendig å følge til punkt og 
+        prikke som syntaksen ovenfor, vil de hjelpe deg med å organisere 
+        oppgaver som gjøres nå og da.
+        <literal>/trunk</literal>-delen som du finner i URL-er i denne 
+        boken er en av disse konvensjonene; vi vil snakke mye mer om det 
+        og beslektede anbefalinger i <xref 
+        linkend="svn.branchmerge"/>.</para>
 
     </sidebar>
 

Modified: trunk/src/nb/book/ch05.xml
==============================================================================
--- trunk/src/nb/book/ch05.xml	(original)
+++ trunk/src/nb/book/ch05.xml	Mon Dec  5 10:09:46 2005
@@ -369,11 +369,12 @@
         depotgrensesnittet.</para>
 
       <!-- @ENGLISH {{{
-      <para>Here is a table that gives a comparative overview of
-        Berkeley DB and FSFS repositories.  The next sections go into
-        detail.</para>
+      <para><xref linkend="svn.reposadmin.basics.backends.tbl-1"/>
+        gives a comparative overview of Berkeley DB and FSFS
+        repositories.  The next sections go into detail.</para>
       @ENGLISH }}} -->
-      <para>Her er en tabell som gir en oversikt over forskjellene 
+      <para><xref linkend="svn.reposadmin.basics.backends.tbl-1"/> 
+        inneholder en tabell som gir en oversikt over forskjellene 
         mellom depoter av typen Berkeley DB og FSFS.
         De neste seksjonene går inn i detalj.</para>
 

Modified: trunk/src/nb/book/ch06.xml
==============================================================================
--- trunk/src/nb/book/ch06.xml	(original)
+++ trunk/src/nb/book/ch06.xml	Mon Dec  5 10:09:46 2005
@@ -97,7 +97,8 @@
       and disadvantages.  In fact, it's possible for different servers
       to run in parallel, each accessing your repositories in its own
       way, and each without hindering the other (see <xref
-      linkend="svn.serverconfig.multimethod"/>).  Here's a brief overview and
+      linkend="svn.serverconfig.multimethod"/>).  <xref
+      linkend="svn.serverconfig.overview.tbl-1"/> gives a brief overview and
       comparison of the two available Subversion servers—as an
       administrator, it's up to you to choose whatever works best for
       you and your users.</para>
@@ -110,7 +111,9 @@
       Faktisk er det mulig for forskjellige tjenere å kjøre parallelt og 
       aksessere depotet på hver sin måte uten å legge hindringer i veien 
       for den andre (se <xref linkend="svn.serverconfig.multimethod"/>).
-      Her er en kort oversikt og sammenligning av de to tilgjengelige 
+      <xref
+      linkend="svn.serverconfig.overview.tbl-1"/> inneholder en kort 
+      oversikt og sammenligning av de to tilgjengelige 
       Subversiontjenerne – som en administrator er det opp til deg å 
       velge hva som fungerer best for deg og dine brukere.</para>
       

Modified: trunk/src/nb/book/ch09.xml
==============================================================================
--- trunk/src/nb/book/ch09.xml	(original)
+++ trunk/src/nb/book/ch09.xml	Mon Dec  5 10:09:46 2005
@@ -4363,20 +4363,45 @@
             revision tree.  See <xref linkend="svn.reposadmin.maint.migrate"/>
             for a practical use.</para>
 
-          <para>If the size of your Subversion dumpfile is a concern,
-            you can use the <option>--deltas</option> switch to (in
-            some cases drastically) reduce the size of the dumpfile
-            that <command>svnadmin</command> creates.  With this
-            switch, instead of writing the full content of each
-            revision to the dumpfile, <command>svnadmin dump</command>
-            will only emit the differences from one revision to the
-            next.  There are, however, disadvantages to creating
-            deltified dumpfiles—it's more CPU intensive to
-            create them, <command>svndumpfilter</command> can't
-            operate on them, and non-deltified dumpfiles tend to
-            compress better.</para>
+          <para>By default, the Subversion dumpfile stream contains a
+            single revision (the first revision in the requested
+            revision range) in which every file and directory in the
+            repository in that revision is presented as if that whole
+            tree was added at once, followed by other revisions (the
+            remainder of the revisions in the requested range) which
+            contain only the files and directories which were modified
+            in those revisions.  For a modified file, the complete
+            fulltext representation of its contents, as well as all of
+            its properties, are presented in the dumpfile; for a
+            directory, all of its properties are presented.</para>
+
+          <para>There are a pair of useful options which modify the
+            dumpfile generator's behavior.  The first is the
+            <option>--incremental</option> option, which simply causes
+            that first revision in the dumpfile stream to contain only
+            the files and directories modified in that revision,
+            instead of being presented as the addition of a new tree,
+            and in exactly the same way that every other revision in
+            the dumpfile is presented.  This is useful for generating
+            a dumpfile that is to be loaded into another repository
+            which already has the files and directories that exist in
+            the original repository.</para>
+
+          <para>The second useful option is <option>--deltas</option>.
+            This switch causes <command>svnadmin dump</command> to,
+            instead of emitting fulltext representations of file
+            contents and property lists, emit only deltas of those
+            items against their previous versions.  This reduces (in
+            some cases, drastically) the size of the dumpfile that
+            <command>svnadmin dump</command> creates.  There are, however,
+            disadvantages to using this option—deltified
+            dumpfiles are more CPU intensive to create, cannot be
+            operated on by <command>svndumpfilter</command>, and tend
+            not to compress as well as their non-deltified counterparts
+            when using third-party tools like <command>gzip</command>
+            and <command>bzip2</command>.</para>
 
-            </refsect1>
+        </refsect1>
         <refsect1>
           <title>Switches</title>
           




More information about the svnbook-dev mailing list