[slowsmile]

@ DiapDealer...I'm afraid that I strongly object to allowing page-map checks in my plugin because it sets a bad precedent. To me there's no grey area. You either follow one standard like the IDPF standard or you don't.

Here's an example of problems that would arise if you don't follow one standard. Say a Sigil user requests an automatic page-map build feature for Sigil and the developers respond that their request does not follow the IDPF standard and his feature request is refused. And then the user responds by saying that there is a already a Sigil plugin that supports and processes page-maps. How are you going to respond to that user? If the above precedent already exists and allows a Sigil plugin to process page-maps then what possible justification can the Sigil developers have for refusing the user's new page-map build feature request?

From the above, here's another interesting question for you: Should all Sigil plugins follow the same epub standard as the Sigil app?(I would really like an answer to this question)