From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Indentation after margin float with caption
Date: Tue, 06 Sep 2016 21:23:58 +0200 [thread overview]
Message-ID: <57CF17CE.1030502@gmail.com> (raw)
In-Reply-To: <CAHy-LL95-T6dsqYOOvAiJ1_qMyZW1z91DczteCAAR5BxH2LQxQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1413 bytes --]
> Mikael P. Sundqvist <mailto:mickep@gmail.com>
> 6. September 2016 um 21:07
>
> 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
When backwards compatiblity is a reason for not changing this adding a
hook can be solution, e.g.
-\def\page_one_place_float_auto {\page_one_place_float_otherwise}
+\def\page_one_place_float_auto
{\page_one_place_float_otherwise\rootfloatparameter\c!next}
which can be used with \setupfloat[next=\indentation]
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2570 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:23 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
2016-09-06 19:23 ` Wolfgang Schuster [this message]
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=57CF17CE.1030502@gmail.com \
--to=schuster.wolfgang@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).