[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
I didn't follow the whole thread but...
It seems to be a common misunderstanding that <node></node> is different from <node /> in XML. However, when it does matter, for instance to satisfy non-conforming legacy application, workarounds are, in XSLT 1.0, to use a comment node (or, sometimes possible, whitespace like you did) and in XSLT 2.0 to use a character-map (put a private use character inside the node and let it map to an empty string).
Tom Schmitter wrote:
Re: [xsl] parameter getting lost in tunnel?
Subject: Re: [xsl] parameter getting lost in tunnel? From: Abel Braaksma <abel.online@xxxxxxxxx> Date: Tue, 22 Jul 2008 21:57:36 +0200 |
I didn't follow the whole thread but...
It seems to be a common misunderstanding that <node></node> is different from <node /> in XML. However, when it does matter, for instance to satisfy non-conforming legacy application, workarounds are, in XSLT 1.0, to use a comment node (or, sometimes possible, whitespace like you did) and in XSLT 2.0 to use a character-map (put a private use character inside the node and let it map to an empty string).
Cheers, -- Abel --
Tom Schmitter wrote:
I now see that xsl:element does not write both the open and close tags unless it has a text node. (and also that my copy-and-add-level-attribute routine is much more screwed-up than I first realized...on to that next...)
Sorry for unnecessary intrusions.
--Tom
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] parameter getting lost in tun, Tom Schmitter | Thread | [xsl] parameter lost in tunnel?, tom s |
[xsl] parameter getting lost in tun, Tom Schmitter | Date | Re: [xsl] Fetch xml from URL in XSL, sudheshna iyer |
Month |
Keywords