Re: utf-8 sanity check.

On Thu, Jul 11, 2002 at 04:44:52PM -0500, Ben Collins-Sussman wrote:
>...
> > > Ben Collins-Sussman <sussman@collab.net> writes:
> > > > Use --locale:
> > > >
> > > > * to specify the charset of the log message being read by -F
> > > >
> > > > * to interpret working copy paths that will be read later on
> > > > (i.e. 'svn up', with no args)

Bah. The environ variables should be used.

> > > I'm not sure I understand the latter scenario... ?
> >
> > I'm not sure that makes much sense either. The only possible reason to
> > do this that I can think of is mounting a hard drive that was created a
> > completely different codepage compared to the default codepage. Even
> > then, I'm still not sure that the intervening layers could handle that.
> >
> > No harm gained in supporting it of course.
>
> The point is, '--locale' is simply a way of manually overriding the
> system locale. At a minimum, it's useful for testing our utf-8
> abilities in a python test, no? :-)

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.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org