Bug 358289 - Handle both XHTML 1.0 and XHTML 1.1 in wikitext-to-html Ant task
Summary: Handle both XHTML 1.0 and XHTML 1.1 in wikitext-to-html Ant task
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: David Green CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 332122
  Show dependency tree
 
Reported: 2011-09-20 15:04 EDT by Torkild Resheim CLA
Modified: 2011-11-22 14:48 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Torkild Resheim CLA 2011-09-20 15:04:00 EDT
The **xhtmlstrict** attibute for the **wikitext-to-html** Ant task allows you to specify that the output should be XHTML. This declares the doctype to be http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd which is version 1.0. The EPUB specifications recommends that the XHTML is version 1.1, which should be doctype http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd. This would normally not be a problem except that different default values apply and certain tools, such as Adobe's __epubcheck__ thus requires that documents are in XHTML 1.1 (which is why bug #33122 depends on this one). See also http://code.google.com/p/epubcheck/issues/detail?id=1. The actual problem lies in the fact that __ebubcheck__ will invalidate otherwise valid documents due to certain default values being applied – these may not be supported by reading systems only conforming to the specification.
re
There could be an extra option to the Ant task allowing you to declare which version the output conforms to, or we could take take the long way and make sure it confirms to either version. I would go for an extra doctype attribute in the Ant task. While it may not be correct with regards to the output the task actually produces, it is up to the user to make sure.
Comment 1 David Green CLA 2011-09-20 17:03:29 EDT
It's possible to specify the doctype via the @htmlDoctype@ attribute.   If that's not sufficient, I suggest that you indicate specifically each instance of a problem with the output.  If you're inclined on creating patches, you can see how xhtmlStrict is applied in HtmlDocumentBuilder.
Comment 2 Torkild Resheim CLA 2011-09-21 02:52:49 EDT
Thanks David. I missed that one as I for some reason was using the Galileo version of the documentation. Closing as INVALID.