Re: output method html doesnt work with namespace in s

I dont agree completely that xsl:output method="html" is quite un-necessary.
There are lots of applications today in use that are based on the ability to
produce html for end users. Whenever the end user is a consumer or a
customer, you will need some way to output fancy stuff. I use it all the
time for generating output.
How each parser transforms the content also has an impact on the output
quality. There is tremendous amount of diversity on how XML is being used.

Ritu Kama
Sarvega Inc
745, McLintock Dr
Burr Ridge
IL - 60527
----- Original Message -----
From: "bryan" <bry@xxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, December 17, 2002 11:08 AM
Subject: RE:  output method html doesnt work with namespace in source
tree


>
> >From that I would say Xalan conforms, Saxon doesnt and MSXML is
> >confused... ;-)
>
> here's a question for I guess everyone, how many people actually find a
> use for xsl:output method="html"?
>
> I think I've used in once or twice, but I'm not sure in that the
> occasions, if any, where I have used it have not been so pressing that I
> could not just output xml.
>
> Are there some particular browsers, html implementations, out there that
> will choke on <br/> for example? I can't say I've come across them so
> they must be relatively rare.
>
> For me it always seemed that the ability to output html was one of the
> things that were originally assumed to be very likely of high import
> that later turned out to have very little import whatsoever.
>
> What is your usage, percentage wise of xsl:output method="html" and why?
>
>
>
>
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


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