Various Locations (PDF Only): Pagination

[ERyan71258]

The following pagination adjustments should be made:

• Clause 3: Move heading from page 4 to page 5.
• Clause 4: Move Optimal Asymmetric Encryption Pattern term from page 5 to page 6, so that it is not separated from its abbreviation and definition.
• 5.2: Move heading from page 8 to page 9.
• 6.3: Move heading from pave 9 to page 10.
• 6.3.6.1: Move heading from page 10 to page 11.
• 6.3.9: Move heading from page 11 to page 12.
• 6.3.10.3: Move heading from page 13 to page 14. Will also eliminate split table.
• 7.3: Move heading from page 15 to page 16.

[SteveLLamb]

Going to move this over to HTML-pub, but I am seeing the various rules. Please correct where needed @ERyan71258:

• Headers should not be floating on a page; at minimum, you need a single line of prose.
• Terms and Definitions items should not break across pages (item, abbr, def, citation).

Past that, all the mention of moving headers above also involves moving prose as well. Is there a min line count you would prefer?

Also, this ties into https://github.com/SMPTE/html-pub/issues/107

[ERyan71258]

While it is nice to fill more than half a page, sometimes it just doesn't happen. I would rather see headers connected to their text, and logical breaks in text (for example, tables self-contained on one page where possible; introductions to formulae, tables or figures directly above said formulae, tables or figures), than a mandate to fill up a page.

Additionally, in an ideal world, when presenting a complex, multi-column table or complex figure, I would like the ability to click to open a larger version. In the Word world, I use landscape-oriented pages to provide more room for tables or to enlarge images.

[SteveLLamb]

Can we start with the following 2 rules, which will disallow page breaks in these cases:

• Headers should not be floating on a page; at minimum, you need a single line of prose. This is noted here https://github.com/SMPTE/html-pub/issues/234
• Terms and Definitions items should not break across pages (item, abbr, def, citation).

Then if we add in controls for allowing editor defined page breaks, we can get the control you want manually, as I don't see a great way to automate that. This would be 2 seperate things at that point.

[ERyan71258]

Yes, I am good with that.

Another item to add, would be the ability to set a paragraph as "Keep with Next" when generated to a PDF. I have kept sets of paragraphs together using KWN.

I designed the following into the Word template:

• Created separate Figure Caption and Table Caption paragraph formats.
• Created a center-justified Figure Anchor paragraph format to be used to insert a figure. It is set to KWN so that it does not separate from the Figure Caption.
• Table Caption format set to KWN so that it does not separate from the table.

I would also like to see better table handling in the PDF generation. Headers do not repeat across pages. Table and column widths change across tables. Occasionally table rows are simply cut off. Table rows should not, except in rare occasions (e.g., if a cell contains man lines of code), split across pages.

[SteveLLamb]

Great. Marking this as a duplicate for tracking (since I referenced it in other documents), and these have been broken out in 2 seperate issues:

• https://github.com/SMPTE/html-pub/issues/234
• https://github.com/SMPTE/html-pub/issues/107