David Carlisle <davidc(_at_)nag(_dot_)co(_dot_)uk> wrote:
I tend to disagree. Someone who is used to reading XSLT code but unused to
your personal coding style will recognize <xsl:value-of select="."/> far
more quickly than they recognize &content;.
Fair point.
But the behaviour is very different. With value-of (or any element)
the white space used for indentation is stripped, but with "stuff"
it is not and the text node generated has content " stuff "
Hmmm... OK. They don't tell you *that* in "SAMS Teach Yourself XML in
10 Nanoseconds" ;-)
Also some XML parsers (notably msxml) default to validation mode when
they see a doctype so try to validate the stylesheet which generates
lots of spurious errors.
Also good to know.
The one thing nxml-mode doesn't do is tell you exactly
where your document becomes invalid.
It sticks a big red line to mark the spot doesn't it?
Er... no. Not here. Maybe because I use a text console? I'll check
it under X when I have a moment. Thanks for all your comments. The
&content; substitution policy is under review ;-)
sdt
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--