From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	HTML_MESSAGE,MAILING_LIST_MULTI,NICE_REPLY_A,T_SCC_BODY_TEXT_LINE,
	URIBL_SBL_A autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 30546 invoked from network); 21 May 2023 13:18:06 -0000
Received: from zapf.ntg.nl (5.39.185.232)
  by inbox.vuxu.org with ESMTPUTF8; 21 May 2023 13:18:06 -0000
Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id AFCB31C2F80;
	Sun, 21 May 2023 15:17:44 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl
Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3LKSE6bsxQOD; Sun, 21 May 2023 15:17:43 +0200 (CEST)
Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 21CB11C31A7;
	Sun, 21 May 2023 15:17:43 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 95F4B1C31A7
 for <ntg-context@ntg.nl>; Sun, 21 May 2023 15:17:41 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl
Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id kReJ2dG0JBP7 for <ntg-context@ntg.nl>;
 Sun, 21 May 2023 15:17:40 +0200 (CEST)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.218.45;
 helo=mail-ej1-f45.google.com; envelope-from=wolfgang.schuster.lists@gmail.com;
 receiver=<UNKNOWN> 
Received: from mail-ej1-f45.google.com (mail-ej1-f45.google.com
 [209.85.218.45])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 8F0331C2F80
 for <ntg-context@ntg.nl>; Sun, 21 May 2023 15:17:40 +0200 (CEST)
Received: by mail-ej1-f45.google.com with SMTP id
 a640c23a62f3a-96aae59bbd6so943925566b.3
 for <ntg-context@ntg.nl>; Sun, 21 May 2023 06:17:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20221208; t=1684675060; x=1687267060;
 h=content-language:in-reply-to:mime-version:user-agent:date
 :message-id:from:references:to:subject:from:to:cc:subject:date
 :message-id:reply-to;
 bh=EtM6hsy6AlY5YiAQjnkiQMk1fj+mQTc6uxHTyZ5mnRg=;
 b=mNJcPBHcmMn+9tFsd2tW0OEku8H/puwQr5NPUY8INuSot3S81ChiT3n0SFP5MMNKqA
 HfgLYQwZbP3YjAaPivbJLWJM5K0/W7bqPozVkYwUM3h4MDdH2p5D6+O7sLRegIJ1ZKKs
 MLQ6adaYErmvnZdE3v4sm6JCyiYLsIdHF7KZpGbPD6y0tX1KL3gAcRI89G0A+QcQ2rHO
 S6jnUkPjUMaGmmKDH8Ef5y3EVw52YSM4VNY2+pYK4X1KKH6cza9VwPtWo9IDGEvl80e2
 E29lduOkXapEFHLxiOXzZTcqMtDfHiHkCPyJo+SC53uSBuH/TTd9A/wzZ+ml4T6fKS3y
 ZRvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1684675060; x=1687267060;
 h=content-language:in-reply-to:mime-version:user-agent:date
 :message-id:from:references:to:subject:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=EtM6hsy6AlY5YiAQjnkiQMk1fj+mQTc6uxHTyZ5mnRg=;
 b=i6mMTaN948gmGLLk3GdAriQJhiG3LQqLvCRPSjL3vp3C/TydR6XeOVI9UVuYFFB5HY
 lI6qgfkIjF87EiNLFBAYACj93blWz0Z6gDvbwku1PjzzsPi8gx200PvO6uxf3n6YDX7z
 kpiGoDlzuXa/T2xdc+boOpGw3eesWYjBbyNym6G+xXwJjU5ufmSC4f8MSHc5bXSOsACS
 E571sVLy3cpdHnM8DJQ7n8Dgd5AnxcNXWT4+vMy98YQusvtCOYgKCBCOO6X+vXico4MF
 LOtkPTOXIFPao/jhdC9X5TVmgfzMTFAIksMuFhekdjGP3Qk0B71+tvAPeSLv8nXyPs3z
 rFlA==
X-Gm-Message-State: AC+VfDx9+1tFip7+NQ+EXtGT9ybbaibPXOfDh6zohQhzQdk5BaLrmGKA
 J8CSSzhj6Tj6InyekJrFyXnLyq7TRRc=
