From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: multi-column spread control (was Re: beginner's questions)
Date: Tue, 14 Nov 2000 18:12:11 +0100 [thread overview]
Message-ID: <3.0.6.32.20001114181211.013f6100@pop.wxs.nl> (raw)
In-Reply-To: <m34s1a4i4d.fsf@coe.uga.edu>
At 11:45 AM 11/14/00 -0500, Ed L Cashin wrote:
>I reviewed vsplit in the TeXbook, and it looks like by getting very
>fancy with low-level glues and penalties (like the fancy index
>example, "Paragraph Manuvers", number seven in Appendix D., but
>vertically instead of horizontally) one could control exactly how the
>columns balanced.
>
>But for a macropackage author like yourself, that would mean breaking
>open the box255 and changing the vertical glue between the elements.
>Maybe that's the kind of compensation and nightmare you're talking
>about?
Balancing is not that hard:
loop
split box to height
if left over is larger than split off part
then
decrease height
else
exitloop
endloop
but you're right, there are a few gory details. If you want to manipulate
boxes:
texexec --modu supp-box
is your friend
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2000-11-14 17:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 16:51 beginner's questions Wouter Verheijen
2000-11-09 17:20 ` Frans Goddijn
2000-11-09 17:54 ` Hans Hagen
2000-11-09 17:40 ` Hans Hagen
2000-11-09 19:25 ` Ed L Cashin
2000-11-11 17:34 ` siepo
2000-11-11 17:56 ` Frans Goddijn
2000-11-24 12:51 ` Christopher Tipper
2000-11-11 19:41 ` Berend de Boer
2000-11-12 11:34 ` siepo
2000-11-12 18:56 ` Denis B. Roegel
2000-11-13 9:37 ` Hans Hagen
2000-11-13 16:54 ` multi-column spread control (was Re: beginner's questions) Ed L Cashin
2000-11-13 17:17 ` Hans Hagen
2000-11-13 18:43 ` Ed L Cashin
2000-11-13 18:44 ` Ed L Cashin
2000-11-14 7:49 ` Hans Hagen
2000-11-14 13:27 ` Ed L Cashin
2000-11-14 14:13 ` Hans Hagen
2000-11-14 14:49 ` Ed L Cashin
2000-11-14 15:49 ` Hans Hagen
2000-11-14 16:45 ` Ed L Cashin
2000-11-14 17:12 ` Hans Hagen [this message]
2000-11-14 18:25 ` Ed L Cashin
2000-11-15 0:23 ` Hans Hagen
2000-11-15 1:15 ` Ed L Cashin
2000-11-15 17:20 ` voting & form design (was: multi-column spread control) Hraban
2000-11-14 21:51 ` multi-column spread control (was Re: beginner's questions) Denis B. Roegel
2000-11-15 0:20 ` Hans Hagen
2000-11-15 23:28 ` Denis B. Roegel
2000-11-19 19:31 ` Hans Hagen
2000-11-12 14:04 ` Documentation Tasks (was: " Hraban
2000-11-13 7:38 ` beginner's questions Hans Hagen
2000-11-13 21:26 ` siepo
2000-11-09 19:19 ` Berend de Boer
[not found] <Hans Hagen's message of "Tue, 14 Nov 2000 18:12:11 +0100">
[not found] ` <Hans Hagen's message of "Tue, 14 Nov 2000 16:49:12 +0100">
[not found] ` <Hans Hagen's message of "Tue, 14 Nov 2000 15:13:29 +0100">
[not found] ` <Hans Hagen's message of "Tue, 14 Nov 2000 08:49:03 +0100">
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=3.0.6.32.20001114181211.013f6100@pop.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).