ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Multi-page tables
Date: Fri, 17 Mar 2006 11:54:00 +0100	[thread overview]
Message-ID: <441A9548.8040402@elvenkind.com> (raw)
In-Reply-To: <ba4316d30603161727h50dd3773p3b929b7b84f05564@mail.gmail.com>



Randall Skelton wrote:
> Just curious if anyone has any suggestions on the request below.  I've 
> searched the list archives and found similar questions but, 
> unfortunately, no answers.  The tables are going in an appendix of work 
> and generally span 5-10 pages... clever (or ugly) hacks greatly 
> appreciated!

My 'solution' would be to drop the page-spanning requirement,
because that makes the rest trivial. I am not saying that it cannot
be done, I just do not know.

Cheers, taco

  reply	other threads:[~2006-03-17 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 19:44 Randall Skelton
2006-03-17  1:27 ` Randall Skelton
2006-03-17 10:54   ` Taco Hoekwater [this message]
2006-03-17 12:23     ` Hans Hagen
2006-03-18 19:29       ` Henning Hraban Ramm
2006-03-20  8:36         ` Hans Hagen

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=441A9548.8040402@elvenkind.com \
    --to=taco@elvenkind.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).