[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 17:25:31 CET

On 2006-03-08 12:51:27 +0100, Alexander Kitaev wrote:
> I've investigated an issue with non-ASCII user names (those that are
> multibyte encoded in UTF-8) and "svn" protocol. Finally I found that sending
> user name in UTF-8 will doesn't work (svnserve reports "username not found")
> unless username in conf/passwd file is also UTF-8 encoded, because when user
> name is read from the config file by svnserve it is not converted to UTF-8
> string and thus doesn't match user name string sent by the client.
> As far as I understand passwd file, as well as other configuration files are
> usually edited with editors that saves files in system encoding, not UTF-8.
> Does it makes sense to change code that reads passwd file to convert user
> names and passwords to UTF-8, before returning them to the caller? Am I
> understand correctly that right now non-ASCII user names may only be used
> when passwd file contains user name in UTF-8?
> I was not able to use non-ASCII user name with command line at all (it was
> saying that character is not convertable to UTF8), but it is probably
> because there is something wrong with my system setup.

from my experience it is always the best solution to use utf8 for all
svn related config files. saves you trouble and hair.


           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 18:38:44 2006

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