(Moving to firstname.lastname@example.org, where it's more appropriate...)
On 1/19/06, André Malo <email@example.com> wrote:
> * Garrett Rooney <firstname.lastname@example.org> wrote:
> > > 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 within
> > > 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...
> So whether the users of a repository (httpd or svnserve) may use the full
> unicode range for their files depends on the locale of the server? That feels
> just wrong ;-) I don't see how there are command line confusings...
Well, yes and no. For all the internals of the repository it doesn't
matter at all what the the locale of the server is, but as soon as you
need to pass that data as part of the command line of an external
program like a hook script it does matter.
> As long as one references files enclosed in the filesystem no translation
> should occur at all. It's just unicode (in utf-8 format). The only part of
> the subversion system which should deal with filename recodings of reposiory
> stored path should be a client.
I'm really not sure I agree, for an external program on a system
running in a particular locale I'd be REALLY surprised to get data
passed in via the command line that shows up in some arbitrary
encoding, it should really show up in the native encoding IMO. The
fact that httpd choses to ignore the system's locale and thus has a
native encoding that only allows 7 bit ascii is the real bug here.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jan 19 20:53:15 2006