This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [docbook-apps] two-column problem

From: Jirka Kosek <jirka at kosek dot cz>
To: Bob Stayton <bobs at sco dot com>
Cc: David Tolpin <dvd at renderx dot com>, docbook-apps at lists dot oasis-open dot org
Date: Fri, 20 Jun 2003 08:46:13 +0200
Subject: Re: [docbook-apps] two-column problem
References: <20030619173730.GA13816@notebook> <200306191748.h5JHmj0C021340@adat.davidashen.net> <20030619111541.O3938@sco.com>

Bob Stayton wrote:

Looking at the DocBook XSL stylesheets, this could be
tough to implement.  The stylesheets often nest fo:blocks
as nested DocBook elements are processed.  If a column
span is requested in some nested element (like a table
in a section in a chapter), then all pending blocks would
have to be closed out, a new block started that is a direct
child of the fo:flow, and then start over with the blocks
that follow the table.

More easy to implement solution will be postprocessing of FO which will "unwrap" nested spanned objects directly under the corresponding fo:flow. Something similar to Ken's PSMI stylesheet for rotated tables.

Jirka

--
-----------------------------------------------------------------
  Jirka Kosek  	
  e-mail: jirka@kosek.cz
  http://www.kosek.cz

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Follow-Ups:
- Re: [docbook-apps] two-column solution
  - From: Lars Trieloff

References:
- Re: [docbook-apps] two-column problem
  - From: Lars Trieloff
- Re: [docbook-apps] two-column problem
  - From: David Tolpin
- Re: [docbook-apps] two-column problem
  - From: Bob Stayton

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]