Pagination chunks should be configurable
Currently publisher provides two approaches for paginating content:
- browse by actual page boundaries using page break elements contained in the TEI
- browse by single divs: if there's not enough content in one div to be displayed, further divs are added
The algorithm for 2) is currently hardcoded and not easy to change.
- make it easier for users to change the pagination code by refactoring the code and moving the corresponding functions e.g. into config.xqm
- let the user choose from different methods, e.g.
- paginate by divs on level 2 only, so everything below level 2 will appear on one page