Bug 489249 - <programlisting> in <example> doesn't break over pages in PDF
Summary: <programlisting> in <example> doesn't break over pages in PDF
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 2.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Content Services Development
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-09 05:33 UTC by Dana Mison
Modified: 2010-11-24 03:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-25 04:37:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Dana Mison 2009-03-09 05:33:15 UTC
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.

Comment 1 Jeff Fearn 🐞 2009-03-25 04:37:46 UTC
This is a limitation of FOP. You will need to pull the programlisting outside the example.


Note You need to log in before you can comment on or make changes to this bug.