Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]

Michael(tm) Smith wrote:

>   - Instead of "XSLT-compat" or some other arbitrary string, why
>     not just require (if we do decide we want to allow it
>     there at all) that it just be the empty string? XSLT engines
>     can output an empty value for it, and it seems to me that if
>     we have it all, we would want the value to be empty, not some
>     standard value that would become a de facto public ID and that
>     apps would lead to the same very real "bogus rationalizations
>     about its purpose" problem that Henri describes.

I think that empty string is also possible solution. And probably better
then "XSLT-compat" or something like that.

>   - I don't know how to get xsltproc to output just
>     <!DOCTYPE html PUBLIC "XSLT-compat"> (or with whatever string
>     for the public ID).
>     If I do xsl:output@doctype-public="XSLT-compat", xsltproc
>     gives me:
>       <!DOCTYPE html PUBLIC "XSLT-compat" "">
>     That is, with an empty string for the system ID. If I instead
>     do xsl:output@doctype-system="XSLT-compat", I get:
>       <!DOCTYPE html SYSTEM "">
>     So unless there's something I'm missing about how to get

Have you specified HTML output method using xsl:output/@method='html'? I
think that it should work for HTML output method also in xsltproc.
This thread is about HTML5 serialization and using XSLT HTML output for
it. For XHTML (or XML serialization of HTML5) there is no such problem
as <!DOCTYPE HTML> is not required.

  Jirka Kosek      e-mail:
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member

Received on Friday, 29 August 2008 09:19:37 UTC