From: bryan [mailto:bry(_at_)itnisk(_dot_)com]
Sent: Tuesday, December 17, 2002 10:08 AM
Subject: RE: [xsl] output method html doesnt work with namespace in
source tree
First, to comment on Jeni's statement:
From this and the behaviour that you report, I'd say that Saxon
conforms and both Xalan and MSXML don't.
Which version of Xalan are we talking about? The version of Xalan-J we use
in production has no problem writing <br/> as <br>. Would this have
something to do with not using -HTML when invoking the transformer?
here's a question for I guess everyone, how many people
actually find a
use for xsl:output method="html"?
Er, everyday, since XSLT drives the presentation layer of our Web sites.
HTML output is pretty much a given.
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.
Netscape 4.x has been mentioned; it has a problem with close tags for empty
elements (and a host of other issues, being horribly obsolete, but that's a
discussion for another mailing list). But other browsers, including new
versions of Netscape and IE, will also have trouble with certain elements if
the processor doesn't write out conformant HTML (I've heard of issues with
<textarea> and IE6 for example).
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?
See above. It's all we do with XSLT. What we're doing now is determining
if this is the most efficient way to handle our presentation.
cheers,
b.
| brian martinez
brian(_dot_)martinez(_at_)trip(_dot_)com |
| senior gui programmer 303.708.7248 |
| trip network, inc. fax 303.790.9350 |
| 6436 s. racine cir. englewood, co 80111 |
| http://www.cheaptickets.com/ http://www.trip.com/ |
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list