This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: ***********Transformation of an XML document containing a default namespace ************
David Carlisle writes:
>
> > There doesn't appear to be a way to control what
> > prefixes are used in the output.
>
> Not so. You can control exactly which namespace nodes appear in the
> output. As far as can be seen all processors will use the prefixes
> specified in those namespace nodes (rather than inventing new prefixes
> and then adding additional namespace declarations for those prefixes)
> so, in practice, you have exact control over the namespace prefixes used.
>
> I've been using this quite a lot recently for IE client side transforms.
> IE doesn't believe in XHTML so firstly you have to make sure all the
> html elements get stuffed out without prefix, then if you want to use
> the microsoft "behavio(u)rs" extensions you have to use a MS-specific PI
> in the output binding the behaviour activex component to a _prefix_
> so you have to ensure that the xml elements are output using the prefix
> youve specified. Been playing with xhtml+mathml, in case you hadn't
> already guessed...
I'm using Saxon. It sounds like you're using some extension to MSXML.
I can see how, using standard XSLT, I can add additional namespace
nodes to the output tree, but I don't see how I can prevent namespace
nodes from the stylesheet or the input doocument from being added to
the output. So I still doon't see a way to coontrol what namespace
prefix is used for a given namespace in the output document.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list