From: Hans Hagen <pragma@wxs.nl>
Subject: splitting tables
Date: Fri, 16 Jun 2006 23:14:32 +0200 [thread overview]
Message-ID: <44931F38.8030000@wxs.nl> (raw)
Hi,
I will upload an alpha release with a cleaned up table (float) split
mechanism. The splitter works for all three table types, either or not
in floats with repeated head (and tail) sections, optionally with
automatic (may become default) caption height detection etc. It works ok
on some simple test files, but I have no time to test more obscure
situations.
I'm not that sure if everything is downward compatible, but splitting is
always tricky (and demanded some intervention) anyway. So, if you are
using this kind of functionality, go ahead, download and test ..
\setupTABLE[split=repeat]
\input tufte \endgraf
\splitfloat[lines=11]
{\placetable{\dorecurse{10}{test\recurselevel\endgraf}}}
{\bTABLE\dorecurse{100}{\bTR \bTD test \eTD \eTR}\eTABLE}
\input tufte \page
\input tufte \endgraf
\splitfloat[lines=0]
{}
{\bTABLE\dorecurse{100}{\bTR \bTD test \eTD \eTR}\eTABLE}
\input tufte \endgraf \page
\input tufte \endgraf
\bTABLE\dorecurse{100}{\bTR \bTD test \eTD \eTR}\eTABLE
\input tufte \page
\setuptabulate[split=yes]
\input tufte \endgraf
\splitfloat[lines=11]
{\placetable{\dorecurse{10}{test\recurselevel\endgraf}}}
{\starttabulate\dorecurse{200}{\NC test \NC test \NC \NR}\stoptabulate}
\input tufte \page
\input tufte \endgraf
\splitfloat[lines=0]
{}
{\starttabulate\dorecurse{200}{\NC test \NC test \NC \NR}\stoptabulate}
\input tufte \page
\input tufte \endgraf
\starttabulate\dorecurse{200}{\NC test \NC test \NC \NR}\stoptabulate
\input tufte \page
\setuptables[split=yes]
\newtoks\TestToks
\TestToks\emptytoks
\appendtoks\starttablehead\to\TestToks
\dorecurse{3}{\appendtoks\VL head \VL head \VL \SR\to\TestToks}
\appendtoks\stoptablehead\to\TestToks
\appendtoks\starttabletail\to\TestToks
\dorecurse{3}{\appendtoks\VL tail \VL tail \VL \SR\to\TestToks}
\appendtoks\stoptabletail\to\TestToks
\appendtoks\starttables[|c|c|]\to\TestToks
\dorecurse{100}{\appendtoks\VL test \VL test \VL \SR\to\TestToks}
\appendtoks\stoptables\to\TestToks
\input tufte \endgraf
\splitfloat[lines=auto] % [lines=11]
{\placetable{\dorecurse{10}{test\recurselevel\endgraf}}}
{\the\TestToks}
\input tufte \page
\input tufte \endgraf
\splitfloat[lines=0]
{}
{\the\TestToks}
\input tufte \page
\input tufte \endgraf
\the\TestToks
\input tufte \page
Watch the lines=auto option! Mechanisms like this will never be perfect,
but I think that the cleanup is not that bad. Especially the \startable
bits and pieces needs some more testing, but then, i need to cleanup up
that code anyway (write a cleaner version of that whole table mechanism).
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next reply other threads:[~2006-06-16 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 21:14 Hans Hagen [this message]
2006-06-17 21:15 ` Johannes Graumann
2006-06-18 21:10 ` 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=44931F38.8030000@wxs.nl \
--to=pragma@wxs.nl \
--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).