epub:type page-list, pagebreak questions

2 posts / 0 new
Last post

We have some questions about use of the epub:type page-list and pagebreak constructs (http://www.idpf.org/epub/vocab/structure/).

When these concepts are expressed in markup, our intent is to display the authored page numbers in the reader UI. Authored page numbers then take precedence over any kind of a calculated virtual page number.

If both page-list and pagebreaks are specified in a book, which markup should be used for page number display? We have some samples in hand that have both, and of course, they conflict. Should we warn the user when we find both constructs in use?

If an ePub uses epub:type=”pagebreak” inconsistently, can we regard that as being worthy of a warning to the author? We see content with out of sequence page numbers, missing page numbers, and some books that use the pagebreak construct in some spine items also include spine items that don’t have any pagebreak markup at all. Using these author-generated page numbers, when there are markup errors or missing markup, is going to be potentially confusing to readers.


The page-list nav and pagebreak semantics are designed to be complementary: the page-list nav provides the ability to quickly/easily move a user to a specific pagebreak location.

It's hard to say whether pagebreak numbering should be consistent or not. What if the publication only contains a subset of the entire work? It could very well have gaps which appear to be "missing" numbers.

I don't know that you'd want to rely on these numbers alone for presentation to the reader. It might be better to use them as a complement to auto-generated numbering.

One of the primary reasons for including page breaks is accessibility; for example, so that non-visual readers can quickly access the corresponding print page location as their sighted peers (e.g., for classroom use).

Secondary menu