This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Why does using the XSL namespace default namespace preclude literal result elements in the empty namespace?
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] Why does using the XSL namespace default namespace preclude literal result elements in the empty namespace?
- From: Aaron Hope <edh at brioforge dot com>
- Date: Sat, 21 Jul 2001 15:43:37 -0400
- References: <3B593436.2050803@brioforge.com> <200107211705.SAA30261@penguin.nag.co.uk>
- Reply-To: xsl-list at lists dot mulberrytech dot com
David Carlisle wrote:
>I am not at all clear what your question is, if XSL is the default
>namespace so you have <template match=".. then literal result elements
>can be in any prefixed namespace, or if you don't want to prefix them
>use
><html xmlns="">
>...
>
>David
>
The html output method precludes using any namespace on the literal
result elements.
Assuming, that is, that you want them to be interpreted as html. (see
the bottom of my
previous post)
Changing the default namespace works though, and it's what I settled on
yesterday night.
Seems a little shifty, though. A mean trick to play on anyone reading
the thing. Not to
mention the fact that my copy of xalan couldn't handle it and I had to
switch
processors.
Thanks for the input,
aaron
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list