On 09.07.2013 22:47, Stefan Sperling wrote:
> 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.
Sorry, I have to ask, useful *how* exactly? There is already a perfectly
valid workaround for the case that Andreas is talking about, namely,
relieving scripts authors from the complexity of parsing multi-lingual
responses. It's just that that perfectly valid workaround happens to not
be "env LANG=C".
Why invent another configuration knob that you already know (given the
rest of your post) is going to cause all sorts of trouble?
-- Brane
--
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane_at_wandisco.com
Received on 2013-07-09 22:54:32 CEST