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] ensure a minimal amount of words / table rows on a page


For paragraphs, you should be able to add "widows" and "orphans" attributes
to the root.properties attribute-set.  I thought the stylesheet already set
those, but apparently not. You set those attributes to some integer, the
number of lines to be kept together.

For table elements, the default behavior is
keep-together.within-column="always" because the formal.object.properties
attribute-set is applied to tables.  For informaltable elements, there is no
keep-together.  So those must be informaltables that have rows being left
behind.  The next version of the stylesheet will have an
'informal.table.properties' attribute-set that could turn it on.  In the
meantime, you would have to do it with the informal.object.properties
attribute-set.

Regarding the full-page table that jumps to the next page instead of
following the section heading, I think perhaps the table plus its
space-before doesn't actually fit, or else it would be on the same page.
You probably want to tune the space between the heading and the table, but
there is no attribute to do that.  It would require a processing instruction
that doesn't yet exist.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Sebastian Fey" <fey@parsytec.de>
To: "Docbook-Apps (E-Mail)" <docbook-apps@lists.oasis-open.org>
Sent: Tuesday, August 03, 2004 6:58 AM
Subject: [docbook-apps] ensure a minimal amount of words / table rows on a
page


hi,


actual i dont think this is possible, but maybe someone knows a way.

it sometimes happens that xep begins a new page just for a few words or just
one row of a table.
id like it to put the whole paragraph (this should work with some
keep-together balancing but i didnt make it till now) on the next page,
and - most likely more complicated - at least 3 rows of a table instead of
one.
another problem is following: consider section-title followed by a table
that just fits on a page.
what the renderer does is writing the title on the first page, break, table
on the next page. but id rather see the table directly behind the title.

any pointers?

thx,
Sebastian






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