subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Sperling <s...@elego.de>
Subject Re: svn checkout - special characters in file name are not encoding properly
Date Thu, 12 Aug 2010 15:16:37 GMT
On Thu, Aug 12, 2010 at 02:30:50AM +0200, Vincent Lefevre wrote:
> On 2010-08-11 19:56:28 +0200, Stefan Sperling wrote:
> > On Wed, Aug 11, 2010 at 04:29:56PM +0200, Vincent Lefevre wrote:
> > > You're forcing the user to use a UTF-8 locale. Unacceptable.
> > 
> > No, we leave users a choice.
> 
> The choice doesn't work.

It doesn't work for your twisted requirement of having a program
running in the C locale use UTF-8. Otherwise it works fine.
 
> > I consider your idea of forcing UTF-8 filenames on everybody unacceptable.
> 
> No, this is not *my* idea. Please read the thread again. I proposed to
> leave the choice by storing the charset chosen by the user in the .svn
> directory (or whatever mean following future WC formats). But you
> didn't want this solution.

It's not a solution because storing the information in wc meta-data
does not fix anything. What is Subversion supposed to do with filenames
that come down from the repository during an update, but cannot be
represented in the recorded charset? Using UTF-8 instead of the recorded
charset is out of the question. That leaves erroring out as the only
option. So how is that different from the current situation?

There is a clearly defined way of letting Subversion know which
charset to use. Set the locale. If you have to, set Subversion's locale
to something other than what locale your terminal uses.

~/bin/mysvn:
 #!/bin/sh
 evn LC_CTYPE="en_US.<preferred charset>" svn update

Stefan

Mime
View raw message