@Kevin...Thanks for providing the links. I admit that I don't know much about Adobe page-maps.
I've read the links that you provided and some of the information surprised me. For instance here is an excerpt from your Safari-O'Reilly link:
Quote:
|
"The catch? page-map is (intentionally) an extension to ePub and adding a page-map file to your ePub will make it invalid. On top of that, unless the reading systems is based on Adobe software (like Digital Editions and the Sony Reader), page-map will have no effect."
|
The above emphasized text seems to indicate that if you have Adobe's page-map feature in your epub then it will not pass Epubcheck. So what you are asking me to do is to accomodate and check a proprietary epub feature(page-maps) that invalidates an epub. The page-map feature also only works on ADE and Sony ereaders that obviously use their own proprietary epub standard(not the IDPF epub standard).
Could you please clarify the reasons why I should include checks on page-map links in my plugin. My own view is that I see no point in my plugin supporting Adobe's proprietary page-map feature when that feature invalidates epubs i.e. I would prefer that my plugin properly follows the IDPF standard for epub 2. I should also mention that, in my research on page-maps, Calibre dropped their page-map plugin in 2010 and it was never replaced.
KevinH said:
Quote:
|
And by the way, the sample epub that was just posted by BeckyEbook correctly uses fragments in the opf guide section so parsing the opf guide will be needed as well.
|
As I've already reported to Becky, after I ran the IDErrorCheck and RemoveUnusedBookmarks plugins on her epub, it passed Epubcheck without any problems. Nevertheless, I will also check all the href ids in the opf with this plugin as you've advised, just to make sure.