From: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: columnsets and footnotes (minimal example)
Date: Mon, 9 Jan 2006 12:47:39 +0100 [thread overview]
Message-ID: <FA1B21D5-946B-4C96-AE98-D549FB115F1C@st.estfiles.de> (raw)
In-Reply-To: <43C235C1.6010801@elvenkind.com>
Am 09.01.2006 um 11:06 schrieb Taco Hoekwater:
>
>
> Steffen Wolfrum wrote:
>> ... and here is an example that shows the problem:
>
> Oops, that doesn't look right at all.
>
> Do you really need column sets, or is "normal" columns
> mode ok as well?
1)
Yes, column sets would be better.
>
> \startcolumns[n=2]
> \dorecurse{10}{\input tufte\footnote{\input ward \relax}}
> \stopcolumns
>
> Looks about right.
>
> Cheers, Taco
2)
When I try ...
\setupfootnotes[n=3]
\starttext
\startcolumns[n=2]
\dorecurse{10}{\input tufte\footnote{\input ward \relax}}
\stopcolumns
\stoptext
at the bottom of page 1 there is a lot of white space before the
footnote text of footnote 1-4 (the footnotemarkers 1 to 4 come up the
next page).
So in this example it doesn't seem to be possible to keep footnote
markers and text at the same page:
Wouldn't it be better in this case to fill page 1 also with the
footnote text of the following footnotes?
In this way the pages would look much better.
Is there a way (penalty?) to express how *urgent* footnote markers
and text need to be forced to the same page?
Or - in other words - to loosen the connection?
Thanks,
Steffen
prev parent reply other threads:[~2006-01-09 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 9:58 Steffen Wolfrum
2006-01-09 10:06 ` Taco Hoekwater
2006-01-09 11:29 ` Hans Hagen
2006-01-09 15:08 ` Steffen Wolfrum
2006-01-10 20:04 ` Problem with \placefigure FrancoisFasoli
2006-01-10 20:26 ` Taco Hoekwater
2006-01-10 21:56 ` Hans Hagen
2006-01-09 11:47 ` Steffen Wolfrum [this message]
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=FA1B21D5-946B-4C96-AE98-D549FB115F1C@st.estfiles.de \
--to=context@st.estfiles.de \
--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).