ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Brooks Moses <bmoses@stanford.edu>
Subject: A number of footnote bugs.
Date: Sun, 04 Sep 2005 13:53:39 -0700	[thread overview]
Message-ID: <4.3.1.2.20050904134231.02666398@cits1.stanford.edu> (raw)

In playing with footnotes on the Wiki, I've come across a number of bugs, 
as well as the questions I mentioned earlier.

Consider the following example text:

   \setupfootnotes[n=3]
   \starttext
    \strut\vfill  % A hack to shorten the page, for Wiki use.
    This\footnote[footA](Or that\footnote{Or the other.}, if you prefer.}
    is a sentence with a footnote\footnote{Actually, two footnotes; this
    one and \in{footnote}[footA] on \at{page}[footA], denoted by
    \note[footA].}.
   \stoptext

This illustrates the following bugs:

1.) Without the \setupfootnotes line, this leaves a vertical space of about 
one blank line between the bottom of the text and the footnote 
separator.  With the \setupfootnotes line, we see that this space is 
proportional to n -- for n=3, it leaves three blank lines.

2.) The columns are ill-spaced in the default case; the footnote markers 
are closer to the column on their left than they are to the column they 
belong to.

3.) Footnotes in footnotes do not produce their numbers in the correct 
order, though they do set the footnotes in the proper order on the bottom 
of the page.  Specifically, the second footnote in the text is 
(incorrectly) numbered 3 rather than 2, but it is (correctly) placed before 
the footnote on the footnote.

4.) According to the comments on lines 63-65 of core-not.tex, setting n=0 
should set the footnotes in a continuous paragraph, using an algorithm from 
the TeXbook.  This does not work at all; the footnotes are set in a single 
column but with a smaller interline space.

Hans, are any of these readily fixable?

- Brooks

                 reply	other threads:[~2005-09-04 20:53 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=4.3.1.2.20050904134231.02666398@cits1.stanford.edu \
    --to=bmoses@stanford.edu \
    --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).