ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Indentation after margin float with caption
Date: Tue, 6 Sep 2016 15:57:41 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.20.1609061547450.10946@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <57CF17CE.1030502@gmail.com>

On Tue, 6 Sep 2016, Wolfgang Schuster wrote:

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

In the move to MkII to MkIV, there have been many changes that are not 
backward compatible. So, I am not in favor of adding a new key when we 
already have an indentnext key just for the sake of backward 
compatibility.

It will be nice if all the location alternatives in setupfloat honored the 
indentnext key. It is really awkaward that when indentnext=yes (or auto) 
location=top and location=bottom behave differently.

If backward compatibility is really important, we could add a mechanism to 
control the indentnext key for each location; but that would add too much 
complexity to the code for very little benefit. If one wants to mix floats 
that indent the next paragraph with floats that don't indent the next 
paragraph, it is possible to define different types of floats (with the 
same counters and lists) such that indentnext=yes for one type and 
indentnext=no for the other.

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

  reply	other threads:[~2016-09-06 19:57 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
2016-09-06 19:57     ` Aditya Mahajan [this message]
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=alpine.LNX.2.20.1609061547450.10946@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).