Re: Broken SVN revision paths encoding

2015-07-28 Thread Dominik Psenner
Thanks Bert for your answer. I've used the latest tortoisehg which used to ship the subversion bindings but stopped to do so. That is entirely documented here: https://bitbucket.org/tortoisehg/thg/wiki/libsvn The server on the other ends dates back to 2011. I believe it is something along 1.4, bu

Re: Broken SVN revision paths encoding

2015-07-28 Thread Bert Huijben
What client (including version) did you use to commit… and against what kind of server? Subversion's clients properly encode characters to utf-8 as far as we know, but perhaps you used some not standard client for the commit. (Newer servers should perform more verifications; that is why that a

Broken SVN revision paths encoding

2015-07-28 Thread dpsenner
Hi there, Somehow I was able to commit a file with a broken filename encoding and now the svn client can no longer process the log messages from the server! For example I commited the file “fooä.bar” and when I then try to svn log I get this: svn: E130003: The REPORT response contains inval