thanks for your reply.
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.
From: Ryan Schmidt [mailto:email@example.com]
Sent: Monday, October 23, 2006 19:55
To: Michal Palička
Subject: Spam:Re: Locale used when expanding keywords ($Date$)
On Oct 23, 2006, at 06:59, 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
> 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:
> It would be nice, if the SVN client could be told to use some specific
> locale (e.g. en_US)
> - instead of the current one. Alternatively, the server's locale could
> be used.
> When the development team is located in multiple countries, the $date$
> is shown in multiple formats (locales). Which is also confusing.
I don't think that should be the case, since the keyword substitution happens entirely on the client side, so unless you're checking out a working copy, then changing your locale on your client, then updating, all the keywords should be expanded in a way that makes sense to you, locally.
> I found some similar posts from the past years, but none of them
> contains any reasonable solution:
> Does the current SVN version solve this problem?
> Are there any plans to modify the client in relation to locale usage?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Oct 25 15:25:05 2006