Thanks for the help. You wrote: "It is available to you if you declare
xpath-default-namespace= in multiple places in your stylesheet, but that
gets awkward."
I think that is what I should be doing to have less impact on existing
code. And at least in my simplified test files I have figured it out.
I have another question now. Here is what I did so far in my test files:
<xsl:template match="EOUProblems">
<xsl:variable name="psetDoc">psettest7.xhtml</xsl:variable>
<xsl:for-each select="document(string($psetDoc))"
xpath-default-namespace="http://www.w3.org/1999/xhtml";>
<xsl:for-each select="//div">
4)<xsl:value-of select="name(.)"/>#
<xsl:copy-of select="."/>
<xsl:apply-templates />
</xsl:for-each>
</xsl:for-each>
</xsl:template>
<xsl:templates match="div"
xpath-default-namespace="http://www.w3.org/1999/xhtml";>
some transform
</xsl:template>
I figured out that I need xpath-default-namespace anywhere I want to use it.
Is there some way that I can use one template for both this default
namespace and the null namespace?
I have lots of code that operates on the base xml file, that I would
like to re-use on the sub file.
Thanks
G. Ken Holman wrote:
If solution (2) were available to you it would look like the following:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
xpath-default-namespace="http://www.w3.org/1999/xhtml";>
...
<xsl:for-each select="div">
4)<xsl:value-of select="name(.)"/>#
.... but it would interfere with your match= of the no-namespace
elements in your XML file, so this approach is not easily available to
you. It is available to you if you declare xpath-default-namespace=
in multiple places in your stylesheet, but that gets awkward.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--