Hi All, Does anybody know why FOP Trunk completely screws up the rendering of the attached file? It works fine when removing the fo:inline element, so I guess this has something to do with that element. FOP 0.95 renders the file correctly, both with and without the fo:inline.
Thanks, Vincent
<?xml version="1.0"?> <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format" font-family="serif" font-size="11pt" text-align="justify" language="en"> <fo:layout-master-set> <fo:simple-page-master master-name="body-first" page-width="210mm" page-height="297mm" margin-top="2.5cm" margin-bottom="2.5cm" margin-left="3.5cm - 0pt" margin-right="3cm"> <fo:region-body margin-bottom="25pt" margin-top="1cm" column-gap="12pt" column-count="1"/> <fo:region-before region-name="xsl-region-before-first" extent="1cm" display-align="before"/> <fo:region-after region-name="xsl-region-after-first" extent="12pt" display-align="after"/> </fo:simple-page-master> <fo:simple-page-master master-name="body-odd" page-width="210mm" page-height="297mm" margin-top="2.5cm" margin-bottom="2.5cm" margin-left="3.5cm - 0pt" margin-right="3cm"> <fo:region-body margin-bottom="25pt" margin-top="1cm" column-gap="12pt" column-count="1"/> <fo:region-before region-name="xsl-region-before-odd" extent="1cm" display-align="before"/> <fo:region-after region-name="xsl-region-after-odd" extent="12pt" display-align="after"/> </fo:simple-page-master> <fo:simple-page-master master-name="body-even" page-width="210mm" page-height="297mm" margin-top="2.5cm" margin-bottom="2.5cm" margin-left="3cm - 0pt" margin-right="3.5cm"> <fo:region-body margin-bottom="25pt" margin-top="1cm" column-gap="12pt" column-count="1"/> <fo:region-before region-name="xsl-region-before-even" extent="1cm" display-align="before"/> <fo:region-after region-name="xsl-region-after-even" extent="12pt" display-align="after"/> </fo:simple-page-master> <fo:page-sequence-master master-name="body"> <fo:repeatable-page-master-alternatives> <fo:conditional-page-master-reference master-reference="body-first" page-position="first"/> <fo:conditional-page-master-reference master-reference="body-odd" odd-or-even="odd"/> <fo:conditional-page-master-reference odd-or-even="even" master-reference="body-even"/> </fo:repeatable-page-master-alternatives> </fo:page-sequence-master> </fo:layout-master-set> <fo:page-sequence hyphenate="true" master-reference="body" language="en" format="1" hyphenation-character="-" hyphenation-push-character-count="2" hyphenation-remain-character-count="2"> <fo:flow flow-name="xsl-region-body" start-indent="0" end-indent="0pt"> <fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">So it may be better to start the combining process as soon as possible, but as seen above paragraphs must be typeset first. Or maybe not? The problem was to define an ordering on the layouts. When a page break can occur in the middle of a paragraph, is it really a problem if that paragraph is not finished yet? As long as the previous paragraphs have their optimal layouts, the total order should be available. All that can happen inside the paragraph is that there may be a few lines more or less on the page; that means a few more boxes added to the set of layouts thatâs available at the beginning of the paragraph. If that set was totally ordered, it should remain so when adding the boxes corresponding to the lines of the current paragraph. That said, itâs not totally clear what happens when not all the lines have the same height. Letâs imagine that a paragraph contains two inline images whose heights are 1.5 times the normal line height. Letâs assume thereâs one layout in which both images are on the same line; and another one where spaces are slightly more shrunk so that the first image can be placed on the preceding line (<fo:inline>Figure 12</fo:inline>). The first layout will be 4.5 units high while the second one will be 5 units high. Maybe that wonât be a problem, butâ¦</fo:block> </fo:flow> </fo:page-sequence> </fo:root>
