-
Notifications
You must be signed in to change notification settings - Fork 39
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
improved placement of page breaks in the PDF #463
Comments
@[email protected] changed component from |
@[email protected] changed status from |
@[email protected] commented This is waiting for an RPC server upgrade, so we can deprecate Python 2.7 support. This will let us move up to the most recent PDF generation library, which may fix the issue. |
@[email protected] commented Just a note that this issue is still present when running xml2rfc 2.38.1 with software library changes made today (including libcairo). |
@[email protected] changed status from |
@[email protected] changed resolution from `` to |
@[email protected] commented Fixed in bcceafd: Changed the approach to avoiding page breaks inside artwork etc., and added styling to prevent page breaks between |
@[email protected] changed status from |
@[email protected] changed resolution from |
@[email protected] commented Reopening so we revisit after the issue with WeasyPrint is addressed. |
@[email protected] changed status from |
@[email protected] commented Waiting for changes to WeasyPrint |
@[email protected] commented Note: Based on discussion with John Levine, the RFC publication process can proceed despite this issue. |
@[email protected] commented A page breaking oddity in the PDF output -- see page 18/19. There's a single sentence on page 19, which precedes a long . Attempts to force the single sentence onto the previous or next page were unsuccessful (tried keepWithPrevious and keepWithNext). |
@[email protected] commented Another page breaking oddity. We see large chunks of whitespace on pp. 5/6 and 9/10, which come before sourcecode. We usually expect such immediately before sourcecode, but the extra whitespace appears on the two pages before sourcecode. Seems similar to issue in 8851 above. https://www.rfc-editor.org/v3test/rfc8916.pdf |
@[email protected] commented Spotted a page break between a dt and dd (newline="false") in RFC 8949, Section 7.1, page 37: https://www.rfc-editor.org/v3test/rfc8949.pdf |
@[email protected] commented Another example. Odd page break placement between two s (when the second is followed by large ). See pages 54 and 55 in the PDF - the one line of text on page 55 ("A possible description for that scenario could be the following:") should be on page 54. files: Tried addding , but it had an odd effect -- splitting the preceding paragraph: Also tried on the preceding paragraph -- same result: https://www.rfc-editor.org/v3test/test8846.pagebreak2.pdf (A paragraph being unnecessarily split by a page break seems similar to #566, but that one didn't use keepWithPrevious or keepWithNext.) |
@[email protected] changed priority from |
@alicerusso - I think this may be OBE by the recent changes to pagebreak behavior. Is there anything here still relevant? |
Examples of the original issue seem to have gone away. |
The following issues have gone away:
I think this is still an issue: |
I've created #1119 for #463 (comment) because it's a bit different to the other page break issues. Other issues mentioned here seem OBE. |
owner:[email protected]
type_enhancement
| by [email protected]Hoping for automatic prevention of
a) page break between reference tag and reference entry
ex: p. 12-13 of https://www.rfc-editor.org/rfc/rfc8689.pdf
p. 12-13 of https://www.rfc-editor.org/authors/rfc8663.pdf
b) page break after section title
ex: section 4 (p. 13-14) of https://www.rfc-editor.org/authors/rfc8695.pdf
Issue migrated from trac:463 at 2022-02-08 07:04:07 +0000
The text was updated successfully, but these errors were encountered: