Re: avoiding NaN-result in string processing due to m

Play the video

Subject: Re: 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
avoiding NaN-result in string processing due to missing elements cavecatem@xxxxxxxxxxxxx - 1 Dec 2008 16:32:46 -0000 Martin Honnen - 1 Dec 2008 16:50:29 -0000 <= Michael Kay - 1 Dec 2008 17:02:38 -0000 Michael Kay - 1 Dec 2008 17:11:36 -0000

<- Previous	Index	Next ->
avoiding NaN-result in string, cavecatem@xxxxxxxxxx	Thread	RE: avoiding NaN-result in st, Michael Kay
avoiding NaN-result in string, cavecatem@xxxxxxxxxx	Date	RE: avoiding NaN-result in st, Michael Kay
	Month

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Subscribe in XML format

RSS 2.0
Atom 0.3


	Stylus Studio® Developer Network \| Contact Us \| Email this page