MobileRead Forums - View Single Post

AlexBell · 04-11-2012, 09:50 PM

This post deals with the standalone version of FlightCrew, and outlines a serious problem that FlightCrew didn't find but ePubCheck did.

In the past I used ePubCheck routinely, but now I use FlightCrew routinely with a final check with ePubCheck.

When finishing an ebook recently I added the XHTML files for several chapters to the ePub package, and edited the toc.ncx file to match. I copied and pasted several nav points which were already there, but though I changed the text headings and the src entries I forgot to change the Navpoint id numbers.

When I checked the ePub package with FlightCrew it passed it with no errors reported. When I checked the same package with ePubCheck it failed the file and indicated that there were duplicate identifiers. After editing the toc.ncx file the ePub was passed both by FlightCrew and ePubCheck.

If I hadn't done the final check with ePubCheck I would have sent off to the publisher a defective ebook in which the TOC of contents didn't work.

I'm afraid I don't know what version of FlightCrew I use, nor how to find out, nor (now that I think of it) whether I have the most up to date version.

04-11-2012, 09:50 PM	#1
AlexBell Wizard Posts: 3,413 Karma: 13369310 Join Date: May 2008 Location: Launceston, Tasmania Device: Sony PRS T3, Kobo Glo, Kindle Touch, iPad, Samsung SB 2 tablet	FlightCrew versus ePubCheck This post deals with the standalone version of FlightCrew, and outlines a serious problem that FlightCrew didn't find but ePubCheck did. In the past I used ePubCheck routinely, but now I use FlightCrew routinely with a final check with ePubCheck. When finishing an ebook recently I added the XHTML files for several chapters to the ePub package, and edited the toc.ncx file to match. I copied and pasted several nav points which were already there, but though I changed the text headings and the src entries I forgot to change the Navpoint id numbers. When I checked the ePub package with FlightCrew it passed it with no errors reported. When I checked the same package with ePubCheck it failed the file and indicated that there were duplicate identifiers. After editing the toc.ncx file the ePub was passed both by FlightCrew and ePubCheck. If I hadn't done the final check with ePubCheck I would have sent off to the publisher a defective ebook in which the TOC of contents didn't work. I'm afraid I don't know what version of FlightCrew I use, nor how to find out, nor (now that I think of it) whether I have the most up to date version.