Re: superfluous namespace declarations with xsl:elemen

Michael Kay wrote:
>>How can I avoid, that with <xsl:element name="{name()}"> and
>>a namespace-prefix in this name, I get a namespace
>>declaration in my output on mostly all elements created this
>>way? Is there some strategy, to get the namespace declaration
>>only once in my root element?
>>
>>Transformers work quite differently on this point (eg. msxslt
>>apparently avoids itself superfluous declarations), so I'm
>>wondering if there is a general approach at all.
>
>
> Most XSLT processors will avoid outputting redundant namespace
> declarations, but there is no way of forcing them to do so.
>
> What processor are you using and what output are you getting?

Because of speed reasons, I often use xsltproc to test my stylesheets
during development process. But little by little, I get the
impression, that xsltproc is not such a good choice for this task. To
many differences from standard behavior occurred in the last time.

I have to manipulate the text content of these nodes (for the ones,
that have "[]" around themselves, I use a separate lookup table,
replacing the actual [value] by the one I found).

...
<arc:ReferenceSet>
 <arc:Reference linkId="[parentdokid]" refType="parent-pointer"/>
</arc:ReferenceSet>
...
<arc:KeywordSet>
 <arc:Keyword>[selektormax]</arc:Keyword>
...

Regards,
Georges

> There is an important difference: xsl:copy puts the new element in the
> same namespace as the original, whereas <xsl:element name="{name()}">
> looks for a namespace declaration in the stylesheet that has the same
> namespace prefix as the original name in the source document.
>
> Michael Kay
> Software AG
> home: Michael.H.Kay@xxxxxxxxxxxx
> work: Michael.Kay@xxxxxxxxxxxxxx