From: Joel via ntg-context <ntg-context@ntg.nl>
To: Joel via ntg-context <ntg-context@ntg.nl>
Cc: Joel <uaru99@yahoo.com>
Subject: Re: [NTG-context] How to really force figure to appear "here"?
Date: Sun, 21 May 2023 13:11:59 +0000 (UTC) [thread overview]
Message-ID: <2003843342.269294.1684674719570@mail.yahoo.com> (raw)
In-Reply-To: <184739469.220649.1684633669751@mail.yahoo.com>
[-- Attachment #1.1: Type: text/plain, Size: 1794 bytes --]
Here, I've created an example that does just that. I want the figure to appear immediately after the bold text. Even if a lot of whitespace is placed and the figure appears on the next page, that is fine, but I don't want the next group of text to appear until *after* the figure. This is really confusing my readers.
\starttext
\input knuth
\input knuth
{\boldface This is a short note about the picture. It should appear right after this.}
\placefigure[here,force]{caption}{
\externalfigure[1.jpg][width=\textwidth]
}
\input knuth
\input knuth
\input knuth
\input knuth
\input knuth
\input knuth
\stoptext
--Joel
On Saturday, May 20, 2023 at 07:49:45 PM MDT, Joel via ntg-context <ntg-context@ntg.nl> wrote:
I have been using \placefigure[here, force] to place some graphics, but its instead showing other text from the next section, then the picture. In testing, this is causing readers to be confused, as they expect to see a picture, but its somehow appearing two pages later. I don't care it it requires a huge blank area on the page before it, how can I make it so any text after \placefigure[here, force] doesn't appear before the figure?
--Joel
___________________________________________________________________________________
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
___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 3605 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
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:[~2023-05-21 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <184739469.220649.1684633669751.ref@mail.yahoo.com>
2023-05-21 1:47 ` Joel via ntg-context
2023-05-21 6:35 ` Mikael Sundqvist via ntg-context
2023-05-21 13:11 ` Joel via ntg-context [this message]
2023-05-21 13:17 ` Wolfgang Schuster via ntg-context
2023-05-24 14:36 ` Henning Hraban Ramm 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=2003843342.269294.1684674719570@mail.yahoo.com \
--to=ntg-context@ntg.nl \
--cc=uaru99@yahoo.com \
/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).