> -----Original Message-----
> From: Daniel Shahaf [mailto:d.s_at_daniel.shahaf.name]
> Sent: dinsdag 31 mei 2011 0:10
> To: Torsten Krah
> Cc: users_at_subversion.apache.org
> Subject: Re: svnadmin: Path '....' is not in UTF-8 - svnadmin load fails
>
> 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.
The problem is: We just know it isn't utf-8. But that doesn't tell us how to
fix it.
But which encoding does it have, if it isn't utf-8 as expected?
Without telling Subversion could choose from hundreds of different encodings
(iso-8859-1?, etc., etc.), which might just contain the one you would like.
(Or maybe your filesystem used format 101).
Subversion defines that it must be utf-8, so it can't answer this question
for you.
Bert
Received on 2011-05-31 13:47:05 CEST