- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 03 Sep 2008 13:11:06 +0200
- To: Thomas Broyer <t.broyer@gmail.com>
- CC: "public-html@w3.org" <public-html@w3.org>
Thomas Broyer wrote: > Some things I haven't read (though I might have just missed them): > * xsl:output has a version attribute, which could very well take the value "5" > * xsl:output method attribute allows QName, so there might be a > special QName meaning "html5" > * none of these require a change to XSLT All of that is true. There's an extension point there, but that doesn't help a lot unless implementations do it. > Also, XSLT cannot generate DOCTYPE internal subsets or entity > references, and people have accomodated; using the xsl:text trick if > they really needed those things, so why couldn't they also accomodate > using the xsl:text trick to output the HTML5 doctype? You need disable-output-escaping, which is optional. > I'd be in favour of having nothing special in the HTML5 spec apart > from a recommandation about using version="5" or a QName for use > within xsl:output/@method. I don't think anybody is against having that as long-term solution, but how does this help with the *current* problem? BR, Julian
Received on Wednesday, 3 September 2008 11:18:28 UTC