On Mar 17, 2006, at 18:41, Carsten Fuchs wrote:
> Carsten Fuchs wrote:
>> b) Whenever a non-ASCII character occurs, either in a file-name,
>> in the contents of a file(!), etc., svn aborts with the error
>> message:
>
> I think that this statement is not quite right, as I just observed
> that as with a), the problem character did not origin from a file
> (name), but from svn output. E.g. the "svn diff" command tried to
> print "Property changes on: ...", which in German contains the "ä"
> Umlaut: "Eigenschaftsänderung auf: ...", and so the error message
> that I get in fact reads: "svn: Auf sichere Daten 'Eigenschafts'
> folgte ein nicht-ASCII Byte 195, das nicht von/nach UTF-8
> konvertiert werden konnte"
>
>> [...]
>> --> What can I do to fix this? Especially b) is a serious problem
>> for me. I've searched the mailing-list archives in this regard and
>> found several suggestions to set one of the LANG environment
>> variables, but I've not been able to solve the problem in spite of
>> extensive tests.
>
> Setting LANG=en_US "fixes" the problem, as there are no umlauts in
> English. So I currently use that setting as a work-around, but
> would still be interested in learning of there is a more generic
> solution.
Which server are you using? Is it by chance svnserve? If so, is the
locale on the server a different one than on the client, keeping in
mind the charset? For example, is the de_DE locale on the server
using UTF-8 while the de_DE locale on the client is using
ISO-8859-15? There was this issue I discovered recently which may
relate:
http://svn.haxx.se/users/archive-2006-03/0494.shtml
This problem of "valid UTF-8 data followed by invalid sequence" comes
up far too often on this list, and I'd like to finally get to the
bottom of it and solve it once and for all.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 17 20:12:57 2006