Hi Snow The encoding of that commit comment is ISO-8859-1. Obviously, since there used NOT to be a problem with this, something new in your code is requiring you to be able to parse or convert all ... [More] strings to unicode. The degree chararacter is obviously a legal UTF-8 character (basically every character is a legal UTF-8) character. The question here is one of encoding. It really doesn't bother me if ohloh just drops those non-parsable characters. Given that the ISO-8859-1 charset will have been used by a reasonable number of western european coders, especially going back to the mid-early 00s and before, I would imagine that you can't really get away telling everyone to change their old commit comments to UTF-8...? Cheers JP [Less]

Thanks Patrick, I can see that it's running again. I'll take a careful look when it's finished.

I had a problem checking out this revision, too. I get this error: svn: In directory 'ascend-416/pygtk/interface' svn: 'ascend-416/pygtk/interface/.svn/tmp/text-base/config.guess.svn-base' has ... [More] unsupported special file type '#!' I am able to look at this file in ViewVC however: http://ascendcode.cheme.cmu.edu/viewvc.cgi/code/trunk/pygtk/interface/config.guess?revision=416&view=markup&pathrev=416 In there, you can see that the file starts with #! /bin/sh (note the space after the #!). I'm not clear why svn would be spitting the dummy here... what would I do to fix the repository in this case? [Less]