From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: \setupfooter[color=red]: red color spills with float over next page
Date: Sun, 4 Dec 2016 11:42:19 +0100 [thread overview]
Message-ID: <974002c0-d7f9-fc67-cef0-bbcab7c3341e@wxs.nl> (raw)
In-Reply-To: <1081CA10-0C78-47B0-86DC-C17BDF04FEBE@gmail.com>
On 12/4/2016 4:05 AM, Benjamin Buchmuller wrote:
> When I have
>
> \setupfooter[color=red, style=bold] (same goes with \setupfooter[style=red])
>
> and a
>
> tex text text
>
> % <<<< page breaks here after typesetting >>>>
>
> \startplacefigure[
> %location=force, % no matter what I do here
> title={Caption.}
> ]
> … something …
> \stopplacefigure
>
> other text
>
> that is moved to the following page as first object, the entire page including the figure’s rulers, caption, and the regular text prints in red (but not bold!?) when I incorporate the file via \component … into my project, but not when I typeset from within \startcomponent … \stopcomponent.
>
> Since “bold” does not seem to float the same way, I guess it is related to color handling at page breaks somehow.
>
> I already tried to \setupfloats[before=\strut] to “force” black bodyfont right before the figure (at least this is what I intended to do), but did not work.
>
> I’m sorry not to be able to provide a more elaborate minimal example asserting the exact conditionals of this behaviour at the moment as I need to hand in a report next week. Probably the footers have to go black this time.
>
> Any suggestions?
not many as i really need an example
you can try
\setupfootertexts[\strut{\red foo}\strut}
instead
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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-12-04 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 3:05 Benjamin Buchmuller
2016-12-04 10:42 ` Hans Hagen [this message]
[not found] <mailman.0.1480849201.24823.ntg-context@ntg.nl>
2016-12-04 19:07 ` Benjamin Buchmuller
2016-12-18 22:00 Benjamin Buchmuller
2016-12-18 22:34 ` Pablo Rodriguez
2016-12-19 9:40 ` Hans Hagen
2016-12-19 16:00 Benjamin Buchmuller
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=974002c0-d7f9-fc67-cef0-bbcab7c3341e@wxs.nl \
--to=pragma@wxs.nl \
--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).