From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: Page break with placement of a figure at the bottom of the page
Date: Sat, 12 Nov 2022 12:28:42 +0100 [thread overview]
Message-ID: <a8704411-7252-9afe-1af2-df59fc3abdb9@gmx.es> (raw)
In-Reply-To: <D44D5B15-D384-4569-A8F4-CB791482AE38@scorecrow.com>
On 11/11/22 21:58, Bruce Horrocks via ntg-context wrote:
>> On 10 Nov 2022, at 17:06, Fabrice Couvreur via ntg-context wrote:
>>
>> Hi,
>> Sorry to come back to you, but it seems to me that there is enough space here.
>> Fabrice
>
> For some reason your PNG images came through in extremely low
> resolution. Without having the ConTeXt source it's hard to say for sure
> what's happening - for example, I would have expected the text on the
> second page to be at the bottom of the first even if there wasn't room
> for the image - because that was what was happening in your first example.
Hi Fabrice and Bruce,
I agree that the source would be helpful to say what may be hard for
ConTeXt.
In any case, ConTeXt has a hard time with pagebreaks when you combine
elements that need both horizontal and vertical calculation, such as in:
\starttext
\dorecurse{64}
{\input knuth\footnote{\input zapf}
\startitemize[a, columns, eight, packed]
\dorecurse{64}{\item\currentitemnumber}
\stopitemize}
\stoptext
There is a similar issue with paragraph notes.
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-11-12 11:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 16:51 Fabrice Couvreur via ntg-context
2022-11-09 18:22 ` Pablo Rodriguez via ntg-context
2022-11-09 18:38 ` Bruce Horrocks via ntg-context
2022-11-10 10:36 ` Fabrice Couvreur via ntg-context
[not found] ` <CACyK-eoFTi70+i_rtPYYY=w76O86c95FRLh1xru7Q1xJZNEp4g@mail.gmail.com>
[not found] ` <CACyK-eqCH76c7ea=fg=gN+niAhb2nBEqXGJXkp-RbOWUY2jfwQ@mail.gmail.com>
[not found] ` <CACyK-ep-hb6-7n5k36Rq1UHsmcQVoV1P_thK1A5typBVhJsRVg@mail.gmail.com>
2022-11-10 17:06 ` Fabrice Couvreur via ntg-context
2022-11-11 20:58 ` Bruce Horrocks via ntg-context
2022-11-12 11:28 ` Pablo Rodriguez via ntg-context [this message]
2022-11-12 14:09 ` Fabrice Couvreur via ntg-context
2022-11-13 8:24 ` Pablo Rodriguez via ntg-context
2022-11-13 10:32 ` Fabrice Couvreur via ntg-context
2022-11-13 13:37 ` Pablo Rodriguez via ntg-context
2022-11-16 13:55 ` Fabrice Couvreur via ntg-context
2022-11-16 13:59 ` Fabrice Couvreur via ntg-context
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=a8704411-7252-9afe-1af2-df59fc3abdb9@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).