Subject: RE: [xsl] Problem on: Cascading xslts on browsers From: "Michael Kay" <michael.h.kay@xxxxxxxxxxxx> Date: Tue, 10 Dec 2002 09:36:00 -0000 |
> I'm playing with xml/xsls and browsers, and have an > xml, for example, data.xml, and two xsl, for example, > stage1.xsl and stage2.xsl. the idea is that, a processor, > reads data.xml it says that should be processed with > stage1.xsl, and the output (explicited from the output of > xsl, to be an xml) says that should be processed with > stage2.xsl (explicitly again). > data.xml -> stage1.xsl -> stage2.xsl > > So, until there everything is ok on command line processors > like xalan (from apache f.) BUT i couldn't get browsers to > look for the stage2.xsl. > Take a look at the API documentation for your XSLT processor and learn how to control it from script in the HTML page. You can't do everything from the <?xml-stylesheet?> processing instruction. Michael Kay Software AG home: Michael.H.Kay@xxxxxxxxxxxx work: Michael.Kay@xxxxxxxxxxxxxx XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Problem on: Cascading xslts o, alejandro david weil | Thread | RE: [xsl] Problem on: Cascading xsl, Mike Kozlowski |
RE: [xsl] Identifying output from t, Michael Kay | Date | RE: [xsl] Memory housekeeping in Sa, Michael Kay |
Month |