From: Henning Hraban Ramm <hraban@fiee.net>
Subject: columns issues
Date: Sat, 14 Jan 2006 16:02:17 +0100 [thread overview]
Message-ID: <1D746AF7-BFF3-4306-9C3B-52B04517FA2E@fiee.net> (raw)
Hello wizards!
The \startcolumns ... \column ... \stopcolumns block handling seems
somewhat broken.
Maybe these "old" columns are deprecated, but I guess they should
work. (And I would like to document them.)
Consider this:
\starttext
\input ward
\startcolumns
\input ward
\column
\input knuth
\stopcolumns
\input tufte
\stoptext
In this case \column works (it doesn't seem to work always), so that
the left column is much shorter than the right one.
But the following paragraph (tufte) is typeset just after the last
line of the left column, so that some lines overprint.
And with [rule=on] the rule is only as short as the left column.
[option=background] also only considers the leftmost (or first in
[direction=left]) column.
Maybe this behaviour is sometimes useful, but I don't think it should
be default.
[balance=no] doesn't affect the balancing of columns, but flushes the
page (i.e. the tufte paragraph moves to the next page). With [n=3]
you see that it doesn't use the whole remaining page.
The whole problem seems to be \column, because without that, everthing
(?) works.
I didn't find out what the options ntop, blank, height and align are
for; I tried several values and nothing seemed to change.
[The source is http://source.contextgarden.net/page-mul.tex
but I don't understand too much of it.]
After looking in the manual, I guess I should consider using
paragraphs or columns sets for most of my use cases, but anyway...
Grüßlis vom Hraban!
---
http://www.fiee.net/texnique/
http://contextgarden.net
http://www.cacert.org (I'm an assurer)
next reply other threads:[~2006-01-14 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 15:02 Henning Hraban Ramm [this message]
2006-01-16 10:28 ` Taco Hoekwater
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=1D746AF7-BFF3-4306-9C3B-52B04517FA2E@fiee.net \
--to=hraban@fiee.net \
--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).