RE: <xsl:stylesheet xmlns...

Always transforme it in the server man. There are still Netscape users
out there!

You can do it in ASPs (and fight with a couple of performance issues)and
you can do it in ISAPI extensions (I use Borland Delphi for this), but you
might first try the fast and easy "XSL ISAPI Filter 2.0", if it fits your
needs. Download it from:

http://msdn.microsoft.com/downloads/default.asp?URL=/code/sample.asp?url=/ms
dn-files/027/000/552/msdncompositedoc.xml


Have fun,
Paulo Gaspar

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxx]On Behalf Of Eric Taylor
> Sent: Friday, August 04, 2000 09:35
> To: 'XSL-List@xxxxxxxxxxxxxxxx'
> Subject: RE: <xsl:stylesheet xmlns...
>
>
> What I've concluded from the feedback I've gotten is that I must download
> the new MXSML3 to be able to use the namespace
> ".../1999/XSL/Transform" with
> IE5, and that if one doesn't have the new MXSML3, one must use the old
> ".../TR/WD-xsl" (thereby losing some functionality) or things
> won't display
> correctly.  It isn't a problem for me to install the new MXSML3, I can't
> expect that most customers who will be using our site will have
> done so.  If
> I get the latest instlled on our server, is there any way to have the
> transformations done on our server so that it won't matter what
> clients have
> on their systems?  Or am I stuck with the old version until
> Microsoft makes
> the standard release of IE conform.  Thanks.  Eric
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list