hoodwink.d enhanced
 

juretta.com

svn: Can't convert string from 'UTF-8' to native encoding: | May 09, 2007-->

May 09, 2007
Filenames containing "special characters" can cause an annoying Subversion error message:
svn: Can't convert string from 'UTF-8' to native encoding:
From the subversion book:
Errors like this typically occur when the Subversion client has received a UTF-8 string from the repository, but not all of the characters in that string can be represented using the encoding of the current locale. For example, if your locale is en_US but a collaborator has committed a Japanese filename, you're likely to see this error when you receive the file during an svn update.
To fix this error message you have to set your current locale appropriately:
macbook:~ stefan$ export LC_CTYPE=en_US.UTF-8
macbook:~ stefan$ locale
LANG=
LC_COLLATE="C"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL="C/en_US.UTF-8/C/C/C/C"
macbook:~ stefan$ svn update
@09:09 | Comments: 2 | Tags: SVN (1)

Diggman

Related Entries


1
Dan says:
Avatar Fri Jun 08 08:53:08 +0200 2007 | #

Thanks for this tip, it seems to be working and my checkout is underway again :)

2
solomon71 says:
Avatar Tue Jul 31 12:14:34 +0200 2007 | #

Gracias, this worked great for me. Update is underway for a huge project. I didn’t have the time to do a full checkout.

About

juretta.com is the personal workspace of Stefan Saasen. You can send him an email or read more about this site in the „About“ section.

« Previous entry

Loading the Netflix Dataset into MySQL
posted about 1 year ago

» Next entry

Google Developer Day 2007 Hamburg
posted about 1 year ago

Related Entries

Recent comment

On: “Attachr.com: OpenID support added

You need to kill this spam stuff!

posted about 1 year ago by entropie

Look!

Latest links  RSS  

More...