From: "Pablo Rodríguez" <oinos@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: space between footnotes
Date: Sun, 03 Jun 2012 01:17:47 +0200 [thread overview]
Message-ID: <4FCA9F1B.7080602@web.de> (raw)
In-Reply-To: <B31C8901-44D3-42F2-82CE-8056B23236C4@googlemail.com>
On 02/06/12 17:03, Wolfgang Schuster wrote:
> Am 02.06.2012 um 16:17 schrieb Pablo Rodríguez:
>> On 02/06/12 15:42, Philipp Gesang wrote:
>>> [...]
>>> In the latter case it is only meaningful for paragraph-style
>>> (serried) footnotes:
>>> ········································································
>>> \setupnote[footnote][
>>> paragraph=yes,
>>> inbetween=\hskip 5em,
>>> ]
>>> \starttext
>>> \dorecurse{5}{foot\footnote{note}}
>>> \stoptext
>>> ········································································
>>> Unfortunately with ordinary settings it is ignored altogether.
>>
>> If this isn't a bug, I wonder whether this shouldn't be implemented. It
>> makes sense.
>
> Add \setupnotation[footnote][display=no] and the example will work.
Many thanks for your reply, Wolfgang.
If I didn't get your explanation wrong, this example should work:
\setupnote[footnote][inbetween=\blank]
\setupnotation[footnote][display=no]
\starttext
\dorecurse{5}{foot\footnote{note}}
\stoptext
I'm afraid it doesn't. What is wrong here?
>>> The alternative you are looking for might be to locally set a
>>> different parskip for the footnote inserts:
>>
>> It adds the space also before or after the first or last one (I guess
>> this is the way these options should work).
>
> It’s a bug because in the following example even the space between the notes is too big,
> it should be 5mm but actually it’s 10mm.
>
> \setupnotation[footnote][before={\blank[5mm]},after={\blank[5mm]}]
Are you sure that this is buggy? If each note should have 5mm before and
after it, I think the right space between notes should be 10mm (5mm
after the previous note plus 5mm before the next note). Maybe I'm being
too simplistic, but I think it's right.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-06-02 23:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 19:51 Pablo Rodríguez
2012-06-02 7:27 ` Philipp Gesang
2012-06-02 13:25 ` Pablo Rodríguez
2012-06-02 13:38 ` Wolfgang Schuster
2012-06-02 14:02 ` Pablo Rodríguez
2012-06-02 13:42 ` Philipp Gesang
2012-06-02 14:17 ` Pablo Rodríguez
2012-06-02 15:03 ` Wolfgang Schuster
2012-06-02 23:17 ` Pablo Rodríguez [this message]
2012-06-03 8:26 ` Wolfgang Schuster
2012-06-03 13:26 ` Alan Bowen
2012-06-03 13:54 ` Wolfgang Schuster
2012-06-03 15:52 ` Alan Bowen
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=4FCA9F1B.7080602@web.de \
--to=oinos@web.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).