ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Table macro choices?
Date: Sun, 6 Dec 2009 21:42:04 +0100	[thread overview]
Message-ID: <44132437-F12F-4C08-B547-F01F9DE645EB@googlemail.com> (raw)
In-Reply-To: <0D54D4B2-A93C-4B3D-BD8A-56696C4C5380@enquora.com>


Am 06.12.2009 um 03:53 schrieb Design Department:

> The main point is that the tabular material runs from just a single to several hundred rows and each page *must* contain both the header and footer explanations associated with the table. Normally the pages are broken at a fixed increment of rows depending on the type of data, usually 20 or 32 per page, but other values are possible. For good measure, field technicians often want a forced page break at an arbitrary row position.
> 
> Two of the table columns contain data which may wrap to multiple lines, as illustrated.
> 
> Is all this possible without writing a new tabular macro? I could get close, but couldn't get the table footer repeating on every page or the forced page breaks. That was using the TeXLive 2008 distribution.


The best I can do.

\setuppapersize[A4,landscape][A4,landscape]

\setuptables[bodyfont=8pt]

\initializeboxstack{table}

\savebox{table}{footer}{\starttable[s0|l|l|l|l|l|l|]
\NC Accept \NC \THREE No detectable indications at the time of inspection            \NC Reject \NC See remarks for explanation            \NC\NR
\NC BT     \NC Burn-through                     \NC IP  \NC Incomplete penetration   \NC SHOTS  \NC Number of shots taken                  \NC\NR
\NC CR     \NC Crack                            \NC IUC \NC Internal undercut        \NC SIZE   \NC Size of pipe                           \NC\NR
\NC EP     \NC Excessive penetration            \NC LC  \NC Low cover                \NC SOD    \NC Source to object distance              \NC\NR
\NC EUC    \NC External under-cut               \NC LOF \NC Lack of fusion           \NC STAMP  \NC Welder’s stamp                         \NC\NR
\NC EXP    \NC Single or double wall exposure   \NC MAT \NC Material being inspected \NC TECH   \NC Inspection technique                   \NC\NR
\NC HB     \NC Hollow bead                      \NC OFD \NC Object to film distance  \NC THICK  \NC Thickness of tubular wall or component \NC\NR
\NC HL     \NC High/low                         \NC P   \NC Porosity                 \NC VIEW   \NC Single Or Double wall viewing          \NC\NR
\NC IC     \NC Internal concavity               \NC S   \NC Slag                     \NC WT     \NC Wall thickness                         \NC\NR
\NC SZ     \NC Component diameter or dimensions \NC SW  \NC Single wall              \NC DW     \NC Double wall                            \NC\NR
\stoptable}

\savebox{table}{header}{\input knuth }

\starttext

\splitfloat[lines=16,inbetween=\foundbox{table}{footer}\page,after=\foundbox{table}{footer}]
  {\foundbox{table}{header}}
  %{\placefigure[none]{}{\foundbox{table}{header}}}
  {\bTABLE[split=yes]
   \dorecurse{100}{\bTR\bTD#1\eTD\bTD text \eTD\eTR}
   \eTABLE}

\stoptext

Wolfgang

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-12-06 20:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 21:58 Design Department
2009-12-05 14:55 ` Wolfgang Schuster
2009-12-05 17:47   ` Design Department
2009-12-05 18:01     ` Wolfgang Schuster
2009-12-06  2:53   ` Design Department
2009-12-06 20:42     ` Wolfgang Schuster [this message]
2009-12-06 21:03       ` Design Department

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=44132437-F12F-4C08-B547-F01F9DE645EB@googlemail.com \
    --to=schuster.wolfgang@googlemail.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).