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

Re: Supporting non-XML-safe pathnames

From: Jon Foster <jon_at_jon-foster.co.uk>
Date: 2004-11-27 01:01:12 CET


Peter N. Lundblad wrote:
> On Wed, 24 Nov 2004 kfogel@collab.net wrote:
> We need a new function to check if a path
> is valid. It should accept valid UTF8 and reject control chars (0-0x1f,
> 0x7f, 0x80-0x9f) and possibly other non-Unicode characters.

I posted a first draft of a patch to try and do this a while ago;
unfortunately I've been distracted by other things and I'm not able
to work on this any more. If someone wants you can probably find my
patch in the list archives, or ask and I'll send you the latest version.

Peter N. Lundblad wrote:
>The difference between NUL, COM1 and others and control chars is that the
>latter will give corrupt XML errors. So this is not the solution for that.

But it would be nice if SVN checked for NUL, COM1 etc when checking out on
Windows, and gave an informative message. My patch tried to do this.

Kind regards,


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 27 01:03:18 2004

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

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