[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: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2004-12-01 21:22:47 CET

On Wed, 1 Dec 2004 kfogel@collab.net wrote:

> 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.
By "just UTF-8" it seems like you're still mixing what's valid UTF-8 and
what are valid XML 1.0 characters. Just wanting to make sure there is no
confusion left here. Control chars are valid UTF-8 but invalid in XML 1.0,
wherever they occur. You just can't have them, without another layer of
encoding. And a correct XML parser shouldn't give the application any
control chars (except the whitespace ones named above).

> > 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 :-).
Hehehehe... Somewhere, I rembember having seen something about newlines
and the dump format. If there is a problem there, we need to ban it as
well. I don't know. Else, +1 from me as well.


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