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

Re: utf-8 sanity check.

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-07-12 00:16:49 CEST

Greg Stein <gstein@lyra.org> writes:
> Not at all. The Python test can easily set the appropriate locale environ
> variable before executing the test process (the exec*e functions).
> $ svn --locale=FOO status
> $ LC_CTYPE=FOO svn status
> They're the same number of characters, so don't even try to say "well, it is
> easier to type". Why are we writing code for this? The system environment
> variable is the defined way to handle this stuff. Why invent something new?
> IMO, it was a mistake to put in initially, and a mistake to retain/fix.

As long as we have a way of doing this in environment, at run time, on
all supported platforms, then I'm +1 on removing the option as well.


   $ LC_CTYPE=FOO svn status

will not work on non-Unix, and won't necessarily even work in all Unix
shells, right? Not saying that's a showstopper, just want to know
what the right solution *is* for those other situations...


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 12 00:27:39 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.