Greg Hudson wrote:
> On Tue, 2006-07-18 at 10:44 +0200, Philipp Marek wrote:
>>On Sunday 16 July 2006 11:21 Philipp Marek wrote:
>>>But the question would remain! It's not possible to allow *every* character
>>>in filenames, else eg. the dump format may be damaged (by \n in filenames).
>>>Similar a \r may cause problems on win32, and so on ....
>>To reiterate: It *is not possible* to allow all characters, so there has to be
> Encoding and decoding is only one answer; disallowing problematic
> characters is another, and I think that option is more palatable to
> Retroactively introducing an encoding and decoding mechanism for paths
> also creates some versioning issues, particularly with the dump format.
> If I have a file named tab\x09name today, that fits in the dump format
> just fine, but you'd be changing the meaning of said dumpfile in future
> versions of Subversion.
Well, not really. You'd have to have a file named tab\x09name that also
carries the svn:filename-encoded property. Since you shouldn't have been
using properties in the svn: namespace anyway, I'd be far less inclined to
have pity for you.
C. Michael Pilato <email@example.com>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Tue Jul 18 17:37:52 2006