Reply-To: dev@subversion.apache.org Delivered-To: mailing list commits@subversion.apache.org Received: (qmail 87610 invoked by uid 99); 18 Sep 2012 13:28:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2012 13:28:12 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2012 13:28:09 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 8C20D23888CD; Tue, 18 Sep 2012 13:27:25 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1387144 - /subversion/site/publish/docs/release-notes/1.8.html Date: Tue, 18 Sep 2012 13:27:25 -0000 To: commits@subversion.apache.org From: stsp@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120918132725.8C20D23888CD@eris.apache.org> 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 -

`mod_dav_svn` now supports hook script UTF-8 input/output - ¶ -

- -

As documented in issue #2487, hook scripts run on a mod_dav_svn-based -Subversion server previously had problems with non-ASCII input and output. -Because Apache HTTPD modules always run in the "C" locale, -which is restricted to ASCII, mod_dav_svn usually failed -trying to process non-ASCII characters.

- -

Among other problems, this prevented pre-lock and -post-unlock hook scripts from operating on paths containing -non-ASCII characters, and prevented non-ASCII error output from -start-commit and pre-commit hooks from reaching -SVN clients.

- -

Subversion 1.8 addresses these problems with a new SVNUseUTF8 -option for mod_dav_svn. If this option is set, mod_dav_svn -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 -must write error messages to stderr in UTF-8. Because ASCII is a -subset of UTF-8 existing hook scripts will continue to work unmodified.

- -

For best results, hook scripts should use a UTF-8 locale if the -SVNUseUTF8 option is active. It is recommended to configure -a UTF-8 locale using the hook script environment configuration file.

- -

API changes, improvements and language bindings (client and server) @@ -932,6 +897,42 @@ to that of other Subversion configuratio

`mod_dav_svn` now supports hook script UTF-8 input/output + ¶ +

+ +

As documented in issue #2487, hook scripts run on a mod_dav_svn-based +Subversion server previously had problems with non-ASCII input and output. +Because Apache HTTPD modules always run in the "C" locale, +which is restricted to ASCII, mod_dav_svn usually failed +trying to process non-ASCII characters.

+ +

Among other problems, this prevented pre-lock and +post-unlock hook scripts from operating on paths containing +non-ASCII characters, and prevented non-ASCII error output from +start-commit and pre-commit hooks from reaching +SVN clients.

+ +

Subversion 1.8 addresses these problems with a new SVNUseUTF8 +option for mod_dav_svn. If this option is set, mod_dav_svn +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 +must write error messages to stderr in UTF-8. Because ASCII is a +subset of UTF-8 existing hook scripts will continue to work unmodified.

+ +

For best results, hook scripts should use a UTF-8 locale if the +SVNUseUTF8 option is active. It is recommended to configure +a UTF-8 locale using the hook script environment configuration file.

+ +

mod_dav_svn now supports hook script UTF-8 input/output - ¶ -

API changes, improvements and language bindings (client and server) @@ -932,6 +897,42 @@ to that of other Subversion configuratio

mod_dav_svn now supports hook script UTF-8 input/output + ¶ +

post-commit hook grows txn-name argument

`mod_dav_svn` now supports hook script UTF-8 input/output - ¶ -

`mod_dav_svn` now supports hook script UTF-8 input/output + ¶ +

`post-commit` hook grows `txn-name` argument