my appologies about not including any of my code, it's been one of those days! And yes, I am using <xsl:element name="{local-name()}">, which is towards the bottom of the page. The code is as follows:

<?xml version="1.0" encoding="ISO-8859-1"?>
    <xsl:stylesheet version="1.0"
        xmlns:xsl="http://www.w3.org/1999/XSL/Transform "
        <xsl:template match="/">
              <table width="261" border="0" cellspacing="0" cellpadding="0">
                    <td><xsl:apply-templates select="//login_fields"/></td>

<xsl:template match="login_fields">

<xsl:template match="*">
      <xsl:element name="{local-name()}">
            <xsl:apply-templates select="@*|xmlns|node()"/>

<xsl:template match="@*|text()">

I Hope this helps narrow down my problem. Many thanks.



On 20/07/06, Michael Kay <mike@saxonica.com> wrote:
This looks like a pure XSLT problem rather than something specific to Saxon, so the right forum is the xsl-list at www.mulberrytech.com.

To copy elements unchanged, use <xsl:copy-of select="...."/>.

It's worth trying to understand why the elements have been changed. Firstly, is it just the namespace prefix that has changed, or is it the namespace URI as well? Prefixes don't matter, URIs do. Secondly, you haven't shown the code that generated the new element: if you did something like

<xsl:element name="{local-name()}">

then this would account for the effect you are seeing.

(In fact, you haven't shown any of your XSLT code. How do you expect people to show you where you've gone wrong if you don't show your code?)

Michael Kay

> -----Original Message-----
> From: saxon-help-bounces@lists.sourceforge.net
> [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of Andrew
> Sent: 20 July 2006 18:45
> To: saxon-help@lists.sourceforge.net
> Subject: [saxon] Transform problem!!
> Hi,
> I am using saxon 8 within Cocoon 2.1.9. I have a sitemap in
> cocoon like so:
> <map:generate type="newjx" src="jx/{2}.xml"/>
> <map:transform type="xslt-saxon" src="style/{2}.xsl"/>
>                      <map:transform
> src="template-style/forms-samples-styling.xsl "/>
> Don't worry, you don't need to understand cocoon to follow
> this. This is a straight forward, God willing!, transformation issue
> What is happening is that when my xml page hits style/{2}.xsl
> and is transformed, all the fi: parts of the tags are
> stripped out!!! So we go from:
> <fi:form-template action="login.kont" ajax="true"
> name="Form1" method="POST">
> <fi:continuation-id>3e1d50522826841983526b05063d32576c1f1e5e</
> fi:continuation-id>
> −
>     <fi:group>
> <fi:styling type="tabs"/>
> −
>     <fi:state>
> −
>     <fi:field id="activetab" state="active" required="false"> .....
> to:
> <form-template action="login.kont" ajax="true" name="Form1"
> method="POST">
> <continuation-id>3e1d50522826841983526b05063d32576c1f1e5e</con
> tinuation-id>
> −
>     <group>
> <styling type="tabs"/>
> −
>     <state>
> −
>     <field id="activetab" state="active" required="false">
> ......
> after the transformation. This I do not want to happen.
> So,  how do I stop all fi: parts of the tags from being
> stripped out? In my stylesheet I am using the following
> command to read in the element 'form' from the xml document:
> <xsl:apply-templates select="//form"/>
> What I want is a command which brings in the contents but but
> does not process it, so that the contents are left as is!!!
> Is there such a thing in xsl?:
> <xsl:apply-templates select-but-do-not-process="//form"/>
> The reason I want this to happen is because the final xsl
> sheet, forms-samples-styling.xsl, expects to see those tags
> intact for it to process them.
> regards
> Andrew

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
saxon-help mailing list