<?user Web admin (admin@something.net) {00000000-0000-0000-0000-000000000000}?>To get this string into an XSLT parameter, I use the following XSLT instruction:<xsl:param name="username" select="/processing-instruction('user')" />A processing instruction can appear anywhere in the XML document. To find processing instructions that are not children of the root element, use the appropriate XPath syntax.
<table>... the first child of the TR element is the whitespace between the TR tag and the first TD tag. As the whitespace is allowed in that position by the HTML standard, you cannot rely on the TR.firstChild property. You should use TR.cells[0] to select the first cell.
<tr id='test'>
<td>Cell #1</td>
<td>Cell #2</td>
</tr>
</table>
Obviously this is too simple, so it's hard to find an explicit answer in the online documentation:
This post is part of You've asked for it series of articles.
The short answer is utf-8. The long answer goes along these lines:
This post is part of You've asked for it series of articles.
You can see how I've used this approach in this post.
When you use xsl:apply-templates in a xsl:template, you might get extra text strings in the transformed results if your input XML data contains unexpected elements with text nodes (due to default XSLT template rules, the extra elements themselves and their attributes are ignored).
There are three ways you can handle this situation:
<?xml version="1.0" ?>... is processed with the stylesheet ...
<data>
<a>A1</a>
<b>B1</b>
<c>Unexpected</c>
<b>B2</b>
<a>A2</a>
</data>
<?xml version="1.0" ?>... you get the string Unexpected in the transformed results. You could either list the children you expect in the xsl:apply-templates, for example ...
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="data">
<xsl:apply-templates /></xsl:template>
<xsl:template match="a">
A: <xsl:value-of select="text()" />
</xsl:template>
<xsl:template match="b">
B: <xsl:value-of select="text()" />
</xsl:template>
</xsl:stylesheet>
<xsl:template match="data">... or you could define a default template that does nothing (overwriting the built-in default that outputs the child text nodes) ...
<xsl:apply-templates select="a|b" /></xsl:template>
<xsl:template match="*" priority="-100" />
This post is part of You've asked for it series of articles.
<?xml version="1.0" ?>... is transformed with this stylesheet ...
<?xml-stylesheet href="t1.xsl" type="text/xsl"?>
<data>
<row>Sample</row>
</data>
<?xml version="1.0" ?>... Firefox displays the resulting text (<b>Sample</b>), but Internet Explorer displays Sample.
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="text" />
<xsl:template match="row">
<b><xsl:value-of select="text()" /></b>
</xsl:template>
</xsl:stylesheet>
<?xml version="1.0" ?>... Saxon would report ambiguous rule match (even documenting the input element that caused the error and the source line number), whereas all the other XSLT translators would silently produce "best effort" results. In fact, the stylesheet had a typo, the last template should match the b element and I would have lots of problems detecting that with MSXML (for example).
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="data">
<xsl:apply-templates /></xsl:template>
<xsl:template match="a">
A: <xsl:value-of select="text()" />
</xsl:template>
<xsl:template match="a">
B: <xsl:value-of select="text()" />
</xsl:template>
</xsl:stylesheet>
<xsl:value-of select='text() /> is used when you want to select the text embedded between the opening and closing tag of the current element. However, in this context, the text() function selects only the first child text node. If you want to:
<?xml version="1.0" ?>... transformed with this stylesheet ...
<?xml-stylesheet href="t1.xsl" type="text/xsl"?>
<data>
<row>Before <b>an embedded tag</b> and after it</row>
</data>
<?xml version="1.0" encoding="windows-1250" ?>... results in the following text:
<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="text" encoding="windows-1250" />
<xsl:template match="row">
Text(): <xsl:value-of select="text()" />
Current element: <xsl:value-of select="." />
Text loop: <xsl:for-each select="text()"><xsl:value-of select="." /></xsl:for-each>
</xsl:template>
</xsl:stylesheet>
Text(): Before
Current element: Before an embedded tag and after it
Text loop: Before and after it
This post is part of You've asked for it series of articles.
Testing for missing attributes in XML elements is different from testing for attributes with empty values. You can test for missing attributes with <xsl:if test="not(@attribute)">, but this test will never succeed if the attribute is present but empty. In that case, you have to use the <xsl:if test="@attribute = ''"> condition.
This post is part of You've asked for it series of articles.
Posts
All Comments
