[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Non-ASCII user names when "svn" protocol is used.

From: Marcus Rueckert <darix_at_web.de>
Date: 2006-03-08 23:11:24 CET

On 2006-03-08 18:54:44 +0000, Philip Martin wrote:
> > it would make sense to me if Subversion read its configuration files
> > in the system locale.
> Except that httpd doesn't do setlocale() so mod_authz_svn cannot do
> native to UTF8 conversions (apart from trivial conversions for ASCII
> strings). At present paths within an AuthzSVNAccessFile need to be
> UTF8 encoded and changing that to native isn't possible since
> mod_authz_svn won't be able to convert such paths to UTF8 as required
> by the Subversion filesystem. The svnserve equivalent is the authz-db
> file, and it's presently also UTF8. I suppose svnserve could do
> things differently, but that doesn't seem like a good idea to me.

why make it more complicated than needed?
throwing in locale handling into all this gives you more trouble than it

if everything internal to svn is utf8 why shouldnt the config files be
the same. UTF-8 isnt this new anymore. and any better editor on the
world now can save utf-8 encoding.

document the config files should be utf-8. just my 2 cents.
this would make supporting svn easier aswell.

just my 2 cents.

           openSUSE - SUSE Linux is my linux
               openSUSE is good for you
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 8 23:11:46 2006

This is an archived mail posted to the Subversion Dev mailing list.