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?

all right, i tracked it down and it's confusing.  all i did was remove

<xsl:attribute-set name="section.title.level1.properties">
 <xsl:attribute name="break-before">page</xsl:attribute>
</xsl:attribute-set>
----- below was removed ------
<xsl:attribute-set name="section.title.level2.properties">
 <xsl:attribute name="break-before">page</xsl:attribute>
</xsl:attribute-set>


  my <qandaset> is directly within a top-level section (inside a chapter),
so (as i interpret it, i might be way off base), that section would be 
considered a level one and, somehow, the title on my <qandaset> is being
interpreted as s level-two section, and a pagebreak is being inserted.

  does the section.title.level2.properties attribute apply to <qandaset>
titles as well?  that would come as a real shock, since that's not
how i read it.

rday



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