ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Design Department <design@enquora.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Table macro choices?
Date: Sat, 5 Dec 2009 19:53:48 -0700	[thread overview]
Message-ID: <0D54D4B2-A93C-4B3D-BD8A-56696C4C5380@enquora.com> (raw)
In-Reply-To: <D393B570-998D-4402-90E8-61CB7C5F7B94@googlemail.com>


On 2009-12-05, at 7:55 AM, Wolfgang Schuster wrote:

> 
> Am 04.12.2009 um 22:58 schrieb Design Department:
> 
>> Earlier this year I attempted to set tabular material using ConTeXt while meeting *all* the following requirements:
>>> Some columns need fixed width, content must wrap to multiple lines
>>> Multi-page tables
>>> Column headings must repeat on every page
>>> Additional header information is required on every page 
>>> Additional footer information containing tabular text and graphics is required on every page
>>> Forced page breaks on arbitrary selected rows
>>> Horizontal rules between specified groups of rows
>> 
>> I was unable to meet all these requirements and reverted to LaTeX. It works, but I prefer ConTeXt and the LaTeX version takes a painfully long time to converge on optimal column widths. I'm now using TeXLive 2009, rather than 2008 - has anything changed in ConTeXt that will meet these requirements?
> 
> Can you show a example from the LaTeX output.

For Walfgang, and anyone else who has thoughts, here's a sample PDF.
http://docs.google.com/fileview?id=0B3ld3P7qGRnwOTRmOWJhYTEtMGQ1Yy00ZGE4LTk0NmQtYzk3NmJlYWIzM2Zh&hl=en

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.


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
___________________________________________________________________________________


  parent reply	other threads:[~2009-12-06  2:53 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 [this message]
2009-12-06 20:42     ` Wolfgang Schuster
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=0D54D4B2-A93C-4B3D-BD8A-56696C4C5380@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).