You are viewing a plain text version of this content. The canonical link for it is here.

Posted to fop-dev@xmlgraphics.apache.org by bu...@apache.org on 2006/08/11 10:08:38 UTC

DO NOT REPLY [Bug 40230] New: - Invalid extra page break creates an undesired empty page

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40230>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40230

           Summary: Invalid extra page break creates an undesired empty page
           Product: Fop
           Version: 1.0dev
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: page-master/layout
        AssignedTo: fop-dev@xmlgraphics.apache.org
        ReportedBy: vincent.hennebert@enseeiht.fr


When there is an <fo:block break-after="page"/> and nothing after it in the
flow, a new page is still created, whereas section 7.19.1 of the recommendation
states that it should be the case only if there is material to typeset
afterwards. See the attached fo sample.
The result is the same if we replace break-after by break-before.
Same result also if we remove the indenting such that all the closing tags after
the block are sticked together, so this is not a whitespace handling issue.

I guess that a Knuth penalty of value -infinity is generated for such a block,
and this doesn't play well with the (infinite glue, -infinite penalty) pair
which is probably added at the end of the page sequence. The penalty should
probably be only generated if there is also some box after it, and before the
ending pair.

If nobody takes this bug I'll have a look at it after the GSoC.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

DO NOT REPLY [Bug 40230] - Invalid extra page break creates an undesired empty page

Posted by bu...@apache.org.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40230>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40230

------- Additional Comments From a_l.delmelle@pandora.be 2006-08-11 17:36 -------
(Here I go again :))
I think this could be handled before layout even kicks off...

FOTreeBuilder could keep track of whether the currentFObj has area-generating content --shouldn't
prove too hard to come up with a set of conditions that have to be satisfied.
I'm thinking much in the same direction as the 'inMarker' instance member I recently added to
FOEventHandler: a switch that is updated in the start- or endElement() event for each FObj. If it does
not have any content, and the currentPropertyList contains a break-before/break-after property,
instruct the current or the previous FO to discard that property (maybe log a warning, because it's not
incorrect to specify it)
Maybe we'd have to add a reference to the previousFObj/previousPropertyList to FOTreeBuilder as well,
but that would be a small price to pay, and may open up perspectives in other areas.

Sorry if I keep nagging about these 'normalizations' in the FOTree... :/

I guess my underlying goal is: whatever layoutengine/renderer combination processes our FOTree, we
should try to offer it a representation of the tree that would be difficult to 'misrender'.

--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

DO NOT REPLY [Bug 40230] - Invalid extra page break creates an undesired empty page

Posted by bu...@apache.org.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40230>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40230


jeremias@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From jeremias@apache.org  2007-11-27 00:52 -------
Should be fixed by:
http://svn.apache.org/viewvc?rev=598558&view=rev


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

DO NOT REPLY [Bug 40230] - Invalid extra page break creates an undesired empty page

Posted by bu...@apache.org.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40230>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40230





------- Additional Comments From vincent.hennebert@enseeiht.fr  2006-08-11 08:10 -------
Created an attachment (id=18697)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18697&action=view)
Sample file demonstrating the problem


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.