I want to take the attribute value passed into it and store it in a static variable for use with the over xsl extension instructions I have defined.   I wanted to avoid passing these attributes (of which there could be many) to the over xsl extension functions because then I would need to pass them to every call I make to these functions in the stylesheet.  It is much cleaner and nicer to have them as independent variables "floating" at the top of the stylesheet.


On 10/18/07, Michael Kay <mike@saxonica.com> wrote:
No, there's no way to influence the way such elements are handled (other that in a filter applied to the stylesheet on its way into the system, of course). You don't really explain what you want to do with such elements, you only say that you don't want them to be ignored. Could you explain what you would like to achieve?
Michael Kay

From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of Netta Doron
Sent: 18 October 2007 17:34
To: saxon-help@lists.sourceforge.net
Subject: [saxon] XSLT extension non-instruction

Is there a way to write an XSLT extension non-instruction i.e. an element that will not be ignored outside a template block?


<xsl:stylesheet version="2.0"
xmlns:xsl=" http://www.w3.org/1999/XSL/Transform"
extension-element-prefixes="saxon lh">

<lh:namespaces-to-pass-through ns="http:\\www.LightHtmlExtractors.com/wc/ns1"/>

<xsl:template match="/">
    <xsl:apply-templates select="node()"/>

<xsl:template match="extract">
<lh:to-lhtml select="markup"/>


I would like for "<lh:namespaces-to-pass-through ns="http:\\www.LightHtmlExtractors.com/wc/ns1"/>" not to be skipped as an element.


This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
saxon-help mailing list