https://issues.apache.org/bugzilla/show_bug.cgi?id=51935
--- Comment #3 from Glenn Adams <gl...@skynav.com> 2011-10-28 07:02:40 UTC ---
(In reply to comment #2)
> Created attachment 27859 [details]
> zip file containing riddle.fo and riddle.pdf file
>
> Apache FOP does not properly handle the <xsl:attribute
> name="keep-with-next.within-page">always</xsl:attribute> and <xsl:attribute
> name="keep-together.within-page">always</xsl:attribute> options in basic
> blocks.
>
> You will notice from the PDF snap that the Apache FOP places a break between
> 2.1.1. Bay: 25 and its accompanying image. (To get to this section in the PDF
> expand Section 2. Substation Riddle Section 2.1. Voltage level: D).
>
> I have compared Apache FOP (Vrsn: fop-1.0) with RenderX XEP (Vrsn:
> xep-4.19-20110414) XSL-FO using processors using XMLmind XSL Utility (Vrsn:
> 4.5.0-01) to render DITA Files into PDF format. The Apache FOP does not
> properly handle the <xsl:attribute
> name="keep-with-next.within-page">always</xsl:attribute> option.
Your description of the problem remains in the XSLT domain, not XSL-FO.
There is no such thing as <xsl:attribute
name="keep-with-next.within-page">always</xsl:attribute> in XSL-FO.
In XSL-FO, this is a property on an FO object, e.g.,
<fo:block keep-with-next.within-page="always">...</fo:block>
Also, I would advise you to try to narrow down the problem to the smallest
XSL-FO input that reproduces the problem. It is difficult to have to wade
through the 1MB riddle.fo file to look for the problem area, which I see is
contained in the following XSL-FO fragment:
<fo:block space-before.optimum="1.5em" space-before.minimum="1.2em"
space-before.maximum="1.8em" space-after.optimum="0.75em"
space-after.minimum="0.6em" space-after.maximum="0.9em" hyphenate="false"
font-family="sans-serif" font-weight="bold" text-align="left"
keep-with-next.within-column="always" font-size="140%" padding-bottom="0.05em"
border-bottom="0.6pt solid blue" keep-with-next.within-page="always">2.1.1.
Bay: 25
</fo:block>
<fo:block space-before.optimum="0.75em" space-before.minimum="0.6em"
space-before.maximum="0.9em" space-after.optimum="0.75em"
space-after.minimum="0.6em" space-after.maximum="0.9em">
<fo:block space-before.optimum="0.75em" space-before.minimum="0.6em"
space-before.maximum="0.9em" space-after.optimum="0.75em"
space-after.minimum="0.6em" space-after.maximum="0.9em"
id="_4WuGAAEqEeG8i4jXCiAfTQ__I_io3oa_">
<fo:block space-before.optimum="0.75em" space-before.minimum="0.6em"
space-before.maximum="0.9em" space-after.optimum="0.75em"
space-after.minimum="0.6em" space-after.maximum="0.9em" hyphenate="false"
font-family="sans-serif" font-weight="bold" text-align="left"
keep-with-next.within-column="always" font-size="120%"/>
<fo:block space-before.optimum="1.5em" space-before.minimum="1em"
space-before.maximum="2em"
space-after.optimum="1.5em" space-after.minimum="1em" space-after.maximum="2em"
id="_4WuGAAEqEeG8i4jXCiAfTQ__I_d16yk_">
<fo:block border-before-width.conditionality="discard"
border-after-width.conditionality="discard">
<fo:block space-before.optimum="0.75em" space-before.minimum="0.6em"
space-before.maximum="0.9em" space-after.optimum="0.75em"
space-after.minimum="0.6em" space-after.maximum="0.9em" font-size="110%"
text-indent="1em"/>
<fo:block text-align="center">
<fo:external-graphic
src="url(file:/C:/helinks/workspace/workspaces/r2be/build.com.helinks.sts/workspaces/riddle/Report/items/Ridde_D_25_fun.png)"
content-width="247px"/>
</fo:block>
</fo:block>
<fo:block hyphenate="false" font-style="italic"
space-before.optimum="0.5em" space-before.minimum="0.4em"
space-before.maximum="0.6em" space-after.optimum="0.5em"
space-after.minimum="0.4em" space-after.maximum="0.6em" text-align="left"
keep-with-previous.within-column="always">Figure 2. Function Diagram of
Ridde/D/25</fo:block>
</fo:block>
</fo:block>
</fo:block>
</fo:block>
For example, if you started with the above fragment, then removed as much
extraneous material that still exhibits the problem, then you would have
reduced it to a manageable level.
Finally, note that there is already a test for
keep-with-next.within-page="always" in the FOP test suite (I will attach an
edited version of this test to this bug report which you can use as a
template). Perhaps you could verify this yourself and then modify this using
your minimal data to try to reproduce your problem.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
