[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xsl] Xalan producing error - (Location of error unknown)org.xml.sax.SAXException: Can not resolve namespace prefix: #all
Subject: Re: [xsl] Xalan producing error - (Location of error unknown)org.xml.sax.SAXException: Can not resolve namespace prefix: #all From: a kusa <akusa8@xxxxxxxxx> Date: Tue, 7 Jan 2014 13:43:10 -0600 |
So is there any way to exclude result prefixes in XSLT 1.0? The documentation does discuss exclude result prefixes attribute for XSLT 1.0 On Tue, Jan 7, 2014 at 1:38 PM, Graydon <graydon@xxxxxxxxx> wrote: > On Tue, Jan 07, 2014 at 11:29:01AM -0800, Martin Holmes scripsit: >> On 14-01-07 11:26 AM, Graydon wrote: >> >Especially since #all is a keyword for _modes_, not prefixes; if you've >> >got something in your code where a namespace prefix starts with an >> >octothorpe (#) that's not going to work anywhere, prefixes can have the >> >characters of the Name production except for >> >> Surely #all is an allowed value for exclude-result-prefixes? It's in >> the example code here: >> >> <http://www.w3.org/TR/xslt20/#lre-namespaces> > > Whups! > > And so is #default. > > Though both are still strictly XSLT 2.0 and thus incomprehensible to > Xalan. Which probably explains why Xalan is looking for a #all prefix, > under the circumstances. > > -- Graydon
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Xalan producing error - (, Graydon | Thread | Re: [xsl] Xalan producing error - (, Graydon |
Re: [xsl] Xalan producing error - (, Graydon | Date | Re: [xsl] Xalan producing error - (, Graydon |
Month |
Keywords