Section 30.7 Page Breaks
A publisher can insert page breaks beyond those that LaTeX creates automatically. This might relieve some awkwardness that LaTeX’s otherwise excellent page breaking failed to relieve. The publisher should identify each source element for which they would like a page break to happen before that element appears in output. For each such element, there must be an
@xml:id. Bring these @xml:id values together in the publication file, using whitespace to separate them. For example:<latex> <insertions pagebreaks="xmlid1 xmlid2 ..."> </latex>
You may use multiple
<insertions> elements to help organize page breaks by chapter, section, etc. For example:<latex> <!-- chapter 1 page breaks --> <insertions pagebreaks="xmlid1 xmlid2"> <!-- chapter 2 page breaks --> <insertions pagebreaks="xmlid3 xmlid4"> </latex>
At time of writing, the allowable elements which may be preceded by a page break using this feature are divisions, numbered blocks, and the following unnumbered elements:
<answer>, <aside>, <audio>, <biographical>, <assemblage>, <blokquote>, <console> (when not a child of a <sidebyside>), <hint>, <historical>, <image> (when not a child of a <sidebyside>), <interactive>, <list-of>, <p>, <paragraphs>, <poem>, <pre>, <program> (when not a child of a <sidebyside>), <sage>, <sbsgroup>, <sidebyside> (when not a child of a <sidebyside>), <solution>, <tabular> (when not a child of a <sidebyside>), and <video>.Note that over time, the precise size of many things in your PDF output may change. This may be because of an underlying change in how PreTeXt builds PDFs. It may be because of change in the LaTeX distribution. And of course, it may be because the source content and publisher specifications (like font) change. So all manually specified page breaks may need to be monitored over the life of a project.
See Subsection 44.3.13.
