[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Why "invalid UTF-8 sequence" also on ignored files?

From: Markus Fischer <markus_at_fischer.name>
Date: Tue, 24 Feb 2009 12:26:07 +0100


I was puzzled today when I saw this

$ svn status
svn: Valid UTF-8 data
(hex: 31 34 32 38 5f 73 74 75 70 70)
followed by invalid UTF-8 sequence
(hex: e4 63 6b 5f)


$ svn --version
svn, version 1.5.1 (r32289)
    compiled Dec 31 2008, 06:38:09

I converted the hex sequence and it turned out to be a filename,

I searched for this filename, and to my surprise this file was, due
svn:ignore set on its directory, actually on the ignore list, but
nevertheless caused this message:

markus_at_dev01:/data/legacy/depression.at$ svn status
I apachewrite/mediencache/1428_stuppäck_neu.gif

Is this deliberately? It is somehow inconvenient because it seems the
ignoring of files doesn't properly work when files contain
out-of-the-current-locale characters.

But then, I was already puzzled that my find command turned up empty:

$ find -iname 1428\*

I had to unset the locale, then it worked:

$ unset LC_CTYPE
$ find -iname 1428\*

So all in all probably an expected edge case ...?

thanks for any tips,
- Markus


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-24 12:31:48 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.