From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: Footnote in TABLE isn't rendered anywhere
Date: Mon, 21 Aug 2017 19:29:14 +0200 [thread overview]
Message-ID: <ff243cd0-69e4-17f3-2f68-77e9b5739227@gmx.es> (raw)
In-Reply-To: <CADs1X49MkieMfSZ6C5SP6pH7-7Qw5WKekddfE65dHhzOdgRpAw@mail.gmail.com>
On 08/21/2017 05:57 AM, Brian Ballsun-Stanton wrote:
> Hi Alan,
>
> I'm sorry I'm... fuzzy today.
>
> Are you asking me to add: "\automigrateinserts" to the wiki example as a
> different mechanism to demonstrate from earlier in this thread,
> proposing it as a different solution this problem, and/or proposing it
> as a solution to the "not rendering inside the wiki ConTeXt version?
Hi Brian,
I wonder how you may define fuzziness, but your question proposes three
well-defined options ;-).
As far as I understand it, Alan was simply proposing a way to get the
footnote out of the table. I mean, to have a footnote from a table.
This is already solved with \postponenotes and \flushnotes.
The problem with the wiki is that you don’t have standard footnotes.
Because having a full page wouldn’t be helpful in most cases.
> My apologies for misunderstanding.
I hope I’m not getting Alan’s point wrong.
Just in case it helps,
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-08-21 17:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 15:00 Andreas Schneider
2017-07-05 18:51 ` Pablo Rodriguez
2017-07-06 7:41 ` Andreas Schneider
2017-07-08 13:17 ` Mathias Schickel
2017-07-10 10:50 ` Pablo Rodriguez
2017-07-10 18:23 ` Mathias Schickel
2017-07-12 16:30 ` Mathias Schickel
2017-07-12 17:05 ` Hans Hagen
2017-07-15 19:11 ` Alan Braslau
2017-07-15 19:55 ` Hans Hagen
2017-07-16 9:38 ` Mathias Schickel
2017-07-12 23:18 ` Aditya Mahajan
2017-07-14 15:22 ` Mathias Schickel
2017-07-15 16:07 ` Pablo Rodriguez
2017-07-15 18:07 ` Mathias Schickel
2017-07-15 19:03 ` Pablo Rodriguez
2017-08-21 1:15 ` Brian Ballsun-Stanton
2017-08-21 2:35 ` Alan Braslau
2017-08-21 3:57 ` Brian Ballsun-Stanton
2017-08-21 17:29 ` Pablo Rodriguez [this message]
2017-08-21 17:21 ` Pablo Rodriguez
2017-08-22 1:17 ` Brian Ballsun-Stanton
2017-08-22 8:17 ` Pablo Rodriguez
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=ff243cd0-69e4-17f3-2f68-77e9b5739227@gmx.es \
--to=oinos@gmx.es \
--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).