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

Re: Spam:Re: Locale used when expanding keywords ($Date$)

From: Ryan Schmidt <subversion-2006d_at_ryandesign.com>
Date: 2006-10-25 21:12:27 CEST

On Oct 25, 2006, at 06:42, Michal Palička wrote:

>>> is there any way to change the behavior of the SVN client related to
>>> keyword expansion?
>>> It seems that the client uses the current locale to expand $Date$.
>>> This causes a problem for us. We use Czech locale and the result of
>>> the expansion contains east-european (non-ascii) characters that are
>>> specific for our language (usually in the abbreviated name of the
>>> day).
>>> When the expansion occurs in an XML file (which contains ASCII
>>> characters only), then the parser expects its content to be
>>> encoded in
>>> UTF-8 (because of the regional characters).
>>> The parser rejects such a file as corrupted.
>> No solution at this time that I'm aware of. Well, you could set
>> LANG to C or some other locale that uses only ASCII characters.
>> This seems to be this issue:
>> http://subversion.tigris.org/issues/show_bug.cgi?id=2332
> Well, I tried to change the locale to en_US.
> Now, the expansion works fine and the file encoding isn't changed.
> The problem is, that I can't change the locale for specific
> application (e.g. in a batch file).
> I use Windows and the only possibility (AFAIK) is to change
> the current user's locale through ControlPanel-->Regional Settings.
> This method affects all applications.
> I would like to use Czech locale as the default and be able to set
> the en_US only for my Subversion client (command prompt window).
> Is something like that possible in Windows?
> LANG=C works on Unix.

Not sure; I don't use Windows.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 25 21:13:17 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.