Subject: Re: [xsl] Why does using the XSL namespace default namespace preclude literal result elements in the empty namespace? From: David Carlisle <davidc@xxxxxxxxx> Date: Sun, 22 Jul 2001 21:33:01 +0100 |
> I'm more interested in finding out if there's a good reason for it, and > if not, fixing it in the next version. To be honest it just seems a strange thing to want to do. It may be reasonable to ask for some feature like that but I think it is unreasonable to say that the current state is broken and needs a "fix". If you live in a namespace-aware XML world, then it doesn't really matter what prefix the output gets, so not a lot a point in having any aliasing mechanism to achieve that. If you a producing "legacy" HTML then it is surely more natural never to put the hTML elements into a namespace in the first place, rather than put them in some fake namespace and then ask to alias them back out of that. 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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Why does using the XSL na, Aaron Hope | Thread | [xsl] problem chain templates toget, Xiaocun Xu |
Re: [xsl] how to changing context, Frank Chen | Date | Re: [xsl] how to changing context, David Carlisle |
Month |