From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: lmtx
Date: Fri, 19 Feb 2021 13:32:52 +0100 [thread overview]
Message-ID: <0ca26e0d-3695-6172-4877-c885ec480838@xs4all.nl> (raw)
Hi,
In the last couple of lmtx uploads \startTEXpage should work a bit
better. These uploads also introduced a new option for alignments, which
can be checked in:
\def\DemoA#1{\vbox{\red \hsize#1\input tufte }}
\def\DemoB#1{\vbox{\green \setupalign[always]\hsize#1\input tufte }}
\def\DemoC#1{\startTEXpage[offset=10pt]\DemoA{#1pt}\blank\DemoB{#1pt}\blank#1pt\stopTEXpage}
\starttext
\dostepwiserecurse{300}{600}{10}{
\startTEXpage[offset=10pt]
\startoverlay
{\DemoA{#1pt}}
{\DemoB{#1pt}}
\stopoverlay
\blank
\the\dimexpr#1pt\relax
\stopTEXpage
}
\DemoC{370} \DemoC{390} \DemoC{490} \DemoC{540} \DemoC{580}
\stoptext
I leave it to users to determine if the few cases where the results
differ are better or worse but one can for instance use it to influence
(as side effect) the last line. In general, tweaking the machinery can
give different results and i guess that hardly any user can make
consistent claims about what is better. It all depends on what one deals
with.
(The keyword is suboptimal, it kind of tells what happens but on the
other obscurew what really goes on: always forcing a first hyphenation
pass when breaking lines.)
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
-----------------------------------------------------------------
___________________________________________________________________________________
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 reply other threads:[~2021-02-19 12:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 12:32 Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-03 21:00 lmtx Hans Hagen via ntg-context
2021-01-18 18:20 lmtx Hans Hagen
2021-01-19 10:57 ` lmtx Floris van Manen
2021-01-19 11:10 ` lmtx Hans Hagen
2021-01-19 11:31 ` lmtx Jano Kula
2021-01-19 19:12 ` lmtx Jan U. Hasecke
2021-01-19 23:03 ` lmtx Hans Hagen
2020-10-30 22:29 lmtx Hans Hagen
2020-10-31 2:50 ` lmtx Jairo A. del Rio
2020-11-02 19:43 ` lmtx Hans Hagen
2020-06-19 10:11 lmtx Hans Hagen
[not found] <mailman.1.1576234801.28358.ntg-context@ntg.nl>
2019-12-13 19:29 ` lmtx Jeong Dal
[not found] <mailman.310.1576128525.1207.ntg-context@ntg.nl>
2019-12-12 23:48 ` lmtx Jeong Dal
2019-12-13 8:39 ` lmtx Otared Kavian
2019-12-12 0:37 lmtx Hans Hagen
2019-12-12 5:28 ` lmtx Otared Kavian
2019-12-12 6:04 ` lmtx Otared Kavian
2019-12-12 10:08 ` lmtx Hans Hagen
2019-12-12 6:36 ` lmtx Richard Mahoney | Indica et Buddhica
2019-12-12 16:59 ` lmtx Pablo Rodriguez
2019-12-12 20:13 ` lmtx Pablo Rodriguez
2019-08-05 12:38 lmtx Hans Hagen
2019-04-02 9:05 lmtx Hans Hagen
2019-04-02 19:03 ` lmtx Taco Hoekwater
2019-04-02 20:11 ` lmtx Henri Menke
2019-04-02 20:19 ` lmtx Hans Hagen
2019-04-02 20:30 ` lmtx Henri Menke
2019-04-02 20:47 ` lmtx 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=0ca26e0d-3695-6172-4877-c885ec480838@xs4all.nl \
--to=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).