From: "Mikael P. Sundqvist" <mickep@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Indentation after margin float with caption
Date: Tue, 6 Sep 2016 21:07:18 +0200 [thread overview]
Message-ID: <CAHy-LL95-T6dsqYOOvAiJ1_qMyZW1z91DczteCAAR5BxH2LQxQ@mail.gmail.com> (raw)
In-Reply-To: <CAHy-LL_yGBC5Or8u_4YJS-AftdU5+BTtDS+toWp5bbPmoAy7XQ@mail.gmail.com>
On Fri, Sep 2, 2016 at 9:47 AM, Mikael P. Sundqvist <mickep@gmail.com> wrote:
> Dear list,
>
> is it possible to have a margin figure with caption, and automatically
> have the next paragraph indented? Look at the example below (pdf
> result attached). If I add the none argument to the float, then the
> next paragraph is indented. Otherwise not. Is it a bug or a feature?
>
> Best regards, Mikael
>
> \setupindenting[yes,medium]
>
> \setupfloats[indentafter=yes]
>
> \starttext
>
> \input tufte
>
> \placefigure[outermargin,middle]{}{\blackrule[width=1cm,height=1cm]}
>
> This should be indented, but it is not! \input tufte
>
> \input tufte
>
> \placefigure[outermargin,middle,none]{}{\blackrule[width=1cm,height=1cm]}
>
> This should be indented, and it is! But I want the caption. \input tufte
> \stoptext
Dear all,
since I got no answer here I cross posted on stackexchange (see
http://tex.stackexchange.com/q/328147/52406). Now, I got a solution to
this from Aditya. It seems that it is not yet clear to me (or Aditya,
as far as I understand from the reply) which float placements that
respects the \setupfloats[indentnext=yes] and which not. Or more
importantly, why.
To make this email thread more complete, the solution of Aditya adds
\unprotect
\def\page_one_place_float_auto
{\page_one_place_float_otherwise\nonoindentation}
\def\page_one_place_float_bottom
{\page_one_place_float_otherwise\nonoindentation}
\def\page_one_place_float_margin
{\page_margin_blocks_process_float\nonoindentation}
\def\page_one_place_float_leftmargin
{\page_one_place_float_side_indeed\page_sides_process_float_leftmargin\nonoindentation}
\def\page_one_place_float_rightmargin{\page_one_place_float_side_indeed\page_sides_process_float_rightmargin\nonoindentation}
\protect
(this kind of solution was also suggested in 2011 in an old thread,
see https://mailman.ntg.nl/pipermail/ntg-context/2011/058152.html)
/Mikael
PS I have a couple of more questions on the list that has not got any
response. I hope you don't mind me cross posting on stackexchange in
these cases.
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-09-06 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 7:47 Mikael P. Sundqvist
2016-09-06 19:07 ` Mikael P. Sundqvist [this message]
2016-09-06 19:23 ` Wolfgang Schuster
2016-09-06 19:57 ` Aditya Mahajan
2016-09-07 11:25 ` Aditya Mahajan
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=CAHy-LL95-T6dsqYOOvAiJ1_qMyZW1z91DczteCAAR5BxH2LQxQ@mail.gmail.com \
--to=mickep@gmail.com \
--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).