From: Ruediger Pluem <rpluem@apache.org>
Date: Sat, 7 Jun 2008 12:51:43 +0000 (+0000)
Subject: * Update transformation
X-Git-Tag: 2.3.0~513
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=83b2dda8fe710151fada0cf081bb3eb235b6f457;p=thirdparty%2Fapache%2Fhttpd.git

* Update transformation


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@664334 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_dav_lock.html.en b/docs/manual/mod/mod_dav_lock.html.en
index ecd4dbb6a90..0be491f3a8c 100644
--- a/docs/manual/mod/mod_dav_lock.html.en
+++ b/docs/manual/mod/mod_dav_lock.html.en
@@ -36,10 +36,10 @@
     the service of <code class="module"><a href="../mod/mod_dav.html">mod_dav</a></code>. But without a backend provider
     which makes use of it, it's useless and should not be loaded into the
     server. A sample backend module which actually utilizes
-    <code class="module"><a href="../mod/mod_dav_lock.html">mod_dav_lock</a></code>, is <a href="http://subversion.tigris.org/">mod_dav_svn</a>, the subversion provider module.</p>
+    <code class="module"><a href="../mod/mod_dav_lock.html">mod_dav_lock</a></code> is <a href="http://subversion.tigris.org/">mod_dav_svn</a>, the subversion provider module.</p>
 
     <p>Note that <code class="module"><a href="../mod/mod_dav_fs.html">mod_dav_fs</a></code> does <em>not</em> need this
-    generic locking module, because it uses it's own more specialized
+    generic locking module, because it uses its own more specialized
     version.</p>
 
     <p>In order to make <code class="module"><a href="../mod/mod_dav_lock.html">mod_dav_lock</a></code> functional, you just have
@@ -49,7 +49,7 @@
     <div class="note"><h3>Developer's Note</h3>
       <p>In order to retrieve the pointer to the locking provider function, you
       have to use the <code>ap_lookup_provider</code> API with the arguments
-      <code>dav-lock</code>, <code>generic</code> and <code>0</code>.</p>
+      <code>dav-lock</code>, <code>generic</code>, and <code>0</code>.</p>
     </div>
 </div>
 <div id="quickview"><h3 class="directives">Directives</h3>
@@ -72,7 +72,7 @@
 </table>
     <p>Use the <code class="directive">DavGenericLockDB</code> directive to specify
     the full path to the lock database, excluding an extension. If
-    the path is not absolute, it will be taken relative to <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>. The implementation of
+    the path is not absolute, it will be interpreted relative to <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>. The implementation of
     <code class="module"><a href="../mod/mod_dav_lock.html">mod_dav_lock</a></code> uses a SDBM database to track user
     locks.</p>
 
@@ -87,7 +87,7 @@
     directory for this purpose rather than changing the permissions on
     an existing directory.  In the above example, Apache will create
     files in the <code>var/</code> directory under the <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> with the base filename
-    <code>DavLock</code> and extension name chosen by the server.</p>
+    <code>DavLock</code> and an extension added by the server.</p>
 
 
 </div>
diff --git a/docs/manual/mod/mod_dav_lock.xml.ja b/docs/manual/mod/mod_dav_lock.xml.ja
index 23b426fc5a3..23661ed24b7 100644
--- a/docs/manual/mod/mod_dav_lock.xml.ja
+++ b/docs/manual/mod/mod_dav_lock.xml.ja
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" ?>
 <!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
 <?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 420993 -->
+<!-- English Revision: 420993:662627 (outdated) -->
 
 <!--
  Licensed to the Apache Software Foundation (ASF) under one or more
diff --git a/docs/manual/mod/mod_dav_lock.xml.meta b/docs/manual/mod/mod_dav_lock.xml.meta
index c73ab7ea4b8..8bcbe0bf5b6 100644
--- a/docs/manual/mod/mod_dav_lock.xml.meta
+++ b/docs/manual/mod/mod_dav_lock.xml.meta
@@ -8,6 +8,6 @@
 
   <variants>
     <variant>en</variant>
-    <variant>ja</variant>
+    <variant outdated="yes">ja</variant>
   </variants>
 </metafile>
diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en
index b512ec514ca..dcd8f899e77 100644
--- a/docs/manual/mod/mod_proxy.html.en
+++ b/docs/manual/mod/mod_proxy.html.en
@@ -856,7 +856,8 @@ through</td></tr>
     thus, disable its persistent connection and pool for that backend.
     This helps in various situations where a firewall between Apache and
     the backend server (regardless of protocol) tends to silently
-    drop connections. To disable connection pooling reuse,
+    drop connections or when backends themselves may be under round-
+    robin DNS. To disable connection pooling reuse,
     set this property value to <code>On</code>. 
     </td></tr>
     <tr><td>flushpackets</td>
diff --git a/docs/manual/mod/mod_proxy.xml.ja b/docs/manual/mod/mod_proxy.xml.ja
index 976d56631e2..e8f50327467 100644
--- a/docs/manual/mod/mod_proxy.xml.ja
+++ b/docs/manual/mod/mod_proxy.xml.ja
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" ?>
 <!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
 <?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 189754:661107 (outdated) -->
+<!-- English Revision: 189754:664013 (outdated) -->
 
 <!--
  Licensed to the Apache Software Foundation (ASF) under one or more
diff --git a/docs/manual/mod/mod_rewrite.html.en b/docs/manual/mod/mod_rewrite.html.en
index 0fa5e348504..7fe2e399777 100644
--- a/docs/manual/mod/mod_rewrite.html.en
+++ b/docs/manual/mod/mod_rewrite.html.en
@@ -1243,10 +1243,11 @@ cannot use <code>$N</code> in the substitution string!
         is specified by <em>NAME</em> and the value is
         <em>VAL</em>. The <em>domain</em> field is the domain of the
         cookie, such as '.apache.org', the optional <em>lifetime</em>
-        is the lifetime of the cookie in minutes, and the optional 
+        is the lifetime of the cookie in minutes (0 means expires at end
+        of session), and the optional
         <em>path</em> is the path of the cookie. If <em>secure</em>
-        is set to 'true' or '1', the cookie is only transmitted via secured
-        connections. If <em>httponly</em> is set to 'true' or '1', the
+        is set to 'secure', 'true' or '1', the cookie is only transmitted via secured
+        connections. If <em>httponly</em> is set to 'HttpOnly', 'true' or '1', the
         <code>HttpOnly</code> flag is used, making the cookie inaccessible
         to JavaScript code on browsers that support this feature.</dd>