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

Re: New entries file format.

From: by way of Peter Davis peter_at_pdavis.cx <peter_at_pdavis.cx>
Date: 2003-01-28 07:47:13 CET

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[Dag Nammit, forgot to CC the list again.]

On Monday 27 January 2003 21:43, cmpilato@collab.net wrote:
 Peter, it seems that what we need to escape in attributes is a
 superset of what needs to be escaped for CDATA.

 So rather than using two different escape routines, how about a flag
 to the escaper which sez use the extra attribute escaping rules,
 too?

I thought of this, but of course it would require changing all the call
points to use the additional attribute. No problem though.

 Also, is it safe to trim that list of extras to just CR, LF, and Tab
 (I really don't wanna see the most common whitespace
 character--Space--escaped if I don't have too)?

- - From reading the spec, yes, it appears that is OK (assuming of course
 that *all* attributes are always CDATA according to the DTD (or lack
 thereof)).

 Finally, you agree that we should *stop* escaping ' and in CDATA
 (that those belong in the only for attributes group), yes? I
 believe we only do that because our xml-escaper is used for atts and
 CDATA, and we knew we needed those escaped in atts.

Yes.

As I said in the issue, would you mind if I wrote this patch, if you
haven't already started (with the addition of numeric character refs in
xml_unescape)?

- --
Peter Davis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+NidyhDAgUT1yirARAmENAJ4qaI0RYs+rftI2qUgEInPDPdAENQCgkO/J
otPyZ4INUYPcBoBFXHNI7Yw=
=V/YF
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:21:22 2006

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.