Re: Getting breaks: revisited

[Oleg Tkachenko]

J.Pietschmann wrote:

There are layouts for which it is very hard to decide what
to do. Consider the following:
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format";>
  <fo:layout-master-set>
    <fo:simple-page-master master-name="thin"
      page-width="110mm" page-height="297mm">
      <fo:region-body/>
    </fo:simple-page-master>
    <fo:simple-page-master master-name="thick"
      page-width="210mm" page-height="297mm">
      <fo:region-body/>
    </fo:simple-page-master>
    <fo:page-sequence-master master-name="master">
      <fo:repeatable-page-master-reference
        maximum-repeats="100" master-reference="thin"/>
      <fo:repeatable-page-master-reference master-reference="thick"/>
    </fo:page-sequence-master>
  </fo:layout-master-set>
  <fo:page-sequence master-reference="master">
    <fo:flow flow-name="xsl-region-body">
      <fo:block width="150mm">blabla..............</fo:block>
    </fo:flow>
  </fo:page-sequence>
</fo:root>

Should this create 100 empty pages and render the text onto
the 101st page, or should it squeeze it onto the first page,
thereby violating the advised width constraint of the block?

btw, how does such a case addressed by the spec? Apparently FOP, antenna and xep do squeeze content. Isn't it an example of overconstrained geometry (5.3.4)?

--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]