Re: i18n and wrapper-tools

On Tue, 10 Jul 2001, Branko [ISO-8859-2] �ibej wrote:

> Perhaps, in order to support such tools, might we consider adding a
> "--setlocale=name" switch to svn, that would override the locale defined
> by the environment? For one thing, that would work on non-Unix platforms
> that don't have env; for another, it would help test the various
> translations, once we have them.

The latest version of Perforce officially introduced a command-line switch
that forces all output into marshalled Python data structs. While I don't
like the idea of tying so tightly to one wrapper language, the idea of
providing special modes that actually return output in script-friendly
form is a good one...

        svn --setoutputmode=XML ...
        svn --setoutputmode=Python ...
        svn --setoutputmode=Perl ...

I agree with the earlier thread that argued in favor of using the APIs
over wrapping scripts, but there -are- some environs in which
wrapping the script is preferable (emacs, for instance, seems such a
case).

-- 
   Tripp Lilley  *  http://stargate.eheart.sg505.net/~tlilley/
--------------------------------------------------------------------------
   "I've been so weird it would have killed a normal man."
   It Is What It Is - Bruton / Fleming (performed by The Highwaymen)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org