ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Adam Reviczky via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: Adam Reviczky <reviczky@gmail.com>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Paragraph break over pages with hanging float
Date: Mon, 15 Nov 2021 14:20:11 +0000	[thread overview]
Message-ID: <CABaoHutBoBkYezSrT-T0HESJOtb5PCNrELs41QcZeXa91C5zUg@mail.gmail.com> (raw)
In-Reply-To: <d9e225b4-50d2-49d6-019c-155cbc5f8cf9@xs4all.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1941 bytes --]

Thank Hans,

I thought something along those lines, but thank you for the explanation.
Indeed, I probably should do it differently.

If the "force" option would not break anything then I would like to try
that, otherwise it is all fine as is.
This is not really critical and I will rather change the float in my
document than create more issues.

Regards,
Adam

On Mon, Nov 15, 2021 at 2:00 PM Hans Hagen <j.hagen@xs4all.nl> wrote:

> On 11/15/2021 6:26 AM, Adam Reviczky via ntg-context wrote:
> > Hi,
> >
> > Is there a way to allow a paragraph to break over two pages (between the
> > paragraph start and the placement of the float) with a hanging float
> > further down the paragraph?
> >
> > MWE:
> >
> > \starttext
> > \input lorem
> > \blank[20*line]
> >
> > % commenting out the hanging float allows paragraph break
> > \startplacefigure[location={right,15*hang}]
> > \framed[width=3cm,height=2cm]{graphic}
> > \stopplacefigure
> >
> > \dorecurse{10}{\input lorem}
> > \stoptext
> >
> > When I remove the hanging float, the paragraph is broken down at the
> > first pagebreak.
> > With the float, the paragraph starts always on the next page, regardless
> > of the space left on the previous page.
> Yes and no ... tex cannot really lookahead here. But thanks to some
> recent new trickery I can provide:
>
>    location={right,15*hang,force}
>
> However, it really is up to the user to check of all works out right
> (but i assume that the 15*hang is also soemthing specific for the
> situation). Adapting this already (too) complex mechanism too much is
> asking for issues.
>
> Hans
>
> -----------------------------------------------------------------
>                                            Hans Hagen | PRAGMA ADE
>                Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>         tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
>

[-- Attachment #1.2: Type: text/html, Size: 2754 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2021-11-15 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  5:26 Adam Reviczky via ntg-context
2021-11-15 14:00 ` Hans Hagen via ntg-context
2021-11-15 14:20   ` Adam Reviczky via ntg-context [this message]

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=CABaoHutBoBkYezSrT-T0HESJOtb5PCNrELs41QcZeXa91C5zUg@mail.gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.nl \
    --cc=reviczky@gmail.com \
    /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).