Re: about character set / encoding conversion in subversion

Ben Collins-Sussman wrote:
>> What character recoding is done within the server (svnserve 1.1.4) and
>> how do I have to configure the server to know all neccessary encodings?

> So 'svn' does this the most, obviously. But even simple programs like
> 'svnserve' or 'svnlook' do it to a small degree. For example,
> svnserve has its own svnserve.conf file which contains locally-encoded
> system paths. svnserve needs to convert them to UTF8 before passing
> them to internal APIs.

Mh, ok. All local paths use standard ASCII characters, as it can be seen by
the fact that svnserve did work fine with this repository if the committed
files didn't contain any non-ASCII-characters.

However it DID break if the comitted files contained characters from richer
charsets.

My server process (svnserve) now runs with LANG=de_DE.utf8@euro and seems to
be happy so far... :-/ bThough I still don't understand why it wanted to
transcode some of the committed file's names into its local encoding?

Now maybe someone could clarify, am I officially too stupid to configure
subversion, or is it really nowhere written that the subversion server
process will need to transcode some strings into its own locale / encoding
for some reason and thus needs to use a local enconding which can represent
all characters of all encodings used by any clients accessing this server?

Anyway, sorry for wasting your time, thanks a lot for your help :-))) and I
really hope it works reliably now. :-)

Greetings,

  Gunter

-- 
To mess up a Linux box, you need to work at it; to mess up your Windows 
box, you just need to work on it.        -- Scott Granneman, Security 
Focus
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org