publican epub's output includes HTML files using "XHTML 1.0 Strict" as DOCTYPE when the recommendation for epub is apparently "XHTML 1.1".
This is diagnosed by epubcheck 3.0-RC1:
WARNING: /home/rhertzog/x/tdah/publish/en-US/Debian/6.0/epub/debian-handbook/Debian-6.0-debian-handbook-en-US.epub/OEBPS/debian-packaging.html: Irregular DOCTYPE: found '-//W3C//DTD XHTML 1.0 Strict//EN', expecting '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"
This error has been reproduced with the Debian Handbook:
$ git clone git://anonscm.debian.org/debian-handbook/debian-handbook.git
$ grep DOCTYPE build/en-US/epub/OEBPS/index.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
33e04d3..4dffa35 HEAD -> devel
HSS-QE has reviewed and declined this request. QE for this bug will be handled by IED.
Attempted to verify but steps to check problem are missing so unsure if this is correct procedure:
1. Check out a publican book from SVN.
2. Run "publican build --langs en-US --formats epub"
3. cd tmp/en-US/epub/OEBPS
4. Opened a random html file with gedit
5. Searched for "XHTML", found the following:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
Looks like this is still XHTML 1.0 Strict. Setting bug back to ASSIGNED.
Sorry, looks like my publican has inexplicably reverted to the non-dev version over the weekend. Setting up dev version again to re-test this bug.
Fixed issue caused by yum update. Tested with publican-3.1.5-0.fc19.t62.noarch
Followed steps from comment#3
Found the following information:
!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"><html xmlns="http://www.w3.org/1999/xhtml">
Looks like XHTML version is 1.1 rather than 1.0 as expected.
The fix for this bug has been shipped in publican 3.2.0