Typically I'm using
<xsl:template match="element">
&nl;[begin thisLabel: ]
well you've got two newlines there, one after the > and one inside the
entity ref. unless you really want two newlines it would be simpler to
go
<xsl:template match="element">
[begin thisLabel: ]
XSLT1 is delightfully quiet about newlines in text output (XSLT2 is more
explict and usefully states that #10 characters will, as in xml output,
produce a system specific line end).
However xslt1 is silent so if you are on dos and want to generate a crnl
pair then you probably have to use
<xsl:text> </xsl:text>
as your
<xsl:text>
</xsl:text>
is equivalent to
<xsl:text> </xsl:text>
even if the file has dos line ends as teh xml parser normalises all line
endings to #10 on the way in.
The xslt2 wording allows the text serialiser to write out
<xsl:text> </xsl:text>
as a #10 #13 pair if it is on DOS but I don't think teh XSLT1 wording
really lets the system do that.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list