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: Wed, 11 Apr 2018 14:51:29 -0600 [thread overview]
Message-ID: <20180411145129.569b49f2@poo.hsd1.co.comcast.net> (raw)
In-Reply-To: <67f119fe-ea26-1a9e-89e7-d8e6eb3f3d4f@xs4all.nl>
On Wed, 11 Apr 2018 22:41:41 +0200
Hans Hagen <j.hagen@xs4all.nl> wrote:
> > Question2: What is going on with \setupfloatcaption ?
> some heuristics to determine the best width ... so that you still get
> a reasonable caption with very narrow figures and not excessive
> captions with too wide figures and when possible a one liner ... it's
> no problem adding some variants (there are some dimensions that can
> be set already) but the current mechanism is not going to change
Hans, I did not ask about funny behavior with captions in general, just
about the handling of key=value for align and with location=.
(And no MWE needed, as I am asking a question about the interface.)
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-11 20:51 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 [this message]
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
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=20180411145129.569b49f2@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).