On Thu, Feb 02, 2012 at 08:12:52PM +0100, Ignacio González (Eliop) wrote:
> OK, I'll investigate further.
> Just to summarize, I have a problem and a no-problem:
> Problem: how to use the aforementioned check-mime-type with 'accented' files
> checked-in from Windows clients.
This is exactly what issue 2487 is about (I've already linked to it
but here is the link again for completeness in the archives):
You see, whatever locale settings you have on your machine do not
affect mod_dav_svn in any way. They do not ever reach mod_dav_svn
because httpd makes sure all apache modules run in the "C" locale,
which only supports ASCII. This was done in httpd deliberately,
for security reasons.
One workaround discussed in the issue is to use mod_setlocale to set
a locale within httpd, bypassing httpd's default behaviour.
This will then indirectly enable the Subversion libraries called from
mod_dav_svn (and thus, hook scripts) to deal with non-ASCII characters.
This would require you to compile an apache module against the httpd
you use as Subversion server (i.e. you'd have to compile a module
against the version of httpd shipped with Subversion Edge) and then
use this module to configure a locale for mod_dav_svn that supports UTF-8.
The other way to fix this problem is to apply the patch which was
committed to trunk in r1239203. It adds a SVNUseUTF8 option to mod_dav_svn
which can be used to work around this problem by enabling UTF-8 support
in the Subversion libraries independently of locale settings.
We cannot backport this fix to 1.7 because doing so would violate our
release-compatibility guarantees. The 1.8 release will include this fix
but it is still far off.
I'm afraid there is no ready-made solution for Subversion Edge at this time.
Though you could ask CollabNet to include a patch or the mod_setlocale
module in Subversion Edge.
> No-problem: how to check out 'accented' files already in the
> repository with a Linux client. "Solved".
Ok, that's good to know :)
Received on 2012-02-02 20:29:39 CET