On Tuesday 19 October 2004 04:21, Patrick Smears wrote:
> On Tue, 19 Oct 2004, John Szakmeister wrote:
> > > > svn: Valid UTF-8 data
> > > > (hex: 4b 75 6e 73 74 68)
> > > > followed by invalid UTF-8 sequence
> > > > (hex: e4 6e 64 6c)
> > >
> > > This indicates that Subversion has found some data that is not
> > > valid UTF-8. In this instance, the text appears to be
> > > 'Kunsth{a-umlaut}ndl', but encoded in ISO-8859-1 rather than UTF-8.
> > >
> > > Perhaps changing to a locale based on ISO-8859-1 will allow you to
> > > proceed?
> >
> > Nope. Subversion doesn't care about the encoding of file contents.
>
> No - but it does care about the encoding of the file *names*, as
> discussed on this list before :-) Sorry if my wording was unclear on
> this point...
It came across as though you were talking about the file contents... yes,
you are correct, filenames do matter. In this case though, the command
like didn't show the presence of the 'Kunsth{a-umlaut}ndl', which means
the error looks like it's in the log message itself.
> > However, it does care about the log message. If you're using a UTF-8
> > locale, the log message should be valid UTF-8 as well.
>
> But yes, my comments re: filenames would also apply to the log message,
> thanks!
Yes it does! :-)
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 19 11:07:41 2004