Unfortunately, I haven't attempted writing extension elements -- just
functions -- and I've got my head so entangled in XSLTC revisions that I'm
not sure I remember the details of how interpretive Xalan is handling
either. So the following may be completely off base. But...
If your xsl:output specifies indentation, that will create whitespace where
the serializer thinks it might be useful; this feature doesn't directly
affect whether whitespace from the source is preserved. So I *think* you're
going to lose the whitespace from your param value, unless you start
playing with xml:space and xsl:preserve-space. I'd have to play with it to
be sure.
If we presume for a moment that extension elements aren't doing anything
blatently odd, Kay's book has a few tips on how to deal with whitespace
that either appears or vanishes unexpectedly. I don't think he covers
everything, so also check http://www.dpawson.co.uk/xsl/sect2/N8321.html,
which in turn points to some related resources.
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
