subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject svn commit: r1387144 - /subversion/site/publish/docs/release-notes/1.8.html
Date Tue, 18 Sep 2012 13:27:25 GMT
Author: stsp
Date: Tue Sep 18 13:27:25 2012
New Revision: 1387144

URL: http://svn.apache.org/viewvc?rev=1387144&view=rev
Log:
* publish/docs/release-notes/1.8.html
  (mod-dav-svn-utf8): Move into the hooks section, since this benefits hooks
   but not much else.

Modified:
    subversion/site/publish/docs/release-notes/1.8.html

Modified: subversion/site/publish/docs/release-notes/1.8.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.8.html?rev=1387144&r1=1387143&r2=1387144&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Tue Sep 18 13:27:25 2012
@@ -766,41 +766,6 @@ Select: (1) use their version, (2) use y
 
 </div>  <!-- cmdline -->
 
-<div class="h3" id="mod-dav-svn-utf8">
-<h3><tt>mod_dav_svn</tt> now supports hook script UTF-8 input/output
-  <a class="sectionlink" href="#hooks-post-commit"
-    title="Link to this section">&para;</a>
-</h3>
-
-<p>As documented in <a
-href="http://subversion.tigris.org/issues/show_bug.cgi?id=2487"
->issue #2487</a>, hook scripts run on a <tt>mod_dav_svn</tt>-based
-Subversion server previously had problems with non-ASCII input and output.
-Because Apache HTTPD modules always run in the &quot;C&quot; locale,
-which is restricted to ASCII, <tt>mod_dav_svn</tt> usually failed
-trying to process non-ASCII characters.</p>
-
-<p>Among other problems, this prevented <tt>pre-lock</tt> and
-<tt>post-unlock</tt> hook scripts from operating on paths containing
-non-ASCII characters, and prevented non-ASCII error output from
-<tt>start-commit</tt> and <tt>pre-commit</tt> hooks from reaching
-SVN clients.</p>
-
-<p>Subversion 1.8 addresses these problems with a new <tt>SVNUseUTF8</tt>
-option for <tt>mod_dav_svn</tt>. If this option is set, <tt>mod_dav_svn</tt>
-assumes that all hook script input/output is encoded in UTF-8.
-This is always the case for paths passed to hook scripts, since Subversion
-uses UTF-8 internally for all paths. If this option is set, hook scripts
-<b>must</b> write error messages to stderr in UTF-8. Because ASCII is a
-subset of UTF-8 existing hook scripts will continue to work unmodified.</p>
-
-<p>For best results, hook scripts should use a UTF-8 locale if the
-<tt>SVNUseUTF8</tt> option is active. It is recommended to configure
-a UTF-8 locale using the <a href="#hooks-env"
->hook script environment configuration file</a>.</p>
-
-</div>  <!-- mod-dav-svn -->
-
 <div class="h3" id="apis">
 <h3>API changes, improvements and language bindings
     (<em>client and server</em>)
@@ -932,6 +897,42 @@ to that of other Subversion configuratio
 
 </div>  <!-- hooks-env -->
 
+<div class="h4" id="mod-dav-svn-utf8">
+<h4><tt>mod_dav_svn</tt> now supports hook script UTF-8 input/output
+  <a class="sectionlink" href="#hooks-post-commit"
+    title="Link to this section">&para;</a>
+</h4>
+
+<p>As documented in <a
+href="http://subversion.tigris.org/issues/show_bug.cgi?id=2487"
+>issue #2487</a>, hook scripts run on a <tt>mod_dav_svn</tt>-based
+Subversion server previously had problems with non-ASCII input and output.
+Because Apache HTTPD modules always run in the &quot;C&quot; locale,
+which is restricted to ASCII, <tt>mod_dav_svn</tt> usually failed
+trying to process non-ASCII characters.</p>
+
+<p>Among other problems, this prevented <tt>pre-lock</tt> and
+<tt>post-unlock</tt> hook scripts from operating on paths containing
+non-ASCII characters, and prevented non-ASCII error output from
+<tt>start-commit</tt> and <tt>pre-commit</tt> hooks from reaching
+SVN clients.</p>
+
+<p>Subversion 1.8 addresses these problems with a new <tt>SVNUseUTF8</tt>
+option for <tt>mod_dav_svn</tt>. If this option is set, <tt>mod_dav_svn</tt>
+assumes that all hook script input/output is encoded in UTF-8.
+This is always the case for paths passed to hook scripts, since Subversion
+uses UTF-8 internally for all paths. If this option is set, hook scripts
+<b>must</b> write error messages to stderr in UTF-8. Because ASCII is a
+subset of UTF-8 existing hook scripts will continue to work unmodified.</p>
+
+<p>For best results, hook scripts should use a UTF-8 locale if the
+<tt>SVNUseUTF8</tt> option is active. It is recommended to configure
+a UTF-8 locale using the <a href="#hooks-env"
+>hook script environment configuration file</a>.</p>
+
+</div>  <!-- mod-dav-svn -->
+
+
 <div class="h4" id="hooks-post-commit">
 <h4><tt>post-commit</tt> hook grows <tt>txn-name</tt> argument
   <a class="sectionlink" href="#hooks-post-commit"



Mime
View raw message