Hide Forgot
In a Publican-generated PDF book, when there is text on the very last line above the page footer, character tails and loops below the baseline are clipped and rendered at the top of the next page. Spotted at page 76 in Red_Hat_Network_Satellite-5.5-Installation_Guide-en-US.pdf and page 130 in Red_Hat_Enterprise_Virtualization-3.0-Evaluation_Guide-en-US.pdf
Please supply links and not just names.
Oh, sorry about that. https://documentation-01.app.eng.bos.redhat.com/site/documentation/en-US/Red_Hat_Network_Satellite/5.5/pdf/Installation_Guide/Red_Hat_Network_Satellite-5.5-Installation_Guide-en-US.pdf - page 76 https://documentation-01.app.eng.bos.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.0/pdf/Evaluation_Guide/Red_Hat_Enterprise_Virtualization-3.0-Evaluation_Guide-en-US.pdf - page 130
HSS-QE has reviewed and declined this request. QE for this bug will be handled by IED.
This is a bug in webkit http://code.google.com/p/wkhtmltopdf/issues/detail?id=33 it will take a considerable amount of time to update wkhtmltopdf to use a newer webkit.
*** Bug 1122975 has been marked as a duplicate of this bug. ***
*** Bug 1192455 has been marked as a duplicate of this bug. ***
Now that wkhtml has migrated to github, does anyone have a current correct issue link? I get the issue when generating the Performance Co-Pilot handbooks. I see the page breaks in the table of context (not sure if it is rendered as a table in html and hence is issue https://github.com/wkhtmltopdf/wkhtmltopdf/issues/2141) Btw. Are there any workarounds for this?
(In reply to Michele Baldessari from comment #9) > Now that wkhtml has migrated to github, does anyone have a current correct > issue link? I took a look and couldn't find it. It looks like upstream has already started the QT5 port. https://github.com/wkhtmltopdf/wkhtmltopdf/blob/0.13/README.md#release-plan > I get the issue when generating the Performance Co-Pilot handbooks. I see the > page breaks in the table of context (not sure if it is rendered as a table > in html and hence is issue > https://github.com/wkhtmltopdf/wkhtmltopdf/issues/2141) The TOC is generated using definition lists. So probably not the exact same thing. > Btw. Are there any workarounds for this? Unfortunately no :(
Please open upstream bugs for PDF issues, there are no resources here to address them. https://github.com/wkhtmltopdf/wkhtmltopdf/issues