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

Re: Regression in utf-8 log message support?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-11-11 22:01:44 CET

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> $ svn propget --revprop -r 2608 svn:log
> Unversioned properties on revision 2608:
> subversion/libsvn_subr/utf.c:168: (apr_err=22, src_err=0)
> svn: Invalid argument
> svn: failure during string recoding
> $
>
> I'm not sure what to think about that. On the one hand, Brane's
> family name doesn't code in 8859-1. On the other hand, we have
> graceful degradation for 'svn log', so at least the rest of the bytes
> are visible, and probably we should do that when fetching the
> `svn:log' property too.

Interesting, on FreeBSD I get:

$ svn pg --revprop -r2608 svn:log http://svn.collab.net/repos/svn
subversion/libsvn_subr/utf.c:207: (apr_err=22, src_err=0)
svn: Invalid argument
svn: Safe data:
"In revisions 2600 and 2598, the Subversion repository has UTF-8 data
that cannot be converted to ISO-8859-1, among others. (The data is
Branko "
... was followed by non-ascii byte 196.

Non-ascii character detected (see above), and unable to convert to
UTF-8.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 11 22:03:40 2002

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.