[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [docbook-apps] two-column problem
Thanks to all for your efforts (most especially Jeff). It appears that I'm "in business" here. In general, it would be a nice enhancement for the Stylesheets if they handled multiple columns a bit better. Thanks, Bill > -----Original Message----- > From: Jeff Beal [mailto:jeff.beal@ansys.com] > Sent: Thursday, June 19, 2003 2:03 PM > To: DocBook Apps Mailing List (E-mail) > Subject: FW: [docbook-apps] two-column problem > > I forgot to hit "Reply All" when working with Bill. For his situation, we > were able to fix the problem by changing the template for <section/> to > not > create an <fo:block/> surrounding the entire section, just around the > section header information. That won't work for all tables, of course, > and > it prevents certain types of customizations (e.g., indenting sections), > but > if page-wide tables are important, this may be an easy way to do it. > > -----Original Message----- > From: Bill Lawrence [mailto:scribe@matrixplus.com] > Sent: Thursday, June 19, 2003 11:31 AM > To: 'Jeff Beal' > Subject: RE: [docbook-apps] two-column problem > > > That's much better. Now all I have to do is to extend this logic to > figure and I'm all set. > > Thanks a bunch! > > Bill > > > -----Original Message----- > > From: Jeff Beal [mailto:jeff.beal@ansys.com] > > Sent: Thursday, June 19, 2003 9:59 AM > > To: 'Bill Lawrence' > > Subject: RE: [docbook-apps] two-column problem > > > > See what happens if you customize the <section/> template to not > create > > the > > surrounding <fo:block/>: > > <xsl:template match="section"> > > <xsl:variable name="id"> > > <xsl:call-template name="object.id"/> > > </xsl:variable> > > > > <fo:block id="{$id}"> > > <xsl:call-template name="section.titlepage"/> > > </fo:block> <!-- Close block here --> > > <xsl:variable name="toc.params"> > > <xsl:call-template name="find.path.params"> > > <xsl:with-param name="table" > > select="normalize-space($generate.toc)"/> > > </xsl:call-template> > > </xsl:variable> > > > > <xsl:if test="contains($toc.params, 'toc') > > and (count(ancestor::section)+1) <= > > $generate.section.toc.level"> > > <xsl:call-template name="section.toc"> > > <xsl:with-param name="toc.title.p" > select="contains($toc.params, > > 'title')"/> > > </xsl:call-template> > > <xsl:call-template name="section.toc.separator"/> > > </xsl:if> > > > > <xsl:apply-templates/> > > </xsl:template> > > > > > -----Original Message----- > > > From: Bill Lawrence [mailto:scribe@matrixplus.com] > > > Sent: Thursday, June 19, 2003 10:33 AM > > > To: 'Jeff Beal' > > > Subject: RE: [docbook-apps] two-column problem > > > > > > > > > Jeff, > > > > > > It is nested. The flow starts at the section, and does indeed get > > > nested one level deep. It's pretty ugly trying to trace that along. > > > Every so often, there's a <block/> tag, which seems utterly > pointless. > > > > > > > -----Original Message----- > > > > From: Jeff Beal [mailto:jeff.beal@ansys.com] > > > > Sent: Thursday, June 19, 2003 9:18 AM > > > > To: 'Bill Lawrence' > > > > Subject: RE: [docbook-apps] two-column problem > > > > > > > > Howdy Bill - > > > > > > > > Are you sure it's just a function of the table height? In looking > > > through > > > > the stylesheets briefly, it looks like only tables that are direct > > > > children > > > > of components (chapters, appendices, and the like) will be direct > > > children > > > > of <fo:flow/> objects. If a table is in a section, the section > > > element > > > > will > > > > create a surrounding <fo:block/>, which is what *should* cause > this > > > error. > > > > If you can verify that the block with the span attribute is a > direct > > > child > > > > of an <fo:flow>, this looks like a XEP error. > > > > > > > > Jeff > > > > -----Original Message----- > > > > From: Bill Lawrence [mailto:scribe@matrixplus.com] > > > > Sent: Thursday, June 19, 2003 10:08 AM > > > > To: docbook-apps@lists.oasis-open.org > > > > Subject: [docbook-apps] two-column problem > > > > > > > > > > > > I'm trying to run two columns using landscape pages, and I > > > need to set > > > > some > > > > tables to span both columns. I've set the pgwide > > > attribute, and this > > > > seems > > > > to work erratically. If has a rather small vertical depth, the > span > > > works > > > > just fine. However, if I create a table that is larger > > > than a single > > > > page, > > > > XEP reports the following: > > > > > > > > {?'span' attribute on block ignored because the element is not a > > > direct > > > > child of a flow} > > > > > > > > After which the table reverts to two-columns. > > > > > > > > Any thoughts? > > > > > > > > > > > > Bill Lawrence > > > > Senior Technical Writer > > > > Matrix Solutions > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]