ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: Alan Braslau <braslau.list@comcast.net>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Footnote in TABLE isn't rendered anywhere
Date: Sat, 15 Jul 2017 21:55:40 +0200	[thread overview]
Message-ID: <9791ffd8-ffac-fc28-0bbc-1b4a4e9dcb48@wxs.nl> (raw)
In-Reply-To: <20170715131152.1efffd70@zoo.hsd1.co.comcast.net>

On 7/15/2017 9:11 PM, Alan Braslau wrote:
> On Wed, 12 Jul 2017 19:05:26 +0200
> Hans Hagen <pragma@wxs.nl> wrote:
> 
>> best play with textbackgrounds
>>
>> \starttext
>>
>> \starttextbackground
>> \dorecurse{10}{test\footnote{tufte}: \input tufte\par}
>> \stoptextbackground
>>
>> \stoptext
>>
> 
> I have found the following to be necessary when using textbackground,
> especially when backgrounds cross page boundaries:
> 
> \setnewconstant\kindofpagetextareas\plusone
> % partial page. HH: low level, no high level switch (yet)
> 
> Maybe Hans can explain this?
Because it's an option (with no parameter yet .. not sure where/how to 
configure it; for floats one can do it per float)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2017-07-15 19:55 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 [this message]
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
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=9791ffd8-ffac-fc28-0bbc-1b4a4e9dcb48@wxs.nl \
    --to=pragma@wxs.nl \
    --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).