Torsten Krah wrote on Mon, May 30, 2011 at 23:47:30 +0200: > Am Dienstag, den 31.05.2011, 00:30 +0300 schrieb Daniel Shahaf: > > Solution is to recode the pathnames (those that are neither in ASCII > > nor in UTF-8). > > Sorry but your "solution" seems really a little bit odd to me. > If <1.6 did not enforce this and 1.6 does - why does 1.6 not recode it > at the time it does encounter such "things" - at least via some optional > command line option? > > Do you really want to tell me that subversion (the "tool" used to manage > my code) is not able to load its own "dump", at least by providing some > "fix" tool by itself if it did things not "right" before - why should i > need or bother with "third-party" tools here - this should be done by > svn, shouldn't it? >
As Stefan said, it would be nice if Subversion itself could fix that, given that old released versions produced such (malformed) filesystems. To my knowledge, currently there is no code in Subversion itself to do this, hence my suggestion to use third-party tools. > > If none of the third-party dump manipulation tools can do > > that, > > Which "third-party" tools you have in mind are able to do that for me? > I know there are a couple of dumpfile manipulator tools that are regularly suggested around this list, but I don't have a specific recomendation. One of the other list members might be able to answer this question.
