From: Design Department <design@enquora.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Table macro choices?
Date: Sun, 6 Dec 2009 14:03:26 -0700 [thread overview]
Message-ID: <2B0BF691-94C4-491E-85A1-5AC4806188C2@enquora.com> (raw)
In-Reply-To: <44132437-F12F-4C08-B547-F01F9DE645EB@googlemail.com>
> The best I can do.
Thanks Wolfgang. At first glance, it appears to cover the essentials.
I'll need to hack on it for a few days to test the minor requirements that aren't so obvious in the sample PDF, but this gets me going again.
A particular advantage (if I'm interpreting this layout correctly) is avoiding the use of column spans for header and footer material (other than the actual column headings). This report has a number of different tabular layouts that I didn't show you, each with unique column counts. Much more reliable if it isn't necessary to watch colspan values in the meta-data sections (which should really be includes.)
I would think the general requirement here isn't that unusual for certain types of technical reports. This report is for a regulatory compliance application. If printed pages within a single report are ever separated, it is essential that the meta-data for the inspection be available on each page, not just the first or last. The same must be true for many scientific and technical layouts.
I particularly need to get my head around what's different from my initial approach.
Once again, thanks. I'll report on results in a few days for anyone following this.
cheers,
david
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2009-12-06 21:03 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
2009-12-06 21:03 ` Design Department [this message]
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=2B0BF691-94C4-491E-85A1-5AC4806188C2@enquora.com \
--to=design@enquora.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).