Non unicode characters in log messages

[Trent Fisher]

I think I found a bug relating to handling of non-unicode characters in 
log messages.  When I do an "svn log" via the file:// url it works fine, 
but when I do it via http:// the history is truncated and ends with this 
message:

svn: REPORT of 
'/svn/tugbu/!svn/bc/236146/QA/CCB/main%20V2.4.X/Documentation/Test%20Plans/Rate%20Engine/Version%202': 
200 OK (https://adc4110279.us.oracle.com)

I figured out that the next revision which would have been displayed 
contained non-unicode characters.  From what I have gathered via some 
Google searches, Subversion shouldn't accept such things, though old 
versions did, and svndump load will let such things in (which means I 
have a bug in my import script).

One side effect of this "error" is that TortoiseSVN thinks the sever has 
gone down and offers to go into offline mode.

If I got rid of the non-unicode characters in the log message, that 
error went away.  FYI the following command seemed to do the trick for 
getting rid of the bad characters, since propget displayed the bad 
characters with backslash escaped octal sequences (i.e. ascii).

svn propget --revprop -r236146 svn:log file:///scm/svn/repos/tugbu | svn 
propset -F - --revprop -r236146 file:///scm/svn/repos/tugbu

So, it seems to me that this is a bug.  Subversion should degrade in a 
more graceful way when this happens, no?  I looked a bit through the 
Issues list, but didn't see anything like this.

++thanks,
trent...