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

Re: "Strange" characters in file names

From: Hans Salvisberg <svn.users_at_salvisberg.com>
Date: 2007-03-26 01:58:45 CEST

Ryan Schmidt wrote:
>>>> svn: Kurs Ern?\195?\164hrung.doc
>>>
>>> Perhaps you have not set the LANG variable so ls and svn don't know how to properly display it. Try export LANG=de_DE.utf8 or whatever the correct value for your OS is. (The contents of the directory /usr/share/locale may tell you what the valid locales are on your system.)
>>
>> Yes, indeed, this helped. ls still doesn't display the file properly (I don't really care), but svn doesn't complain anymore.
>>
>> Can you explain (or point me to an explanation), what this does and why it's needed? I'd prefer not to set a locale (leave it at the default POSIX), because I don't want to introduce a bias towards German. This particular filename happens to be in German, but I'm sure someone will upload a file with a French name sooner or later.
> svn: Can't convert string from native encoding to 'UTF-8':
>
> This does not introduce a bias towards German. It does cause error messages to be printed in German. Based on the name of the file, I assumed you would want that. If you prefer English error messages from Subversion, use en_US.utf8, or whatever it is on your OS.
>
> The important part is the .utf8 part, which explains to Subversion and other tools that you are using the UTF-8 character encoding. UTF-8 can handle all languages, so as long as your locale is a UTF-8 locale, you will be able to handle all filenames.

How do I know I'm using the UTF-8 encoding? How do you know? Could svn know it, too?

What exactly does it mean that I'm "using the UTF-8 encoding"? That the filename is UTF-8-encoded?

Instead of two question marks, ls now displays two different box drawing characters. So, even if svn doesn't complain anymore, how do I know that UTF-8 really is the correct encoding and I wouldn't risk putting something into the repository that might cause trouble?

>> The directory with the offending file has svn:ignore set to "*". I guess I'll just ignore the entire directory instead, but I wonder why svn looks at the files at all.
>
> Whether you want to ignore the files or not is your business.

In this case I do want to ignore thm, but I'm surprised that svn looks at them anyway and trips over the "strange" characters.

Hans

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 26 01:59:09 2007

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.