Re: i18n and wrapper-tools

Tripp Lilley wrote:

>On Tue, 10 Jul 2001, Branko [ISO-8859-2] E`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 ...
>

Yes, that would be nice to have, someday. Or even
"--output-filter=path/to/libsomething.so", if you want complete
flexibility. But "someday" is definitely the watchword here. :-)

We'll start with "--setlocale", which avoids the real problem we'd have
in the presence of l10n. Let's defer other possibilities to post-2.0.

>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).
>
Right. I may not like it, but I agree.

Brane

-- 
Brane �ibej
home: <brane_at_xbc.nu> http://www.xbc.nu/brane/
work: <branko.cibej_at_hermes.si> http://www.hermes-softlab.com/
ACM : <brane_at_acm.org> http://www.acm.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org