Bug 41841 - table overflow on page and in table cells
Summary: table overflow on page and in table cells
Status: CLOSED DUPLICATE of bug 39840
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: pdf (show other bugs)
Version: 0.93
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-14 08:17 UTC by Knut H. Hertel
Modified: 2012-04-01 13:52 UTC (History)
0 users



Attachments
the failing document (299.55 KB, text/plain)
2007-03-14 08:18 UTC, Knut H. Hertel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Knut H. Hertel 2007-03-14 08:17:32 UTC
When rendering the attached document (generated with docbook 1.72 stylesheets) I
get two problems:
1.) the last table overflows the last page and is missing data
2.) in the table some columns overflow (there is no possiblity to break)
I can fix the first problem, when removing a "keep-with.." in one block
manually, but cannot fix the second. Also fixing the block manually is awkward.
When will fop support docbook again (it works with fop 0.20 and older docbook
stylesheets)?
Comment 1 Knut H. Hertel 2007-03-14 08:18:15 UTC
Created attachment 19707 [details]
the failing document
Comment 2 Chris Bowditch 2007-03-14 09:23:50 UTC
FOP does support Docbook. However there are some limitations to the FO that it 
supports. It just appears that your document is generating a quite complex FO.

For issue (2) do you mean you get a series of messages like:

WARNING: Line 1 of a paragraph overflows the available area. (fo:block, 
location: 4213/47)

This simply means FOP is unable to find a break point in your text, e.g. a 
space or hyphenation point in a long word within the table cell. To overcome, 
you can insert SHY or ZWSP characters at convenient points within the long 
word inside the table cells. FOP will then be able to break the long word onto 
the next line.

I'm keeping this issue open because item (1) does look like a nasty bug. 
Thanks for reporting!
Comment 3 Paul Vinkenoog 2007-03-17 05:34:13 UTC
Issue (1) is the same as reported in #39840. If you read the comments and follow
the links there, you get some suggestions for workarounds.
Comment 4 Vincent Hennebert 2007-11-29 11:13:45 UTC
See bug #39840 for the remaining issue.

*** This bug has been marked as a duplicate of 39840 ***
Comment 5 Glenn Adams 2012-04-01 13:52:47 UTC
batch transition to closed remaining pre-FOP1.0 resolved bugs