ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau <braslau.list@comcast.net>
To: Denis Maier <maier.de@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Place footnote after reference
Date: Mon, 22 Jul 2019 08:37:48 -0600	[thread overview]
Message-ID: <20190722083748.3fd0ef88@poo.hsd1.co.comcast.net> (raw)
In-Reply-To: <CAMXdeGFseiqsLPD=6zX0Wde2bVGphi7+m1x8581cBbxyUnezHA@mail.gmail.com>

On Mon, 22 Jul 2019 16:27:45 +0200
Denis Maier <maier.de@gmail.com> wrote:

> llI don't know a solution for this, but would be very interested.
> With LaTeX you can use the `atbegshi`-package that gives you a
> command ` \AtBeginShipoutNext`:
> 
> ```
> \footnotemark
> \clearpage
> \AtBeginShipoutNext{\footnotetext{Text.}}
> ```
> 
> This only works for individual footnotes, but it's already quite
> useful. Is there something similar for ConTeXt?
> I can think of at least three situations:
> 
> 1. Put footnote text to the next page for a single footnote.
> 2. Allow footnote text on next page for all footnotes.
> 3. Allow footnote text on next page of a double page spread  for all
> footnotes.
> 
> Best,
> Denis
> 
> 
> 
> 
> 
> 
> Am Mo., 22. Juli 2019 um 08:43 Uhr schrieb Huseyin Özoguz <
> h.oezoguz@mmnetz.de>:
> 
> > Hello,
> >
> > ConText seems to try to place the footnote on the same page as the
> > footenotereference. See this example:
> >
> > \showgrid
> > \starttext
> > \input tufte
> > \input tufte \footnote{Footnote 1}
> > \input tufte
> > \input tufte \dorecurse{35}{Blub or what }\footnote{Footnote 2}
> > \input tufte
> > \stoptext
> >
> > But that results into one (or two?) fewer line on the first page.
> >
> > Is there a possibility to implement the following rule? -> NEVER
> > move lines onto the next page to achieve footnote and reference
> > beging on the same page. If necessary set the footnote on the next
> > page, after the reference.
> >
> > Or would you suggest a better solution? I have a book with
> > grid=yes, so the default-setting is not suitable.
> >
> > Thanks
> > Huseyin


I do not know the details, but take a look at the following keywords
(which do the *opposite* of what you are seeking):

\setupnote
  [footnote]
  [split=verystrict,scope=page]

Alan
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-07-22 14:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22  6:38 Huseyin Özoguz
2019-07-22 14:27 ` Denis Maier
2019-07-22 14:37   ` Alan Braslau [this message]
2019-07-22 15:00     ` Taco Hoekwater
2019-07-22 18:01     ` Wolfgang Schuster
2019-07-22 16:34 Huseyin Özoguz
2019-07-22 17:11 ` Rik Kabel
2019-07-22 17:14 ` Alan Braslau
2019-07-22 18:46   ` Huseyin Özoguz
2019-07-23  7:41 ` Taco Hoekwater
2019-07-23  8:48 Huseyin Özoguz

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=20190722083748.3fd0ef88@poo.hsd1.co.comcast.net \
    --to=braslau.list@comcast.net \
    --cc=maier.de@gmail.com \
    --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).