Re: XSLT 15th Nov: xhtml output method

> My own inclination is to use the <xsl:output version="2"> attribute to
> handle such differences. But I will add an issue (#157) so it comes up on
> the WG agenda. 

I'd agree that a version attribute would be more versatile if there was
anything much that could be done for later xhtml variants but I suspect
that is not the case.  If you have an xhtml2 document using nested
<section elements, xforms, linking using hlink (or xlink) etc, then some
serialisation tricks like putting a space before "/>" aren't really going
to make the thing render in netscape 4. 

xhtml 1 (.0) is explictly designed to be able to work in legacy browsers
by using the lax error checking of html parsers, and it's useful to have
an xslt output type that uses the compatability guidelines to generate
xhtml1 in that style.

Conversely xhtml2 is (as I understand it) trying to have as little as
possible magic html rules and so the xml output method should really
be enough (although adding th eencoding info to the head would perhaps
still be useful)

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

Received on Wednesday, 20 November 2002 09:24:26 UTC