Subject:Inability to create namespace definition in mapper Author:(Deleted User) Date:12 Jul 2001 11:18 AM
I have found that it is not possible to copy literal text and namespace definitions from a source document to a destination document. I also find it frustrating that if a example destination file has literal entries (such as processing instructions) or name space definitions these do not by default get copied and also I have only been able to set them up by the set literal even if they exist in the example file loaded.
Subject:Re: Inability to create namespace definition in mapper Author:Minollo I. Date:12 Jul 2001 11:37 AM
At 11:24 AM 7/12/2001 -0400, you wrote:
>I have found that it is not possible to copy literal text and namespace
>definitions from a source document to a destination document. I also find
>it frustrating that if a example destination file has literal entries
>(such as processing instructions) or name space definitions these do not
>by default get copied and also I have only been able to set them up by the
>set literal even if they exist in the example file loaded.
I'm not totally sure I understand what you are asking for here.
- About namespace declarations: the XSLT processor is in charge of
automatically copy the namespace declarations from the source document into
the destination document; if I run a testcase in which my source XML has a
xmlns:myNS="..." namespace declaration and I create a Mapper on top of it,
I will get the xmlns:myNS="..." namespace declaration generated in the
result document (actually we have the opposite problem here; not handling
the xsl:stylesheet "exclude-result-prefixes" attribute yet, you can't avoid
having the namespace declarations copied)
- About PI's or comments: you are right, you don't have the possibility
to copy them automatically into the destination document; I'm adding this
to our PCR list; what other kind of "literals" do you have in mind here?