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

Re: issue #1954 (was: Re: Supporting non-XML-safe pathnames)

From: <kfogel_at_collab.net>
Date: 2004-12-01 17:33:30 CET

Thanks folks for clarifying my mistaken idea of what is valid in XML
1.0 and 1.1. I now grok the situation...

VK Sameer <sameer@collab.net> writes:
> Wouldn't this depend on SVN's definition of a valid pathname? Could that
> be settled first?

I'm happy with just UTF-8, that is, no control chars except LF, CR,
and TAB.

(In one mail, Julian Reschke wrote "SP" where I think he meant "LF".
Obviously, we would allow SP, it's just that it's not a control
character, whereas LF is. Both are allowed.)

> Once the definition is settled, if a valid pathname contains UTF8
> characters not in the XML 1.0 legal character set, then it would require
> escaping/base-64 encoding before use as an attribute value.

Okay. +1 on prohibiting control characters except LF, CR, TAB. I
doubt any users are going to suffer much if we do that. There doesn't
seem to be much opposition to it on this list either (am I forgetting
anyone?), and clearly it'll make Peter Lundblad very happy :-).

Does anyone object to VK Sameer proceeding along those lines?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 1 17:39:10 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.