Pipeline DTBook to EPUB script

I am attempting to create an EPUB using a DTBook which was created with the SaveAsDaisy 2.1.1 Word 2007 add-in. The DTBook is of version 2005-3 ("dtbook xmlns="http://www.daisy.org/z3986/2005/dtbook/" version="2005-3" xml:lang="en-US"" is from the .xml file that contains the DTBook). However, according to the DTBook-to-EPUB script found at http://data.daisy.org/projects/pipeline/doc/scripts/OPSCreator.html: "The OPS Specification is quite picky about what kind of text documents can be used within an EPUB. You can only use XHTML 1.1 (not 1.0) documents, or DTBook 2005-2 (not 2005-1 or 2005-3) documents." Looking at the changelog from version 2005-2 to 2005-3 I find the following changes (http://www.daisy.org/z3986/2005/release_notes_dtbook_2008-01-16.html#dtd2_3): -- Changed pid, sid, version, and filename for 2005-3 throughout, including documentary comments -- (Issue 194) Removed superfluous %dtbookblock entity -- (Issue 191) Updated RFC reference from 3066 to 4646 -- (Issue 148) Updated comments regarding caption/@imgrefs to reflect type of IDREFS, not %URI; -- (Issue 156) Changed attlist for title to %attrs; -- (Issue 157) Added @smilref and @showin to bdo -- (Issue 195) Expanded title content model to include inlines -- (Issue 200) Added pagenum to imggroup content model -- (Issue 199) Added pagenum to table and tbody content models However, I cannot find the descriptions of these issues. The release notes also say that the DTBook-to-EPUB script will *try* to shoehorn a file of an incorrect version into a file of a correct version. So my question is this: is there a better way to do DTBook-to-EPUB creation or should I just cross my fingers?

You're right, the EPUB specification accepts only documents in the DTBook version 2005-2. The Pipeline contains a "DTBook Migrator " script but unfortunately this script supports only forward migration at the moment, you cannot revert to 2005-2 from 2005-3. Anyway, in most of the cases, the 2005-3 DTBook document will be a valid 2005-2 document when you change its version declaration, so "crossing your fingers" should be fine. I personally don't know of any other tool (which doesn't mean they do not exist). If you do face unexpected errors or issues, don't hesitate to come back to us. For the details on the issues, you can look at the Z39.86 Issue Tracking section on the DAISY website: http://www.daisy.org/z3986-issue-tracking Hope this helps, Romain.