From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Subject: Footnote bug still there!
Date: Fri, 13 Jul 2001 17:35:40 +0200 [thread overview]
Message-ID: <714073312.20010713173540@bigfoot.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
Hi,
I just set the latest ConTeXt up, and the first thing I tested was
the footnote bug (footnote going to the next page).
The attached file show the error. The proposed patch (proposed
quite some time ago) does not fix the problem.
Please allow me to insist on this problem. It is one of the
reasons why people choose one system or the other (this happens at
least with WordPerfect against Word: Word has a similar problem,
WordPerdperfect doesn't).
--
Giuseppe "Oblomov" Bilotta
[-- Attachment #2: footbug2.tex --]
[-- Type: application/octet-stream, Size: 678 bytes --]
\setupindenting[medium]
\starttext
\input knuth
\blank
\input zapf
\blank
\startcolumns
\input tufte\footnote{This was a text from Tufte. Let's now get
this footnote a little longer, so as to trigger the second bug. We
need at least two lines, maybe three of four\dots}
\stopcolumns
\blank
\input tufte\footnote{\input zapf }
\blank
\input knuth
\page[yes]
\input knuth
\blank
\input zapf
\blank
\startcolumns
\input tufte
\stopcolumns
\blank
You don't need another footnote to trigger the bug: just
enough text to push the last line of the problematic
paragraph to the end of the page.
\input tufte\footnote{\input zapf }
\blank
\input knuth
\stoptext
[-- Attachment #3: footpatch.tex --]
[-- Type: application/octet-stream, Size: 158 bytes --]
\def\synchronizefootnotes%
{\ifvoid\footins\else\insert\footins{\unvbox\footins}\fi}
\appendtoks \synchronizefootnotes \to \everypar
\input footbug2.tex
reply other threads:[~2001-07-13 15:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=714073312.20010713173540@bigfoot.com \
--to=bourbaki@bigfoot.com \
/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).