Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: domain of rooneg@gmail.com designates
 64.233.184.203 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=OO/BB8f1K174MvH1btP4sTCHfmCtG1lC+XLuHEFqFfrE9+TzWMsN2LQUsHYYN51re6cYgL1lTLULIdGqF1+jpW1r/Cblq4qxdh6uhr3AZFxtoUJSHz+WaaBSa6DG7WkvuDj9QatqrHHj+uwTIz/QYWZ3RU7P9KrSo7yIxJGkazY=
Message-ID: <7edfeeef0601181514g68569983o3085aa70fa6f5232@mail.gmail.com>
Date: Wed, 18 Jan 2006 15:14:06 -0800
From: Garrett Rooney <rooneg@electricjellyfish.net>
Sender: rooneg@gmail.com
To: dev@httpd.apache.org
Subject: Re: httpd and locales
In-Reply-To: <200601190008.17032@news.perlig.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <7edfeeef0601181117yb0af3cbsfd553c5a0e4c7a62@mail.gmail.com>
	 <20060118223005.GA28979@redhat.com>
	 <7edfeeef0601181500t39a1137fwbad5a8e717febb8b@mail.gmail.com>
	 <200601190008.17032@news.perlig.de>

On 1/18/06, Andr=E9 Malo <nd@perlig.de> wrote:
> * Garrett Rooney wrote:
>
> > The specific problem I'm trying to fix is that mod_dav_svn fails to
> > run a pre-lock hook script when you try to lock a filename with double
> > byte characters.  It never even gets to the point of trying to run the
> > script, it fails trying to build the command line because it can't
> > convert the filename from utf8 to the native encoding because the
> > locale is C and thus the native encoding is 7 bit ascii.  I'm having
> > trouble finding a work around for this that doesn't involve setting
> > the locale, although if there's anything obvious I'm missing I'd love
> > to hear it.
>
> It doesn't belong here, but... I'm wondering why the path isn't passed as
> UTF-8. Why is it translated to the locale at all? It's all happening with=
in
> the svn file system, so I'd really expect to get utf-8 and would consider
> locale translation as a bug.

Well, I imagine that the assumption is that any hook script is going
to be using the actual locale specified in LANG/LC_ALL/etc env
variables, so if we don't translate to that locale it'll get rather
confused by utf8 data in its command line.  As a general rule svn
translates from native -> utf8 on input and from utf8 -> native for
output.  Ironically, if the LANG/LC_ALL/etc env vars were being
followed by httpd this translation would be a noop, since the system
uses a utf8 locale...

-garrett