ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "JOHN CULLETON" <john@wexfordpress.com>
To: <ntg-context@ntg.nl>
Subject: Headers for natural tables.
Date: Mon,  5 Mar 2007 11:24:23 -0800	[thread overview]
Message-ID: <200703051124.AA1704664@wexfordpress.com> (raw)

I hve determined by trial and error that the multiline feature [nr=2] of Natural Tables does not work well, if at all, in the TABLEhead area. But the TABLEhead area is necessary for readable split tables. Currently I use single lines in the header area and suppress some of the rules to create a multiline effect thus: 

\bTABLE [option=stretch,split=repeat]
\setupTABLE[r][1][height=0cm,width=0cm,frame=off]
\setupTABLE[c][1][width=1.7in]
\setupTABLE[r][2][bottomframe=off]
\setupTABLE[r][3][topframe=off]
\bTABLEhead
\bTR          %dummy row
\bTH \eTH
\bTH \eTH
\bTH \eTH
\eTR
\bTR         %first visible row
\bTH  
{\bf Investment} \eTH
\bTH 
{\bf Portfolio } \eTH
\bTH 
{\bf Average Stock } \eTH
\eTR
\bTR
\bTH  
{\bf Category} \eTH
\bTH 
{\bf Allocation} \eTH
\bTH 
{\bf  Market Exposure} \eTH
\eTR
\eTABLEhead
...
This example also uses the (apparently) obligatory dummy row as described by others.

Natural Tables have been around for a while. It is unfortunate that no one has come up with a real manual for these tables. All that exists are "learn by example" documents, which do not describe limitations such as the one I worked around in the above code. 


John Culleton


_________________________________________________________________
Need personalized email and website? Look no further. It's easy
with Doteasy $0 Web Hosting! Learn more at www.doteasy.com

             reply	other threads:[~2007-03-05 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05 19:24 JOHN CULLETON [this message]
2007-03-06 12:06 ` Wolfgang Schuster

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=200703051124.AA1704664@wexfordpress.com \
    --to=john@wexfordpress.com \
    --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).