From: "Huseyin Özoguz" <h.oezoguz@mmnetz.de>
To: Alan Braslau <braslau.list@comcast.net>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Place footnote after reference
Date: Mon, 22 Jul 2019 20:46:10 +0200 [thread overview]
Message-ID: <36a043a7-7777-644a-f8db-f110f03435c6@mmnetz.de> (raw)
In-Reply-To: <20190722111410.3ee1769c@poo.hsd1.co.comcast.net>
> So why not place footnotes in a (sufficiently large) reserved bottom
> space? The typeset text area would then be uniform across all pages and
> notes would appear where needed.
Would be possibe in some cases, but not in mine: I have many small
footnones, only a few words, and some very long with several lines. With
your solution I would waste 50%+ of the area or - as an alternative - I
had to split the long footnotes across several pages and their
footnote-areas. Actually that might be an interesting workaround ... I
will try it, but it would cost still a lot of space and pages.
Huseyin
Huseyin Özoguz
E-Mail: h.oezoguz@mmnetz.de
Am 22.07.2019 um 19:14 schrieb Alan Braslau:
> On Mon, 22 Jul 2019 18:34:34 +0200
> Huseyin Özoguz <h.oezoguz@mmnetz.de> wrote:
>
>> The problem is, that Context (or Tex) skips lines, which is poor
>> typesetting, too many even than necessary in some cases, and that is
>> not suitable. Endnotes are no solutions aswell, I need footnotes. So
>> the solution to have reference and footnote not on the same page
>> seems the least bad workaround, if possible at all.
> So why not place footnotes in a (sufficiently large) reserved bottom
> space? The typeset text area would then be uniform across all pages and
> notes would appear where needed.
>
> 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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-07-22 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-07-23 7:41 ` Taco Hoekwater
-- strict thread matches above, loose matches on Subject: below --
2019-07-23 8:48 Huseyin Özoguz
2019-07-22 6:38 Huseyin Özoguz
2019-07-22 14:27 ` Denis Maier
2019-07-22 14:37 ` Alan Braslau
2019-07-22 15:00 ` Taco Hoekwater
2019-07-22 18:01 ` Wolfgang Schuster
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=36a043a7-7777-644a-f8db-f110f03435c6@mmnetz.de \
--to=h.oezoguz@mmnetz.de \
--cc=braslau.list@comcast.net \
--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).