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

Re: Call For Votes: converting log messages to UTF-8

From: Marcus Comstedt <marcus_at_mc.pp.se>
Date: 2002-06-05 00:20:22 CEST

=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:

> >How (when) will the --locale option affect the locale setting? If I
> >do
> >
> > svn -m 'log message' --locale zh_TW.BIG5
> >
> >should this be interpreted differently from
> >
> > svn --locale zh_TW.BIG5 -m 'log message'
> >
> >? Environment variables are simpler because they are always set
> >before the program execution starts.
> >
>
> The order of options never matters. --locale is interpreted in main(),
> along with the other options, and before any real work is done.

I know where --locale is interpreted. But I also know that the -m
would get interpreted before it in the first example, and that it
might have made sense to do any conversion there. But if that is
qualified as "real work" and such is not allowed to be done during
option parsing, then I guess I'll just have to rewrite my UTF-8 patch
a little. (Not becase of the log message (which is translated later
anyway), but things like username and password which I translate
directly during the option parsing pass.)

Btw, is creating an error message "real work"? That can happen during
option parsing, requires an UTF-8 conversion, and would be very
awkward to have to defer.

  // Marcus

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 5 00:25:00 2002

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