[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: Joachim Durchholz <jo_at_durchholz.org>
Date: 2006-01-02 11:51:45 CET

Gunter Ohrner schrieb:
> Gunter Ohrner wrote:
>>Problem: checkin was successful. Subsequent commits in a directory with
>>umlauts now cause the error message "svn: Can't recode string".
> Doesn't anyone have an idea what I may be doing wrong?

Just saw your message for the first time.

> Also pointers to FAQs / relevant svnbook sections are greatly appreciated, I
> couldn't find anything helpful for my case. :-(

I got the same problem with this setup:
* Working on a Windows workstation
* Committing a file that contained an umlaut in its name
* Trying to svn export that file *to a Linux directory*.

Prefixing the svn export command with
   export LC_CTYPE=en_US.UTF-8
did the trick for me.

Note that this made svn recode the file names to UTF-8, which may or may
not be what you want. (It didn't work too well for me because I'm
running ssh with ISO 8859-1. And I'm not sure how Apache would handle
such a file name - it probably depends on what its environment told it
about the locale. OTOH I didn't care about anything, since file names
with umlauts aren't supposed to be visible at shell or HTTP level
anyway; files with umlauts in their names aren't supposed to have
meaning outside the repository on the server. Your setup may be different.)

On the Unix side, you can try
   locale -a
to get a list of all installed locales. Doing
   echo $LC_CTYPE
should tell you what the default locale is.

I'd try using a wider locale (with more characters suppored), i.e. one
that is *.utf8, *.iso8859*, or *@euro, then reconfigure whatever needs
to be reconfigured for that character sets. (I'd go for switching the
entire system, but if you already have things with umlauts in your file
system, a changed encoding will change their names. OTOH if the current
encoding already could handle umlauts, you'd probably not get those
recode errors from SVN.)

> 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.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 2 11:53:43 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.