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

Re: python svn.wc.revision_status unicode handling bug

From: Wesley J. Landaker <wjl_at_icecavern.net>
Date: Sun, 27 Jan 2008 14:12:54 -0700

On Wednesday 23 January 2008 19:13:31 Eric Gillespie wrote:
> I doubted that could be the case here, and realized I never tried
> running svnversion myself. I just did so, and got:
> subversion/libsvn_subr/utf.c:543: (apr_err=22)
> svn: Can't convert string from native encoding to 'UTF-8':
> subversion/libsvn_subr/utf.c:541: (apr_err=22)
> svn: I?\194?\178C_dir

What platform are you running on? The error you are getting with svnversion,
I don't get, and it's understandable: I am running on Debian GNU/Linux,
with a UTF-8 locale. The filename I²C is already in correct UTF-8, and the
locale is UTF-8. There is no problem converting it the filename (in UTF-8)
from my locale (UTF-8) to UTF-8. =)

The string "I?\194?\178C_dir" in the error message you printed above looks
like correct UTF-8, but it seems like you don't have a UTF-8 locale, so of
course my example tarball didn't work in that case--it made an invalidly
encoded UTF-8 "I²C" string in your filesystem.

Anyway, I think the error as I reported -- failing in the python bindings,
but not with svnversion is still valid. Is anyone else interested in
investigating this?

Wesley J. Landaker <wjl_at_icecavern.net> <xmpp:wjl_at_icecavern.net>
OpenPGP FP: 4135 2A3B 4726 ACC5 9094  0097 F0A9 8A4C 4CD6 E3D2

Received on 2008-01-27 22:13:16 CET

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