ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: "'ntg-context@ntg.nl'" <ntg-context@ntg.nl>
Subject: Re: tables: templates en page splitting
Date: Sun, 05 Jul 1998 15:24:32 +0200	[thread overview]
Message-ID: <359F7E90.24F1B9B1@wxs.nl> (raw)

Berend de Boer wrote:

> How can I setup table templates with table headers?
> 
> The manual is inaccurate in this respect (it says you can do a
> \def\mytemplate{\starttable[]}, but this gives errors in
> \starttabel[mytemplate] ).

This is what the documentation in core-tab says: 

%D \starttypen
%D \definetabletemplate[test][|||]
%D
%D \starttabel[test]
%D \VL test \VL test \VL\AR
%D \VL test \VL test \VL\AR
%D \VL test \VL test \VL\AR
%D \stoptabel
%D \stoptypen

> In the sources I saw the \definetabletemplate. This works for setting up
> your column definitions. I also like to add customer headers.

Right. What are customer headings? 

> Also my tables don't seem to split. I use \starttabellen. Are there some
> rules? Like minimum of rows, or something else?

In what way? 

\startbuffer
\starttabelkop
\HL
\NC \bf Parameter        \NC \bf Beschikbaar als commando \NC\SR
\HL
\stoptabelkop

\starttabelstaart
\HL
\stoptabelstaart

\starttabellen[|l|l|]
\NC bovenafstand         \NC \type{\bovenafstand}        \NC\FR
\NC bovenhoogte          \NC \type{\bovenhoogte}         \NC\MR
\NC hoofdafstand         \NC \type{\hoofdafstand}        \NC\MR
\NC hoofdhoogte          \NC \type{\hoofdhoogte}         \NC\MR
\NC kopniveau            \NC \type{\kopniveau}           \NC\MR
\NC kopwit               \NC \type{\kopwit}              \NC\MR
\NC rugwit               \NC \type{\rugwit}              \NC\MR
\NC margeafstand         \NC \type{\margeafstand}        \NC\MR
\NC margebreedte         \NC \type{\margebreedte}        \NC\MR
\NC linkermargebreedte   \NC \type{\linkermargebreedte}  \NC\MR
\NC rechtermargebreedte  \NC \type{\rechtermargebreedte} \NC\MR
\NC randafstand          \NC \type{\randafstand}         \NC\MR
\NC randbreedte          \NC \type{\randbreedte}         \NC\MR
\NC linkerrandbreedte    \NC \type{\linkerrandbreedte}   \NC\MR
\NC rechterrandbreedte   \NC \type{\rechterrandbreedte}  \NC\MR
\NC papierbreedte        \NC \type{\papierbreedte}       \NC\MR
\NC papierhoogte         \NC \type{\papierhoogte}        \NC\MR
\NC zetbreedte           \NC \type{\zetbreedte}          \NC\MR
\NC zethoogte            \NC \type{\zethoogte}           \NC\MR
\NC tekstbreedte         \NC \type{\tekstbreedte}        \NC\MR
\NC teksthoogte          \NC \type{\teksthoogte}         \NC\MR
\NC voetafstand          \NC \type{\voetafstand}         \NC\MR
\NC voethoogte           \NC \type{\voethoogte}          \NC\MR
\NC onderhoogte          \NC \type{\onderhoogte}         \NC\MR
\NC onderafstand         \NC \type{\onderafstand}        \NC\LR
\stoptabellen
\stopbuffer

\splitsplaatsblok[regels=1]
  {\plaatstabel
     [hier][tab:parameters]
     {Parameters voor pagina layout.}}
  {\haalbuffer}

This should work. Can you collect 'failing tables', so I can optimize
the mechanism? When I have enough failing examples I'll look at it
(these are the least easy things to implement in TeX) 

The example is from the beginners manual (see latest maps). Suffixes are
automatically added. (\splitfloat, \teilegleitobjekt) Also look at the
buffer mechanism ([name] is optional). Keeps your sources clean!

Hans 

-----------------------------------------------------------------
                                              Hans Hagen | PRAGMA
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | fax: 038 477 53 74 | mail: pragma@wxs.nl
-----------------------------------------------------------------


             reply	other threads:[~1998-07-05 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-05 13:24 Hans Hagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-07-07  7:19 Hans Hagen
1998-07-03 18:34 Berend de Boer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=359F7E90.24F1B9B1@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).