From: Hans Hagen <j.hagen@xs4all.nl>
To: denis.maier@ub.unibe.ch, ntg-context@ntg.nl
Subject: Re: Log overful boxes
Date: Thu, 4 Mar 2021 15:12:04 +0100 [thread overview]
Message-ID: <8299b833-46c4-e337-43e3-90a22f7eb065@xs4all.nl> (raw)
In-Reply-To: <bcdfb1550566432ea576b0c4513ba83a@ub.unibe.ch>
On 3/4/2021 12:32 PM, denis.maier@ub.unibe.ch wrote:
> Thanks, that's helpful. Is there a way to collect these pieces of information and print them at the end together with rest of the processing information. I'm thinking of something like:
>
> mkiv lua stats > 2 overful boxes, 3 underful boxes
>
> or:
>
> warning > 2 overful boxes, 3 underful boxes
>
> What do you think?
only when you document it on the wiki ....
pack quality >
pack quality > 4 entries added to the log file : overfull=1 | underfull=3
pack quality >
in the log:
pack quality > start
pack quality > oeps.tex [0000 - 0010] : overfull hbox : m
pack quality > oeps.tex [0000 - 0011] : underfull hbox : m
pack quality > oeps.tex [0000 - 0012] : underfull hbox : mm
pack quality > oeps.tex [0000 - 0013] : underfull hbox : mmm
pack quality > stop
using the already available mechanism:
\enabletrackers[builders.hpack.quality]
\enabletrackers[builders.hpack.overflow]
\starttext
\hbox to 0em {m}
\hbox to 1em {m}
\hbox to 2em {mm}
\hbox to 3em {mmm}
\hbox to 3em {m m m}
\stoptext
(so not much code needed; lmtx only)
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 prev parent reply other threads:[~2021-03-04 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 17:46 denis.maier
2021-03-03 16:41 ` Hans Hagen
2021-03-04 11:32 ` denis.maier
2021-03-04 14:12 ` Hans Hagen [this message]
2021-03-05 21:35 ` denis.maier
2021-03-05 22:14 ` Hans Hagen
2021-03-08 10:52 ` denis.maier
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=8299b833-46c4-e337-43e3-90a22f7eb065@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=denis.maier@ub.unibe.ch \
--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).