OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

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


Subject: Re: [docbook] continued label for long tables


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Paul,
Bob Stayton's book provides a customization to add "Continued" labels
if  you're using XEP as your fo renderer:

http://www.sagehill.net/docbookxsl/TableTemplateCust.html#TableContinuedLabel

David

On 01/25/2012 07:24 AM, Paul Tremblay wrote:
> I have a question about the XSL stylesheets in docbook. For a long 
> table, it is desirable to have the title repeated on every page,
> with the word "continued" after the first occurrence. Most FO
> processors don't implement the latest standards of FO, so we need
> some work around. I have used two in the past:
> 
> 1. Include the label in a running header or footer.
> 
> 2. Break the table into two table. Process the first table as
> normal. For the second table, create a header with title and the
> continued label.
> 
> (1)  requires that you create your own page sequences and call on
> them. Doing so is not difficult. The difficult part comes in
> calling the page sequences in the right order. For example, if you
> have a long table in the middle of a chapter, you would have to
> call the page sequence template, apply all the templates for the
> text before the long table, call the long table sequence, then call
> on the original sequence for the rest of the content. While this
> solution is possible, it does not lend itself to reuse, because you
> would have to do a lot of re-writing each time.
> 
> (2) requires that you know how much of your table fits on one page 
> before you write the rest of it. Though you cannot know the exact
> inches your text will take, you can make an educated guess and
> readjust the table after a few trial runs. Though (2) is far from
> perfect, at seems to provide less re-writing than (1) and lends
> itself for reuse.
> 
> Any thoughts or hints before I launch into implementing (2)?
> 
> Paul

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPIAVDAAoJEMHeSXG7afUhQ80IAI4UYnbKcDCfl6B4sci42n6D
PuUwx5M+oL2QbWoAXaXADEDvrQ5yGtIzretqAEuFvbnf59YNwu4Xnoab797FrHfy
MIAR7s1WCTJnowhzBd9gc82JDItrYfN1wqdAsa5vFkt06uSPBX591NOFzXNKAmBd
NVKjUPFPq6oy+yB3cHFzDeynt3LKDu6tJaEI7YzuhUSvMXKrrVW5oNbEpvuzWx9E
1gd9m/Sn496ML3awslTY8H3c/YCbS9hH+sd7S5WRkdR31El7t8ErpWEYteCane81
EISjuw+/FyAomx0nrq+CRhx2rvbL9Xd5+GiuIA5AmdMHgfOn8CDqjRa+yGieLBo=
=1Dre
-----END PGP SIGNATURE-----


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