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;.
I tend to disagree as well. Apart from meaning that someone else has to
check what &content; means,
<xsl:if test="..">
&content;
</xsl:if>
visually looks to me much more like
<xsl:if test="..">
stuff
</xsl:if>
than
<xsl:if test="..">
<xsl:value-of select="."/>
</xsl:if>
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 "
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.
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?
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--