On Jul 6, 2006, at 1:58 AM, Ryan Schmidt wrote:
> On Jul 6, 2006, at 08:12, Thomas Singer wrote:
>
>> I'm using Mac OS X 10.4.7 with Subversion 1.3.1 (r19032) and have
>> problems adding files with umlauts in the name.
>>
>> - I've created a file "Überbau.txt" in the working copy
>> - first problem: when listing the directory content on the
>> console, the
>> file name appears as "U??berbau.txt"
>> - when I invoke 'svn status' in this directory, I get following error
>> message:
>> ~/test tom$ svn status
>> subversion/libsvn_subr/utf.c:466: (apr_err=22)
>> svn: Can't convert string from native encoding to 'UTF-8':
>> subversion/libsvn_subr/utf.c:464: (apr_err=22)
>> svn: U?\204?\136berbau.txt
>> Why that? Can't Subversion read every file name?
>> - ok, after setting LC_ALL, it works (even with the right umlaut!):
>> ~/test tom$ export LC_ALL=en_US
>> ~/test tom$ svn status
>> ? Überbau.txt
>
> I think you answered your own question... you need to set LC_ALL
> (or LANG) first so Subversion knows what character encoding it's
> working with.
Actually, on Mac OS X all file names are, by convention, encoded
as UTF-8, so the svn client should be able to decode file names
without LC_ALL, which really has nothing to do with file names. That
said, it is possible to write file names containing bytes that can't
decode as UTF-8. In that situation, you're somewhat SOL.
I don't know if other OS's specify an assumed encoding for file
names.
That said, I think LC_ALL is relevant to what the encoding of
svn's output should be.
-wsv
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 6 22:54:31 2006