Hi Bob, Thanks for the information. No need to apologize for the delay; I have a workaround, so time was not an issue.
One follow-up, to make sure I understand the situation. docbook.xsl without the <xsl:output> directive works fine with Saxon. When is that directive needed? Is this an incompatibility between Saxon and other processors or is something else going on? Thanks, Dick ------- XML Press XML for Technical Communicators http://xmlpress.net [email protected] On Nov 3, 2015, at 16:10, Bob Stayton <[email protected]> wrote: > Hi Dick, > Sorry for the slow response. If you look in the xhtml directory, there > is a special master file named docbook-no-doctype.xsl, which is > identical to docbook.xsl except it omits that <xsl:output> directive. > Switching to that solved the problem in some cases. But no one ever did it > for xhtml-1_1 for epub 2 documents. > > Bob Stayton > Sagehill Enterprises > [email protected] > > On 10/21/2015 5:52 PM, Richard Hamilton wrote: >> Hi Bob, >> >> As a followup, it looks like this is a problem that existed in >> 1.78.1. Looking back at my files and email, I see that this was >> discussed in 2013 and was attributed to a quirk in Saxon. >> >> The issue comes up in xhtml-1_1/docbook.xsl which has the following >> line: >> >> <xsl:output method="xml" encoding="UTF-8" indent="no" >> doctype-public="-//W3C//DTD XHTML 1.1//EN" >> doctype-system="http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"/> >> >> Once set, saxon will put that DOCTYPE into everything, even if the >> output has a different namespace. >> >> I resolved this locally by removing the doctype-public and >> doctype-system attributes from this line in docbook.xsl, maketoc.xsl. >> and profile-docbook.xsl. >> >> I forget why this couldn't be changed in the distributed stylesheets >> (maybe a problem with xsltproc or another xslt processor), but if it >> can be changed, that would be helpful. >> >> Thanks, Dick ------- XML Press XML for Technical Communicators >> http://xmlpress.net [email protected] >> >> >> >> On Oct 21, 2015, at 17:15, Richard Hamilton <[email protected]> >> wrote: >> >>> Hi Bob, >>> >>> I built one of our books using the fo stylesheets, and it came out >>> clean. Not an extensive test, but it does build a book with an >>> index, a glossary, and a fair number of customizations. >>> >>> I built an epub using the epub2 stylesheets and got the following >>> message from epubcheck (both epubcheck 3.0.1 and 4.0.0): >>> >>> ERROR: xliff.epub/OEBPS/content.opf: Obsolete or irregular DOCTYPE >>> statement. The DOCTYPE can be removed. WARNING: >>> xliff.epub/OEBPS/toc.ncx: Irregular DOCTYPE: found '-//W3C//DTD >>> XHTML 1.1//EN', expecting '<!DOCTYPE ncx PUBLIC "-//NISO//DTD ncx >>> 2005-1//EN" "http://www.daisy.org/z3986/2005/ncx-2005-1.dtd";>'. >>> >>> I removed all of my customizations, and got the same error with the >>> standard stylesheets, so I'm pretty sure that the problem is not in >>> my customizations. >>> >>> The same book run through the epub3 stylesheets does not generate >>> this error, so it looks like it is specific to epub2. >>> >>> I'll keep using the stylesheets and let you know if I see anything >>> else. >>> >>> Thanks for everything you do to support the stylesheets. >>> >>> Dick ------- XML Press XML for Technical Communicators >>> http://xmlpress.net [email protected] >>> >>> >>> >>> On Oct 21, 2015, at 15:35, Bob Stayton <[email protected]> wrote: >>> >>>> It has been about a week since candidate DocBook XSL 1.79.0 was >>>> released, and it has been downloaded about 150 times. Has anyone >>>> who has tried it run into any problems yet? If so, please let me >>>> know so they can be fixed for the 1.79.1 release. >>>> >>>> -- Bob Stayton Sagehill Enterprises [email protected] >>>> >>>> --------------------------------------------------------------------- >>>> >>>> > To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: >>>> [email protected] >>>> >>> >> >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