X-Google-Smtp-Source: ACHHUZ5pCOBf1iBuvna6yM3imxJP3b4buiRVb34lzv46yx+cvXRF/Xeu2gVDgOtuImPFZCmTzSaP3A==
X-Received: by 2002:a17:907:6d1e:b0:953:57a1:55e1 with SMTP id
 sa30-20020a1709076d1e00b0095357a155e1mr7203200ejc.62.1684675059982; 
 Sun, 21 May 2023 06:17:39 -0700 (PDT)
Received: from ?IPv6:2a02:810d:a8bf:fe08::c3b6? ([2a02:810d:a8bf:fe08::c3b6])
 by smtp.gmail.com with ESMTPSA id
 c2-20020aa7c982000000b0051056dc47e0sm1852410edt.8.2023.05.21.06.17.39
 for <ntg-context@ntg.nl>
 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
 Sun, 21 May 2023 06:17:39 -0700 (PDT)
To: Joel via ntg-context <ntg-context@ntg.nl>
References: <184739469.220649.1684633669751.ref@mail.yahoo.com>
 <184739469.220649.1684633669751@mail.yahoo.com>
 <2003843342.269294.1684674719570@mail.yahoo.com>
Message-ID: <a5efce38-8f93-84e8-f8a7-222af546026d@gmail.com>
Date: Sun, 21 May 2023 15:17:37 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 PostboxApp/7.0.60
MIME-Version: 1.0
In-Reply-To: <2003843342.269294.1684674719570@mail.yahoo.com>
Content-Language: en-US
Subject: Re: [NTG-context] How to really force figure to appear "here"?
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.38
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Content-Type: multipart/mixed; boundary="===============2437585128780368980=="
Errors-To: ntg-context-bounces@ntg.nl
Sender: "ntg-context" <ntg-context-bounces@ntg.nl>

This is a multi-part message in MIME format.
--===============2437585128780368980==
Content-Type: multipart/alternative;
 boundary="------------C941949678C66BF5A68062C3"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------C941949678C66BF5A68062C3
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Joel via ntg-context schrieb am 21.05.2023 um 15:11:
> 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]
>     }

Get rid of the here keyword and use only force, you can't use both at 
the same time
and one gets ignored (depends whatever is first checked in the float 
mechanism).

\placefigure[force]{caption}{\externalfigure[1.jpg][width=\textwidth]}

Wolfgang


--------------C941949678C66BF5A68062C3
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html theme="default-light" iconset="color"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body text="#000000"><span>Joel via ntg-context schrieb am 
21.05.2023 um 15:11:</span><br>
<blockquote type="cite" 
cite="mid:2003843342.269294.1684674719570@mail.yahoo.com">
  <meta http-equiv="content-type" content="text/html; charset=utf-8">
  <div class="ydp5f8df172yahoo-style-wrap" style="font-family:Helvetica 
Neue, Helvetica, Arial, sans-serif;font-size:10px;">
        <div dir="ltr" data-setdir="false">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.</div><div
 dir="ltr" data-setdir="false"><br></div><div dir="ltr" 
data-setdir="false"><div>\starttext<br>    \input knuth<br>    \input 
knuth<br><br>    {\boldface This is a short note about the picture. It 
should appear right after this.}<br>   
 \placefigure[here,force]{caption}{<br>       
 \externalfigure[1.jpg][width=\textwidth]<br>    }<br>
</div></div></div>
</blockquote>
<br>
Get rid of the here keyword and use only force, you can't use both at 
the same time<br>
and one gets ignored (depends whatever is first checked in the float 
mechanism).<br>
<br>
\placefigure[force]{caption}{\externalfigure[1.jpg][width=\textwidth]}<br>
<br>
Wolfgang<br>
<br>
</body></html>

--------------C941949678C66BF5A68062C3--

--===============2437585128780368980==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___________________________________________________________________________________
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
___________________________________________________________________________________

--===============2437585128780368980==--