From: Alan Braslau <braslau.list@comcast.net>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setupfloatcaption align=
Date: Thu, 12 Apr 2018 10:56:01 -0600 [thread overview]
Message-ID: <20180412105601.1508b219@poo.hsd1.co.comcast.net> (raw)
In-Reply-To: <72381e97-8d72-ab82-acce-4f8a3d0c3528@xs4all.nl>
On Thu, 12 Apr 2018 18:11:08 +0200
Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 4/12/2018 5:54 PM, Alan Braslau wrote:
> > On Thu, 12 Apr 2018 10:09:58 +0200
> > Hans Hagen <j.hagen@xs4all.nl> wrote:
> >
> >> tolerance in text/par alignment is just that: adding tolerance and
> >> it is bound to align and it only kicks in in par building and
> >> there is not always a par involved
> >
> > Why does a float caption not build a paragraph? Does a \framed
> > sometimes not build a paragraph?
>
> it's not framed ... framed is advanced in the sense that it can
> analyze the build paragraph for the natural width
>
> float captions look at the size oif the float plus some overshoot ...
> unrelated mechanisms
Maybe, a float caption *should* be a frame?
And if it isn't, I am asking why would a caption not be treated as a
paragraph?
> >> location has to do with the placement and float as a whole and
> >> there tolerance has to deal with snapping
> >
> > Not float location but \setupfloatcaption location (i.e. top,
> > bottom, ...): relative location of the float caption.
>
> those are locations of the caption relative to the float
That is what I have been trying to say!
So how does "tolerance" come into play?
Alan
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-04-12 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 20:13 Alan Braslau
2018-04-11 20:41 ` Hans Hagen
2018-04-11 20:51 ` Alan Braslau
2018-04-12 8:09 ` Hans Hagen
2018-04-12 15:54 ` Alan Braslau
2018-04-12 16:11 ` Hans Hagen
2018-04-12 16:56 ` Alan Braslau [this message]
2018-04-12 16:59 ` Hans Hagen
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=20180412105601.1508b219@poo.hsd1.co.comcast.net \
--to=braslau.list@comcast.net \
--cc=j.hagen@xs4all.nl \
--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).