RE: Carrying Namespaces through a XSL to XSL Transform

Sorry,

but what problem is this intended to solve?

(Almost) every time I see disable-output-escaping and xsl:text being used to
generate XML, there's something wrong with the design of the XSLT code...

Julian

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Kevin
> McCarthy
> Sent: Wednesday, December 27, 2000 7:39 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Cc: chadsm@xxxxxxxxx
> Subject: Re:  Carrying Namespaces through a XSL to XSL
> Transformation
>
>
> Chad,
>
> Here is a template that I have used in the past, using MSXML3.
> This successfully outputs multiple namespace references in the resulting
> XSLT.
> I am using parameters in the below example to define on of my
> namespaces and
> schema locations.
>
> Good luck,
> -Kevin
>
>
>
> <!--
>  renderXSLStylesheetStart:
>   renders the opening xsl:stylesheet tag and attrs
> -->
> <xsl:template name="renderXSLStylesheetStart">
> <xsl:text disable-output-escaping="yes">&#60;&#63;xml
> version="1.0"&#63;&#62;</xsl:text>
> <xsl:text disable-output-escaping="yes">
> &#60;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> version="1.0"</xsl:text>
>   xmlns:s="urn:schemas-microsoft-com:xml-data"
>   xmlns:dt="urn:schemas-microsoft-com:datatypes"
>   xmlns:<xsl:value-of select="$ns"
> />="x-schema:http://localhost/schema/<xsl:value-of select="$name"
> />Schema.xml"
>   xmlns:editA="x-schema:http://localhost/schema/EditAttributes.xml" &#62;
> </xsl:text>
> </xsl:template>
>
> -----Original Message-----
> From: Smith, Chad <chadsm@xxxxxxxxx>
> To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx' <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
> Date: Wednesday, December 27, 2000 10:30 AM
> Subject:  Carrying Namespaces through a XSL to XSL Transformation
>
>
> >> Because of the inability to convert XPath strings to XPath
> nodesets, I am
> >> forced to perform XSL to XSL Transformations.  these
> transformations have
> >> worked out well with a single exception: I cannot migrate more than one
> >> namespace to the resulting XSLT file.  This is a problem
> because I would
> >> like for the resulting XSLT to utilize some form of embedded
> script, but
> >> since I am using Xalan, this requires two additional namespaces.
> >>
> >> I am currently using 'xsl:namespace-alias' to carry over the actual XSL
> >> namespace, however multiple uses of this tag with different
> properties do
> >> not migrate additional namespaces but only attempt to overwrite the
> first.
> >>
> >> Any ideas?
> >
> > XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> >
> >
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list