From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: "Idris Samawi Hamid ادريس سماوي حامد via ntg-context"
<ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: Forbid footnotes from splitting across pages
Date: Wed, 3 Aug 2022 15:47:05 +0200 [thread overview]
Message-ID: <68956620-80a4-32c3-06ed-8f42669065de@gmx.es> (raw)
In-Reply-To: <op.1qavyurgejo439@desktop-mt1m160>
On 8/3/22 03:05, Idris Samawi Hamid ادريس سماوي حامد via ntg-context wrote:
> Dear gang,
>
> Objectives:
>
> i) Prevent footnotes from splitting across a page or pagebreak
Dear Idris,
I wonder whether a \framed[offset=none, frame=off, width=\textwidth]
would make sense here.
At least, it would prevent page breaks.
> ii) Make sure that the footnote reference number in the main text is
> always on the same page as the footnote.
\setupnote[footnote][split=verystrict, scope=text] might help here.
But it cannot achieve what is practically impossible:
\setupnote[footnote][split=verystrict, scope=text]
\starttext
\dorecurse{25}
{ab cd ef\footnote{\input{knuth}}}
\stoptext
I know that this depends from the publisher, but in these cases endnotes
are a way more viable option.
Just in case it might help,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-08-03 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 1:05 Idris Samawi Hamid ادريس سماوي حامد via ntg-context
2022-08-03 13:47 ` Pablo Rodriguez via ntg-context [this message]
2022-08-03 14:21 ` Hamid,Idris via ntg-context
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=68956620-80a4-32c3-06ed-8f42669065de@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).