From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: bug in paragraph footnotes?
Date: Thu, 12 Mar 2015 22:39:15 +0100 [thread overview]
Message-ID: <55020783.10309@wxs.nl> (raw)
In-Reply-To: <5501C467.1040706@gmx.es>
On 3/12/2015 5:52 PM, Pablo Rodriguez wrote:
> Dear list,
>
> I’m afraid that the following sample shows a bug in interline space for
> footnotes:
>
> \startsetups[setups:footnote]
> \setupinterlinespace[line=6ex]
> \stopsetups
>
> \setupnotation[footnote][alternative=serried]
> \setupnote[footnote][paragraph=yes, setups=setups:footnote]
>
> \starttext
> \dorecurse{2}{These are footnotes\footnote{\input knuth}. }
> \stoptext
>
> Could anyone confirm it or explain me what I’m missing?
these paragraph notes are kind of special as we need to cheat a bit to
let tex handle them right as inserts (see the texbook)
i'll send you a patch offline but no guaranteed
(some day i'll redo this a bit in a more mkiv-isch way)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2015-03-12 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 16:52 Pablo Rodriguez
2015-03-12 21:39 ` Hans Hagen [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=55020783.10309@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).