While I agree on the concept, the reality is not as correct. Please define "properly design your stylesheet"?
My biggest beef with XSLT processors is they do to much thinking for me and not enough DWIM-ing. I want to be able to select, print, and arrange things [read: elements/attributes], NO have it correct tag out for me [read: adding/subtracting slashes and such]. <br /> going into <xsl:output method="html"/> comes out as "<br>", at least for me in libxslt and sablot, which is certainly not what I want it to do. <xsl:output method="html"/> also completely munges <html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en"> into <html lang="en" lang="en">. Granted, these may be more specific to each xslt processor, but still, Do What I Mean, not what you think I mean. Even more to the point, XHTML fits well in neither method="html" or method="xml" transformations. I'm sure there are ways around it ala encoding or hiding things from the xslt processoer, but come on, that's silly IMHO. > -----Original Message----- > From: Tod Harter [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 08, 2002 9:36 AM > To: Melvyn Sopacua > Cc: [EMAIL PROTECTED]; AxKit List > Subject: Re: MSIE Render; Content-Type Questions > > > Doesn't actually matter. There is no "official" xhtml output > method either. > XSLT 1.1 draft as of the latest one I read didn't include it. > The reasoning > being that if you properly design your stylesheet then the > html method will > work fine and should output legal xhtml. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
