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

Locale problem: Can't convert string from native encoding to 'UTF-8'

From: Richard Sheldon <richardsheldon_at_comcast.net>
Date: 2005-10-20 16:11:08 CEST

I have been having the same problem as David has. I've setup the most
noddy example I can think of, to rule out as many things as possible.
Here's the setup
    - Windows XP Pro, SP2
    - Locale - American English
    - Subversion 1.2.3
    - TortoiseSVN 1.2.4
   - Suse Linux 9.3 Pro
   - Subversion 1.2.3
   - svnserve
   - LANG settings tried en_US.UTF-8, C
I created a single directory, with no contents, and tried to import this
into the repository, and got the following message:
$ svn import -m message repo2 svn://fubar/repos
svn: Transaction cleanup failed
svn: Can't convert string from native encoding to 'UTF-8':
svn: Ph?\17Xx?\21h?\1
I tried this both from the command line (bash shell under cygwin), and from
TortoiseSVN, and got the same resultin both cases. I tried changing the
LANG of the server to "C" and restarting, but no joy.
I'm almost at a loss here. I've spent the last 4 hours screwing around
trying to get this to work.
One thing I have noticed is that the SUSE version of subversion is NOT
linked against libiconv - should it be for the conversions to work?
(although I don't know what it's converting, as I can't see any non-ASCII
characters in the dir name or log message). I guess the next step is to
build from scratch.
Suse 9.3 doesn't appear to have the iconv library, so I guess I'll have to
do that one too (and perhaps the apr). Sheesh!
Any help or advice would be appreciated. It does seem suspicious that both
David and are having problems on Suse systems.
Received on Thu Oct 20 16:23:47 2005

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.