OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] any idea why a <qandaset> would be forced to thenext page

On Thu, 8 May 2003, Bob Stayton wrote:

> On Thu, May 08, 2003 at 11:17:22AM -0400, Robert P. J. Day wrote:
> > 
> >   as part of a sample markup document, i have a *very* simple
> > <qandaset>, after an introductory sentence, but when i generate
> > the PDF (xsltproc -> fop), the entire qandaset is being forced
> > to the next page.
> > 
> >   certainly, nothing i read in the semantics for qandaset suggests
> > this should happen.
> > 
> >   any advice?
> I can't seem to duplicate this problem.
> Can you post a short sample file that illustrates it?

actually, i'm being innovative :-), and isolating where the problem is
by looking at the intermediate .fo file.  from my xml file, i generated
the .fo file in three different ways:

1) xsltproc
2) xalan
3) saxon

  in *every* case, the <fo:block> element was as you see below -- with
a 'break-before="page"' attribute, which forced the <qandaset> to the
next page.  [excerpt follows]

 <fo:block id="d0e373">
               <fo:block font-family="sans-serif" font-weight="bold" 
keep-with-next.within-column="always" space-before.minimum="0.8em" 
space-before.optimum="1.0em" space-before.maximum="1.2em">
                  <fo:block font-size="14pt" break-before="page">The Cat 
               <fo:list-block space-before.optimum="1em" space-before

  when i edited the .fo file and took out that attribute, then used
FOP to generate the PDF, it was fine.

  this suggests that the docbook FO stylesheets are somehow doing this,
which is what i'm about to look at.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]