This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Refinement: creating namespaces in a generated script
- From: David Carlisle <davidc at nag dot co dot uk>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Wed, 18 Sep 2002 11:50:45 +0100
- Subject: Re: Refinement: [xsl] creating namespaces in a generated script
- References: <084C456607D37B48A975772691A9C34A01E415@bonn28.bonn.fiscus.de>
- Reply-to: xsl-list at lists dot mulberrytech dot com
] staroffice/content.xml (which does not include namespace declarations for
] ns1, ns2, ns):
]
] <text:p text:style-name="Standard">
] <text:variable-set text:name="__Adressen_jeweilsInZeile"
] text:value-type="string">
] /ns1:elem1/ns1:elem2/ns2:elem3/ns2:elem3</text:variable-set>
] </text:p>
If the file does not have namespace declarations then it does not
conform to the namespace spec and it can not be used as input to XSLT at
all. XSLT only works on Namespace conforming documents.
If you can not edit the file you can make a wrapper file that looks
like
<!DOCUMENT foo [
<!ENTITY content SYSTEM "content.xml">
]>
<foo
xmlns:ns1="http//foo.bar.ns1"
xmlns:ns2="http//foo.bar.ns2"
>
&content;
</foo>
Then use this file as input to your XSLT transform.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list