Hi Stefan,
The parameters for column count apply to page-sequences in FO output. They are used in
declaring the fo:simple-page-masters used in page-sequences. There is a set of column
params for each class of page-master, such as front, body, back, etc.
The abstract element is a block element that does not generate its own page-sequence.
In that respect, it is more like a figure or table that spans multiple columns. Such
column spans are achieved on an fo:block by adding a span="all" property to the block.
I suspect you already have something like that for the article title and author.
To apply that property to abstract, you can add it to the attribute-set named
'abstract.properties'. However, some FO processors don't handle such spanned blocks
when they are contained in another block, as for title page elements. See this doc
for more details on this complication.
http://www.sagehill.net/docbookxsl/MultiColumns.html#PageColSpans
But if you have spans working for the title, then getting it to work for abstract
should not be too hard.
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Stefan Seefeld" <[email protected]>
To: "DocBook Apps Mailing List" <[email protected]>
Sent: Saturday, May 19, 2012 11:53 AM
Subject: [docbook-apps] two-column layout for article abstract
Hello,
I'm trying to customize the fo stylesheets to produce a IEEE-compliant
paper. The template that I'm looking at prints the abstract within the
first column. It seems that the DB stylesheets aren't prepared to have
the abstract be part of the two-column layout, as there doesn't appear
to be a "column.count.abstract" parameter. Is that a simple omission, or
is there a more fundamental reason behind this ?
Thanks,
Stefan
--
...ich hab' noch einen Koffer in Berlin...
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
