[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 15:49:21 +0100

Vincent Lefevre wrote:
> On 2008-02-18 13:05:06 +0100, Branko Čibej wrote:
>> 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).
> No, transliterating does not work with svn (though iconv is OK):

Please don't be deliberately obtuse. We don't do transliteration because
we don't try to determine if the provided iconv supports it. What you
see is deliberate; not nice and sexy, but deliberate and not a bug.

> some
> kind of warning or other way to inform the user would be useful, because
> some information is lost after a transliteration.

So what? Who cares about "some information lost" in a log message
printed to the console? If you're wrapping the svn command-line client
and find that to be a problem, use "svn log --xml".

Or use an UTF-8 locale.

-- Brane

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 15:49:50 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.