On Tue, 2004-11-30 at 04:47, kfogel@collab.net wrote:
> kfogel@collab.net writes:
> > VK Sameer <sameer@collab.net> writes:
> > > I'm not particularly interested in having filenames with control
> > > characters, it removes an easily creatable test case, for one :) It just
> > > happened to be a lead-in to non-XML-safe pathnames.
> > > But I am concerned about using svn_xml_is_xml_safe as it stands now as
> > > it doesn't reject of other invalid characters. I've attached a list of
> > > accepted characters to this email, please take a look.
> >
> > I'd like to take a deep breath and get an overview of this issue
> > again. I've rethreaded it so it refers to issue #1954.
> >
> > The Problem:
> > ============
> >
> > On the client side (and maybe over the wire, in DAV?) we use XML
> > attributes to hold path names, at least basenames. Thus, any
> > character that cannot be represented in an XML attribute value cannot
> > be used in a filename. Note that this is *not* the same as
> > prohibiting characters which cannot appear directly in an attribute
> > value. Some characters cannot appear directly, but perhaps can be
> > represented by escaping.
> >
> > 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?
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.
Sameer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 30 10:40:32 2004