Uploaded image for project: 'FOP'
  1. FOP
  2. FOP-1223

Invalid extra page break creates an undesired empty page

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Reopened
    • Resolution: Unresolved
    • 2.5
    • None
    • layout/unqualified
    • None
    • Operating System: All
      Platform: All
    • 40230

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            vhennebert Vincent Hennebert

            Dates

              Created:
              Updated:

              Slack

                Issue deployment