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

Re: problems with non-ascii filenames: "Can't convert string from 'UTF-8' to native encoding"

From: Kalin KOZHUHAROV <kalin_at_thinrope.net>
Date: 2005-10-04 05:03:45 CEST

Sean McBride wrote:
> Hello,
> I have a file in my working copy named:
> TMS Frame Assem... inst Final.eps
> That non-ascii char (which I hope neither the list nor your mail client
> messes up) is an elipsis (U+2026).
Well, sending a mail in ISO-8859-1 was guaranteed to mess it as it did (transform it to three dots).

> When I added the file to the repo, I get the message:
> svnlook: Can't convert string from 'UTF-8' to native encoding:
> svnlook: /tmp/svnlook.1/docs/Dev/Hybex Figs/TMS Frame Assem?\226?\128?
> \166 inst Final.eps
What has svnlook do here? What exactly did you type?

> I am using svn 1.2.3 both locally and on the server, on Mac OS 10.4.2.
What is your locale in the client and the server (if latter matters)?

Waht is the filesystem used both on server and client. Can it handle UTF-8 filenames correctly?

I just tried to reproduce this in linux, but it worked as expected:

$ perl -CS -e 'print "touch \"TMS Frame Assem\x{2026} inst Final.eps\"\n";'
$ touch "TMS Frame Assem… inst Final.eps"
$ ll TMS\ Frame\ Assem…\ inst\ Final.eps
-rw-r--r-- 1 kalin users 0 Oct 4 11:51 TMS Frame Assem… inst Final.eps
$ svn add TMS\ Frame\ Assem…\ inst\ Final.eps
A TMS Frame Assem… inst Final.eps
$ svn ci TMS\ Frame\ Assem…\ inst\ Final.eps -m "testing utf8"
Adding TMS Frame Assem… inst Final.eps
Transmitting file data .
Committed revision 110.

Give us more details, and somebody might spot the problem.


|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 4 05:05:56 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.