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

Re: svn: Can't recode string

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-01-19 05:38:03 CET

> 2) It's not obvious why this is even necessary. I thought subversion
> was supposed to be unicode savvy? Assuming it stored the filename in
> some Unicode encoding in the database (UTF-8, UTF-16, etc...) and my
> OS fully supports Unicode (Mac OS X uses Unicode everywhere and the
> HFS+ filesystem stores filenames in Unicode), why is there a problem?
> Can someone enlighten me?

Subversion stores all pathnames as UTF-8 internally. But the
commandline client, before printing the path, must convert the UTF-8 to
the 'native' locale of your shell, so it's readable by the user. Each
user has a locale that is capable of displaying some subset of unicode;
  I'm not aware of any locale that can display *all* unicode.

The "can't recode string" error means that your current locale is
unable to render some unicode data. That is, there's a path with some
name that your locale cannot decipher. It's your responsibility to set
your locale to something that can decode all the paths in your

For example, if your collaborator in China writes a Chinese filename to
the repository, then you better not have an ISO-8859-1 latin locale
running; it won't be able to display the Chinese unicode. You and
your collaborator need to coordinate on this.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 19 05:43:28 2005

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