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

"Can't recode string" again...

From: Gunter Ohrner <G.Ohrner_at_post.rwth-aachen.de>
Date: 2005-12-30 01:06:33 CET


I already found a few references to this error but no discussion seemed to
give a definitive solution to this problem.

Client: svn 1.2.3, LANG=de_DE@euro (ISO 8859-15), Filenames with umlauts
Server: svn 1.1.1, bdb 4.2 backend, using svnserve, "C" locale

Problem: checkin was successful. Subsequent commits in a directory with
umlauts now cause the error message "svn: Can't recode string".

strace shows that this error message is generated by the *server* process:

,----[ ]
| write(3, "( 2 ( edit-pipeline )
| 41:svn:// ) ", 69) = 69
| read(3, "( failure ( ( 22 19:Can\'t recode string
| 28:subversion/libsvn_subr/utf.c 363 ) ) ) ", 4096) = 82

This is what I do not understand. I always thought subversion would
normalize all strings to UTF-8 before juggling with them, so I'm wondering
why the server process complains, it should not have to recode anything?
The URL it gets looks like url-encoded UTF-8 to me...



The duke had a mind that ticked like a clock and, like a clock, it 
regularly went cuckoo.        -- (Terry Pratchett, Wyrd Sisters)
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 30 01:08:02 2005

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