Quote:
Originally Posted by GeoffC
Confusing when on the one hand we discover Adobe's "ePub best practice" that mentions the use of PageMap, and then a couple of posts including Do not use page mapping on epubcheck stating the OPF specs do not allow PageMap to be used.
Implying that only ADE will allow use of the page map....
So much for a 'standard' ..... |
Adobe had to solve page number issue (and put page numbers on the margin) for business reasons. Our position is that page map is a practical solution to existing problem. It will be supported in the future. Other renderers are free to use it as well. In the future NCX syntax will probably be "blessed" for the same purpose, but currently it is not. Once NCX page map syntax is officially part of the standard, Adobe viewer will support it in parallel to existing page map syntax.
Jon's message that you referred to is Jon's opinion (not IDPF position) and I think he misrepresents many things. I saw a variation of this message in so many places that I am just unable to go to each one and rebuke it.
In a nutshell: yes, it is non-standard extension and it won't validate (being an extension); no, it won't be dropped; no, it won't cause problems in any other viewer; no, there is no standard way of doing it (even though alternative syntax does validate, that usage of NCX is not "blessed" in the spec); no, there is no other viewer that implements NCX syntax for pages at this point.