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

Re: svn log behaves strangely when characters cannot be represented in the local charset

From: Branko Čibej <brane_at_xbc.nu>
Date: Mon, 18 Feb 2008 13:08:39 +0100

Branko Čibej wrote:
> Vincent Lefevre wrote:
>> When in a log message, some characters cannot be represented in the
>> charset specified by the current locale, all the non-ASCII characters
>> are silently converted in a strange format, e.g. I get:
>>
>> Test caract?\195?\168re non ISO-8859-1: ?\226?\134?\146
>>
>> in ISO-8859-1 for the log message:
>>
>> Test caractère non ISO-8859-1: →
>>
>> I don't think such a format is useful in practice. For this reason,
>> not outputing a warning to stderr (telling which revisions could not
>> be handled correctly) and not terminating with a non-zero exit status
>> is a bug, IMHO.
>>
>> Tested with svn version 1.4.6 (r28521) under Debian/unstable.
>>
>
> That log message is in UTF-8, which is perfectly OK. Subversion will
> convert that to you locale's encoding if it can; if not, it will
> "transliterate" (but not really; we need a real transliterating
> iconv). Set your locale correctly and that "svn log" output will go away.

And by the way, "svn log" should *not* terminate with an error just
because it can't display a log message prettily.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-18 13:09:00 CET

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

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