On Fri, Aug 13, 2010 at 12:27:30AM +0200, Vincent Lefevre wrote: > On 2010-08-12 17:16:37 +0200, Stefan Sperling wrote: > > 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? > > With the current situation, a "svn up" run under the non-UTF-8 locale > will either fail or corrupt the working copy if some filenames have > non-ASCII characters. With UTF-8 recorded as the encoding for > filenames, "svn up" will always work. See the difference?
Yes, I see the difference. It's a question of where the primary configuration knob for the charset is located. Right now, the source of charset information is always the locale. You want it to be the locale at checkout time and some pre-recorded value at update time (not sure what your idea is about all the other subcommands). But I don't think having two sources for this information is a good idea. So I think Subversion should continue trusting users with setting their locale. It's simple. It works. But that's *my* opinion. We do lazy-consensus based development. So talk to other people in the community if you like, and if you can convince a majority of them, we can do it your way. Stefan
