[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: Branko Čibej <brane_at_xbc.nu>
Date: 2002-06-05 00:35:41 CEST

Greg Stein wrote:

>On Tue, Jun 04, 2002 at 10:56:08PM +0200, Branko Äibej wrote:
>
>
>>Greg Stein wrote:
>>...
>>
>>
>>>Nope. We don't have to do anything. The user can always do:
>>>
>>>$ LC_CTYPE=some.locale svn commit -m "log message"
>>>
>>>That sets the LC_TYPE environment variable for just the one execution of the
>>>'svn' program.
>>>
>>>
>>Please, let's just for once hear some design discussion that doesn't
>>assume all the world is Unix. What you propose only works in Bourne-like
>>shells (even the csh incantation is different).
>>
>>
>
>The point is: it is simple to tweak your environment for an invocation. Our
>defined way to get the locale is the environment variables. Why have more
>than one way to do the same thing?
>
>Regarding non-Unix: in the part of my email (which you cut :-), I pointed
>out how other clients (e.g. a nifty Windows client) can adjust its character
>set as much as it wants.
>
But I want to use the command-line client on Windows (perhaps with
Emacs), and I'm not aware of an environment variable that would reliably
change the locale there. That's why I'd rather use a switch, which will
work the same way on all platforms..

>>We already have a --locale option. It was introduced so that front-ends
>>that wrap the command line client (and there will be such; Emacs vc-mode
>>comes to mind) will get predictable output in the presence of localized
>>messages.
>>
>>
>
>And I might debate its proper existence. It was added *long* before we had a
>plan for i18n or l10n. I think it was totally premature, and it shouldn't be
>a justification for other behavior.
>
>
>
>>We might as well reuse that, or introduce a similar option
>>(--input-locale?) for log messages, file names, prop names, etc. I'd
>>support that, FWIW.
>>
>>
>
>I don't think that adding more switches is the answer. There is already a
>mechanism: it is called LC_CTYPE.
>
>Heck, I will suggest right now: let's eliminate the --locale option. I see
>no point in the switch. It has unknown effects, and it isn't even used
>reliably (i.e. it won't meet user expectations).
>
Yes it will, provided we document that the only reliable, portable use
is "--locale=C" -- which usage, btw, is the whole point of having such a
switch.

>When we have an i18n plan post-1.0, then we can reintroduce the switch *if
>it is needed*.
>
>

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
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:36:09 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.