From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: no looseness in LMTX?
Date: Tue, 7 Sep 2021 14:57:03 +0200 [thread overview]
Message-ID: <9EF99C9D-AFB5-493E-A5CE-368769A8639F@fiee.net> (raw)
In-Reply-To: <7cd2bfc6-1ec2-a3fe-c501-4a1a431c4b28@xs4all.nl>
> Am 07.09.2021 um 14:07 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>
> On 9/7/2021 11:49 AM, Henning Hraban Ramm via ntg-context wrote:
>> In my magazine and book projects, I sometimes fix pagebreaking by stretching paragraphs with \looseness=1
>> Unfortunately this works _in my project_ only with MkIV, i.e. \looseness has no effect with LMTX.
>> I tried different examples (e.g. the attached file) and can’t reproduce the problem, there MkIV and LMTX always behave the same.
>> So it must be something in my settings.
>> What could cause the difference?
>> I tried English and German and different settings of alignment and tolerance.
>> Might it be font dependent?
>
> explained in manuals ...
>
> \startlinenumbering
> \startparagraph
> Weit .. beirren.
> \stopparagraph
> \stoplinenumbering
>
> \startlinenumbering
> \startparagraph\looseness=+2
> Weit .. beirren.
> \stopparagraph
> \stoplinenumbering
>
> \startlinenumbering
> \startparagraph
> Weit .. beirren.
> \looseness=+2\updateparagraphproperties\stopparagraph
> \stoplinenumbering
>
> in lmxt we freeze the properties set when a paragraph starts (contrary to using the last set value which actually fails when you set it inside a group)
>
> so, when you change some property mid paragraph you need to update the properties in order for them to be effective (can be done for looseness only if really needed); that works independent of grouping so it's more robust
Ok, but I thought I needed to use \looseness directly at the beginning of the paragraph, since it’s forgotten after the next \par?
HR
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-09-07 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 9:49 Henning Hraban Ramm via ntg-context
2021-09-07 11:15 ` Wolfgang Schuster via ntg-context
2021-09-07 13:13 ` Henning Hraban Ramm via ntg-context
2021-09-07 13:27 ` Hans Hagen via ntg-context
2021-09-07 12:07 ` Hans Hagen via ntg-context
2021-09-07 12:57 ` Henning Hraban Ramm 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=9EF99C9D-AFB5-493E-A5CE-368769A8639F@fiee.net \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
--cc=texml@fiee.net \
/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).