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

Re: Locale Issue in Subversion checkout with svn:keywords

From: Konstantin Kolinko <knst.kolinko_at_gmail.com>
Date: Fri, 8 Jul 2011 07:54:23 +0400

2011/7/8 BRAGA, Bruno <bruno.braga_at_gmail.com>:
> On Thu, Jul 7, 2011 at 11:26 PM, Konstantin Kolinko <knst.kolinko_at_gmail.com>
>> 2011/7/7 BRAGA, Bruno <bruno.braga_at_gmail.com>:
>> >(...)
>> >
>> > So, I was wondering if there is any way to set the locale of the SVN
>> > client
>> > in a server, to ensure it will always checkout using a certain locale
>> > (of
>> > course, English). Doing so in Japanese or Chinese, for instance, messes
>> > up
>> > with the compilation of files, if you have enforced locale tags en every
>> > file. One good example if the $Date $ keyword, which gives the date in
>> > Unicode chars for Japanese.
>>
>> 1) Do not use $Date$. It is not for you. It 1) uses local timezone, 2)
>> uses utf-8 regardless of the actual file encoding. Forcing a locale
>> would not solve 1).
>
> Yes, we are curently using something like:
> $ export LC_MESSAGES='en_US.UTF-8' && svn co ...
>
>>
>> 2) Do not use $Id,  if you have non-english characters in committer
>> login names or in file name (because of utf-8, see above)
>
> Hum... I did not know that we were not supposed to use this... At lest it is
> good to know that this is the solution.

The UTF-8 issue that I mentioned is known as
http://subversion.tigris.org/issues/show_bug.cgi?id=2332

>>
>> Any other keyword is causing trouble?
>
> We did not have problems with the $Id, only with the $Date. But I will
> follow your suggestion, and remove both.
>
> However, it kind of kills the merit of using svn:keywords, at least for us.
>

Best regards,
Konstantin Kolinko
Received on 2011-07-08 05:55:17 CEST

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.