Skip to content
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

Open
ERyan71258 opened this issue Feb 13, 2024 · 5 comments
Open

Various Locations (PDF Only): Pagination #253

ERyan71258 opened this issue Feb 13, 2024 · 5 comments
Labels
duplicate This issue or pull request already exists

Comments

@ERyan71258
Copy link
Collaborator

ERyan71258 commented Feb 13, 2024

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 SteveLLamb transferred this issue from another repository May 15, 2024
@SteveLLamb SteveLLamb transferred this issue from another repository May 16, 2024
@SteveLLamb
Copy link
Member

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 #107

@ERyan71258
Copy link
Collaborator Author

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
Copy link
Member

SteveLLamb commented May 23, 2024

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 Prevent Page breaks (keep with next) #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
Copy link
Collaborator Author

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 SteveLLamb added the duplicate This issue or pull request already exists label May 23, 2024
@SteveLLamb
Copy link
Member

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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants