>> Just to make things clear :
>>
>> * The clients are Mandrake 10.0 Official (subversion 1.0.1) and
>> Windows XP Pro (TortoiseSVN 1.0.3, Build 968). Actually, I have the
>> same problem from both clients ... which might mean that the problem
>> is on the server, or that one of the client corrupted the repository ...
>
>
> In that case, yes, it looks like the problem is on the server side. On
> the other hand, changing LANG on the client side does make a difference,
> so the problem's probably a bit more complex than that.
According to Ben Collins-Sussman in a post a few minutes ago:
> * The Subversion repository demands that all paths and
> commit messages be stored in UTF8. This means that when
> committing, the client will attempt to convert local paths
> (and commit messages) to UTF8, and when doing a checkout/update,
> it will attempt to convert UTF8 paths back into native locale.
> So if a user commits a Chinese filename, that's fine, but
> then you better make sure every other user has a locale
> capable of representing that filename.
It's up to the client to convert the filename from the local filesystem
encoding to UTF-8. Therefore a broken client could well send invalid
UTF-8 to the server.
I don't know whether clients such as TortoiseSVN or previous versions of
apr or svn on Linux used to be broken. Maybe someone else can comment on
that.
Also, does the server always check the received filename is correct
UTF-8? If not, or if previous versions of the server did not, then the
repository could well contain filename that are invalid UTF-8 as sent by
a broken client.
Other than that, I can't explain why you would get ther error message.
Dimitri
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 24 17:06:43 2004