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?)
>
> Once we know the answer to that basic question, we need to decide what
> subset (possibly the entire set) we want to support.
>
> VK Sameer, is this a reasonable summary? And do you happen to know
> the answer to the first question?
Okay, after some research to aid my always-sieve-like memory, it looks
like any character can be encoded in an XML attribute using typical
"&" char encoding, as in:
<element attr="look_I_have_a_quote_"_in_my_value"/>
So, we can represent any UTF8 string we want, right?
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 30 00:22:19 2004