[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-11-30 17:11:26 CET

On Tue, 30 Nov 2004, VK Sameer wrote:

> On Tue, 2004-11-30 at 04:47, kfogel@collab.net wrote:
> > kfogel@collab.net writes:
> > > In order to solve this, we need to know exactly what can be
> > > *represented* in an attribute value. Do we know the answer to that
> > > yet? (For example, can we represent all valid UTF8 paths in an XML
> > > attribute value?)
> Wouldn't this depend on SVN's definition of a valid pathname? Could that
> be settled first?
The problem is that these questions are interrelated. If we had been able
to represent control characters in XML using character references, then we
would have no compatibility problems, since the parser would handle the
parsing (really?:-) for us. Since we can't do that, we would have to
introduce new mechanisms to represent a few IMO very useless characters in
the XML and add compatibility stuff for this. Therefore, it makes sense to
know what is well-formed XML before making the decision.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 30 17:16:55 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.