[ 
https://issues.apache.org/jira/browse/FOP-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Charlie Halpern-Hamu updated FOP-2609:
--------------------------------------
    Description: 
In the attached examples more.fo and less.fo, page 1 has a content width of 
5.5in, achieved with 1in page margins, and an extra 1in region-bdy margin-left.

In more.fo, the other pages have a content width of 6.5in, as they have a 
region-body margin-left of 0in. In less.fo, the other pages have a content 
width of 4.5in, as they have a region-body margin-left of 2in.

There's space at the bottom of page 1, but not enough for a scale-to-fit 
graphic. So the graphic gets bumped to page 2. The graphic correctly scales its 
width to fit the page 2. And it correctly scales its height in proportion to 
its width.

However, at the bottom of page 2, text either overflows to page 3 too late or 
too soon.

In more.fo, text at the bottom of page 2 overflows onto page 3 too late, 
running over the footer when it should get bumped to page 3. It appears that, 
for the purposes of determining if there is space left on the page, the height 
of the graphic is counted as if it had appeared on page 1, instead of the wider 
page 2.

In less.fo, the text at the bottom of page 2 overflows onto page 3 too soon, 
stopping well above the footer. Again, it appears, that for the purposes of 
determining if there is space left on the page, the height of the graphic is 
counted as if it had appeared on page 1, instead of the narrower page 2.

  was:
In the attached example, page 1 has a content width of 5.5in, achieved with 1in 
page margins, and an extra 1in content-region margin-left. The other pages all 
have a content width of 6.5in, as they don't have have the extra margin-left.

There's space at the bottom of page 1, but not enough for a scale-to-fit 
graphic. So the graphic gets bumped to page 2. The graphic correctly scales its 
width to fit the wider page 2. And it correctly scales its height in proportion 
to its width.

However, at the bottom of page 2, text runs over the footer and even over the 
bottom of the page, when it should get bumped to page 3. It appears that, for 
the purposes of determining if there is space left on the page, the height of 
the graphic is counted as less, as if it had appeared on the narrower page 1.

If the content width for page 2 is adjusted to be LESS than page 1, the text at 
the bottom of page 2 overflows onto page 3 too soon, stopping well above the 
footer. Again, it appears, that for the purposes of determining if there is 
space left on the page, the height of the graphic is counted as if it had 
appeared on page 1 (and thus is wider and taller).


> When scale-to-fit graphic overflows to page with different width, height used 
> for page overflow doesn't change
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: FOP-2609
>                 URL: https://issues.apache.org/jira/browse/FOP-2609
>             Project: FOP
>          Issue Type: Bug
>          Components: image/png, layout/block, layout/page
>    Affects Versions: 2.1
>         Environment: Windows 7
>            Reporter: Charlie Halpern-Hamu
>         Attachments: graphic.png, less.fo, less.pdf, more.fo, more.pdf
>
>
> In the attached examples more.fo and less.fo, page 1 has a content width of 
> 5.5in, achieved with 1in page margins, and an extra 1in region-bdy 
> margin-left.
> In more.fo, the other pages have a content width of 6.5in, as they have a 
> region-body margin-left of 0in. In less.fo, the other pages have a content 
> width of 4.5in, as they have a region-body margin-left of 2in.
> There's space at the bottom of page 1, but not enough for a scale-to-fit 
> graphic. So the graphic gets bumped to page 2. The graphic correctly scales 
> its width to fit the page 2. And it correctly scales its height in proportion 
> to its width.
> However, at the bottom of page 2, text either overflows to page 3 too late or 
> too soon.
> In more.fo, text at the bottom of page 2 overflows onto page 3 too late, 
> running over the footer when it should get bumped to page 3. It appears that, 
> for the purposes of determining if there is space left on the page, the 
> height of the graphic is counted as if it had appeared on page 1, instead of 
> the wider page 2.
> In less.fo, the text at the bottom of page 2 overflows onto page 3 too soon, 
> stopping well above the footer. Again, it appears, that for the purposes of 
> determining if there is space left on the page, the height of the graphic is 
> counted as if it had appeared on page 1, instead of the narrower page 2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to