-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Various Locations (PDF Only): Pagination #253
Comments
Going to move this over to HTML-pub, but I am seeing the various rules. Please correct where needed @ERyan71258:
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 #107 |
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. |
Can we start with the following 2 rules, which will disallow page breaks in these cases:
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. |
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:
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. |
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: |
The following pagination adjustments should be made:
The text was updated successfully, but these errors were encountered: