[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
cavecatem@xxxxxxxxxxxxx wrote:
Well XPath 2.0 has an if..then..else expression so instead of using the xsl:if construct you could put the check into the select e.g.
<xsl:value-of
select="if (rdf:Description/(tiff:XResolution | @tiff:XResolution)) then ... else ()"/>
Of course that does the same check but it is a bit shorter.
--
Re: [xsl] avoiding NaN-result in string processing due to missing elements
Subject: Re: [xsl] avoiding NaN-result in string processing due to missing elements From: Martin Honnen <Martin.Honnen@xxxxxx> Date: Mon, 01 Dec 2008 17:50:05 +0100 |
cavecatem@xxxxxxxxxxxxx wrote:
A possible solution is to query for the element/attribute first
<xsl:if test="rdf:Description/(tiff:XResolution | @tiff:XResolution)">
<xsl:value-of select ...
</xsl:if>
Is there another way to do this?
Well XPath 2.0 has an if..then..else expression so instead of using the xsl:if construct you could put the check into the select e.g.
<xsl:value-of
select="if (rdf:Description/(tiff:XResolution | @tiff:XResolution)) then ... else ()"/>
Of course that does the same check but it is a bit shorter.
--
Martin Honnen http://JavaScript.FAQTs.com/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] avoiding NaN-result in string, cavecatem@xxxxxxxxxx | Thread | RE: [xsl] avoiding NaN-result in st, Michael Kay |
[xsl] avoiding NaN-result in string, cavecatem@xxxxxxxxxx | Date | RE: [xsl] avoiding NaN-result in st, Michael Kay |
Month |
Keywords