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

Re: "Can't recode string" again...

From: Gunter Ohrner <G.Ohrner_at_post.rwth-aachen.de>
Date: 2006-01-02 16:41:30 CET

Joachim Durchholz wrote:
> Prefixing the svn export command with
> export LC_CTYPE=en_US.UTF-8
> did the trick for me.

LC_* is unset, LANG is set to the current locale. I also tried unstting LANG
and exporting LC_CTYPE as de_DE@euro, with the same results.

I'm not using an UTF8 encoding on the client side, so "something.UTF-8"
would probably lead to corrupt results.

>> What charset does svnserve try to recode the UTF-8 to?
> I'd guess it's the character set that the client uses for file names.

Mh, so the client converts the filename to UTF-8 before committing /
updateing, and the server converts it back to the client's character
encoding? Why doesn't the server store the filename in an encoding-neutral
UTF-8 and leave all re-encoding work to the different clients, which could
likely have different locale setting with different encodings?



"Nach uns der Syn-Flood!"
        -- Autor unbekannt
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 2 16:56:03 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.