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

Re: Check-out fails with LANG=C

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 9 Jul 2013 22:47:35 +0200

On Tue, Jul 09, 2013 at 10:02:00PM +0200, Andreas Krey wrote:
> On Tue, 09 Jul 2013 21:43:50 +0000, Stefan Sperling wrote:
> ...
> > I think using UTF-8 by default would be a good choice today. But it
> > certainly wasn't when the Subversion project was started years ago.
> > And we cannot change the existing default behaviour now. That would
> > create compatibility nightmares with existing working copies.
>
> You could still make the encoding settable in the WC configuration,
> and optionally make that default to utf8 in the checkout. Old WCs
> wouldn't be affected. If the filesystem doesn't know, the application
> should store a value. (This whole stuff is scary anyway.)

Ok, fine. I can see that working and be useful. Apart from the fact
that we currently do not really have a concept of a per-WC configuration.

But with the default set to the old behaviour please. We don't want
to cause surprises for unsuspecting users.

This knob would have to be in the client config, I guess, and apply
to all working copies during checkout and update. The working copy
would of course need to remember the value of the config knob had
during the initial checkout (this can be stored in wc.db), and would
re-use that value even if the configuration knob is changed.

What if the encoding specified in the config is not supported by
the iconv library? Do we fall back to LANG or ASCII?

Re-encoding all filenames in a working copy would only be possible
via a new 'svn checkout', I guess. Same as resetting LANG and running
'svn checkout' again.

I recall us having had this discussion before, by the way:
http://svn.haxx.se/users/archive-2011-06/0296.shtml

Another idea: Introduce a new inheritable property that dictates
what encoding clients should be using for filenames. This would
probably be very easy to mess up when multiple client platforms
are involved, but could prevent problems for users who don't set
up their config or LANG correctly where admins just want this to
work out of the box within their own organisation.

> > I don't really understand what kind of answers you are hoping to get.
>
> 'You might have a point there'?

You do. Now please file an issue or send a patch :)

> > Are you actually proposing that we change something in Subversion,
> > or are you arguing out of spite?
>
> False dichotomy? My spite is currently reserved for clearcase.

Ouch. I've seen others feel your pain :( It's not very pleasant indeed.
Received on 2013-07-09 22:48:09 CEST

This is an archived mail posted to the Subversion Users mailing list.