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

Re: svn checkout - special characters in file name are not encoding properly

From: Paul Ebermann <Paul-Ebermann_at_gmx.de>
Date: Wed, 11 Aug 2010 17:34:19 +0200

Vincent Lefevre wrote:
> On 2010-08-11 13:51:18 +0200, Stefan Sperling wrote:
>> On Wed, Aug 11, 2010 at 12:35:59PM +0200, Vincent Lefevre wrote:

>>> Yes, and this is another reason why the solution chosen by Subversion
>>> doesn't work well. For instance, GNOME always uses UTF-8 for filename
>>> encoding.
>> You might as well argue that Subversion's solution works well but
>> GNOME's solution does not.
> That's wrong. GNOME let's me to use any locale in shell sessions.
> Subversion doesn't.

Yes, but GNOME does not allow using any locale in a file manager session (or, it ignores
the locale in the filemanager session, while the command line tools do not).

(KDE is similar, for my experiments.)

>>> So, if the user uses ISO-8859-* locales (for shell sessions),
>>> one gets inconsistencies.
>> So don't use GNOME if you don't want your filenames encoded in UTF-8,
> I meant: one gets inconsistencies between GNOME and Subversion.
>> or don't use a non-UTF-8 locale when working with files you want to
>> use from GNOME. Problem solved.
> You're forcing the user to use a UTF-8 locale. Unacceptable.

No, GNOME forces the user to use a UTF-8 locale, if ls, rm, cd and other command line
tools are to show/accept the same name as the GNOME file manager.

Subversion here simply behaves as any other Unix command line tool, it seems, with the
additional gotcha that it does not only use input from and output to terminal and file
system, but also from/to the repository.

Received on 2010-08-11 17:34:59 CEST

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.