Subject: RE: [xsl] xsl:sort in old MSXML From: "Claudio Russo" <crusso@xxxxxxxxxxxxxxxxx> Date: Wed, 2 Jul 2003 09:41:22 -0300 |
David, Sorry, but when you mean "to convert", do you mean "to transform"? But if the answer is "to convert", why should I convert to HTML and place the output in my pages? Why not to use the "on-the-fly" processing of XSLT to get the "output=HTML"? Claudio. -----Original Message----- From: David Carlisle [mailto:davidc@xxxxxxxxx] Sent: Martes, 01 de Julio de 2003 05:52 p.m. To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: RE: [xsl] xsl:sort in old MSXML I don't get the Procedural one. In your msg you've said "write XML at home and convert it into HTML". I think from this excerpt that you mean that instructions can be kept and run inside an XML file. I still don't get how. I only associate the process to de XSL language, providing an HTML output. Wendell meant that rather than fight with complexities of cross-browser client side javascript interfaces to XSLT, a simpler and far more popular route is to maintain your XML document and your XSLT file "in house" and then use a command line xslt program (you can use msxsl.exe if you want to stay with MS) to convert your XML files to HTML. You then put these HTML pages on your web server. That way they can be read by any browser without having to worry about XSLT support. David XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] xsl:sort in old MSXML, Jim Fuller | Thread | Re: [xsl] xsl:sort in old MSXML, David Carlisle |
RE: [xsl] Namespaces II, Andrew Welch | Date | RE: [xsl] xsl:sort in old MSXML, Claudio Russo |
Month |