Re: Mac OS X: problems adding files with umlauts

> That said, it is possible to write file names containing bytes that can't decode as UTF-8.

I can't believe that. Could you please give an reproducible example?

> I think LC_ALL is relevant to what the encoding of svn's output should be.

I'm sure, you mixed here two things: the file names and the output. File
names should be always convertible to a general character representation
like UTF-8. Displaying the file names with the right sign in the output is a
different issue and might depend on the used font.

If you think, LC_ALL should be relevant for the file name detection in
Subversion, could you give answers for the following questions:
- What LC_ALL-value the user should set?
- What should happen when the wrong value was set?
- What value to set for file names in different languages?

--
Best regards,
Thomas Singer
_____________
SyntEvo GmbH
Schillerallee 2
83457 Bayerisch Gmain
Germany
www.syntevo.com
Wilfredo Sánchez Vega schrieb:
> 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
> 
> 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org