Subject: RE: [xsl] xsl:sort in old MSXML From: "Michael Kay" <mhk@xxxxxxxxx> Date: Wed, 2 Jul 2003 17:38:29 +0100 |
> > So, what should I need this Saxon if it all depends on IE6 or > Mozilla to run the XSLT that I typed using a standard txt > editor? Wouldn't be processed by its standard processor (eg: > IE6 --> MSXML3; Mozilla --> I don't know; Nestcape 7 --> I > also don't know). > I'm having trouble working out what it is that's confusing you. Several people have tried to explain this to you, and it's very simple, but somehow the message hasn't got through. You start with a file of XML. You run an XSLT transformation that takes this XML and a stylesheet as input, and produces a file of HTML as output. You send this HTML to a browser. The browser turns the HTML into pixels on your screen. The XSLT engine can be integrated with the browser. In this case you never get to see the HTML, you only see the final pixels. This is called client-side transformation. It generally needs an XSLT engine from the same supplier as the browser (Using Java applets is theoretically possible but not widely practiced). Alternatively you can use an XSLT engine that is quite separate from the browser. In this case they are usually run on different machines. This is called server-side transformation. They do not have to run at the same time (you can do the transformation in advance, at publishing time, and store the HTML on disk). And the XSLT processor doesn't have to come from the same supplier as the browser, because the all that the browser sees is an HTML file, and it doesn't even know that it was produced as the output of an XSLT transformation. Is this any clearer? Michael Kay XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] xsl:sort in old MSXML, David Carlisle | Thread | RE: [xsl] xsl:sort in old MSXML, Wendell Piez |
RE: [xsl] if statement, Michael Kay | Date | [xsl] question regd. xsl translatio, xsl user |
Month |