[publican-list] [Bug 489249] New: <programlisting> in <example> doesn't break over pages in PDF
bugzilla at redhat.com
bugzilla at redhat.com
Mon Mar 9 05:33:16 UTC 2009
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: <programlisting> in <example> doesn't break over pages in PDF
https://bugzilla.redhat.com/show_bug.cgi?id=489249
Summary: <programlisting> in <example> doesn't break over pages
in PDF
Product: Red Hat Enterprise Linux 5
Version: 5.2
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: publican
AssignedTo: jfearn at redhat.com
ReportedBy: dmison at redhat.com
QAContact: ecs-dev-list at redhat.com
CC: publican-list at redhat.com
Classification: Red Hat
Target Release: ---
Description of problem:
The <programlisting>tag doesn't split at page breaks if it is contained in an
<example>, it moves onto the next page (same behaviour as an image) if the
content is less than one page. If the programlisting content is more than one
page it runs off the bottom of the first page and disappears.
Version-Release number of selected component (if applicable):
0.42
How reproducible:
everytime
Steps to Reproduce:
1. add a <example><programlisting>...</programlisting></example> near the
bottom of the page so you would expect it to run onto the next page
2. build the pdf
Actual results:
Whole content is displayed on the 2nd page.
Expected results:
The content is split over the two pages.
Steps to Reproduce:
1. add a <example><programlisting>...</programlisting></example> near the
bottom of the page so you would expect it to run onto the next page and the one
after
2. build the pdf
Actual results:
The content runs off the bottom of the first page.
Expected results:
The content is split over the multiple pages.
Additional info:
I've only seen this with <programlisting> but suspect it would also do it with
other content.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the publican-list
mailing list