Changes

Jump to navigation Jump to search
39 bytes removed ,  10:35, 27 March 2014
m
no edit summary
Try to divide your table into...
* {{cmd|bTABLEheadcmdbTABLEhead}} (table header)* {{cmd|bTABLEnextcmdbTABLEnext}} (alternate table header on following pages)* {{cmd|bTABLEbodycmdbTABLEbody}} (table body)* {{cmd|bTABLEfootcmdbTABLEfoot}} (table footer)and {{cmd|setupTABLEcmdsetupTABLE}}<tt>[split=yes]</tt> or <tt>[split=repeat]</tt>
see also [[source:tabl-ntb.mkiv|tabl-ntb.mkiv]]
In this case the <b>table head</b>
(all between {{cmd|bTABLEheadcmdbTABLEhead}} and {{cmd|eTABLEheadcmdeTABLEhead}})
is printed only once at the beginning of the table. But if you use <tt>[split=repeat]</tt>,
it is printed on top of every new page, that contains parts of
your multipage table. Please take account of the fact, that the
head cells are enclosed by {{cmd|bTHcmdbTH}} and {{cmd|eTHcmdeTH}} (and not \[be]TC).
If you want to use an alternative table header for all following pages,
you can do this by defining an additional header. Just add the second header
between {{cmd|bTABLEnextcmdbTABLEnext}}...{{cmd|eTABLEnextcmdeTABLEnext}},
right after your normal head definition.
Now every additional page of the multipage table starts with the
<b>next table head</b>.
The <b>table foot</b> is declared between {{cmd|bTABLEfootcmdbTABLEfoot}} and{{cmd|eTABLEfootcmdeTABLEfoot}}. It defines the concluding row of your natural table.
'''Beware:''' Split tables often begin not on the page (or in the column, if you use them) where they ''could'' start, but on/in the next one.
56

edits

Navigation menu