From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Benjamin Buchmuller via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Count (and limit) glyphs per line?
Date: Fri, 24 Jun 2022 19:58:51 +0200 [thread overview]
Message-ID: <64eb5229-ab5a-8566-2d40-9f6a74986a81@xs4all.nl> (raw)
In-Reply-To: <252F31DD-EEDD-458C-9B54-5B7DFE420C3D@gmail.com>
On 6/24/2022 5:15 AM, Benjamin Buchmuller via ntg-context wrote:
> Dear list,
>
> I've been confronted with the following 'intriguing' formatting requirement for a document:
>
> "
> • Type density: Must be no more than 15 characters per linear inch (including characters and spaces).
> • Line spacing: Must be no more than six lines per vertical inch.
> "
>
> While the line spacing resolves in ConTeXt to
>
> \setupinterlinespace[line=\dimexpr(1in / 6)]
>
> I was wondering if one can limit "type density" as the number of glyphs per inch in TeX too? I thought, it is more convenient to rephrase this request (for a 7 in textwidth) to limit the number of glyphs per line to 112. (Font must be sans or serif, of course ...)
>
> I've tried
>
> \setuplayout[width=112\averagecharwidth]
>
> which, however, results in ~120–130 characters and spaces per line. Pragmatically, I'm narrowing the text width to empirically match the requirement, but I'm nevertheless curious if there is a Lua/TeX solution to this "problem"?
Just assume the worst case and take the narrowest character:
\showframe
\setupbodyfont[modern] % we need to set the font
\normalexpanded {
\setuplayout
[textwidth=\the\dimexpr112\fontcharwd\font`.\relax]
}
\starttext
\input tufte
\stoptext
-----------------------------------------------------------------
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:[~2022-06-24 17:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 3:15 Benjamin Buchmuller via ntg-context
2022-06-24 5:44 ` Max Chernoff via ntg-context
2022-06-25 15:38 ` Benjamin Buchmuller via ntg-context
2022-06-25 20:25 ` Benjamin Buchmuller via ntg-context
2022-06-25 21:40 ` Max Chernoff via ntg-context
2022-06-26 15:59 ` Benjamin Buchmuller via ntg-context
2022-06-26 22:32 ` Max Chernoff via ntg-context
2022-06-27 9:33 ` Hans Hagen via ntg-context
2022-07-18 21:24 ` Benjamin Buchmuller via ntg-context
2022-07-26 17:40 ` Hans Hagen via ntg-context
2022-06-26 17:11 ` Hans Hagen via ntg-context
2022-06-26 8:28 ` Hans Hagen via ntg-context
2022-06-24 7:31 ` Henning Hraban Ramm via ntg-context
2022-06-24 17:58 ` Hans Hagen via ntg-context [this message]
2022-06-26 19:26 Benjamin Buchmuller 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=64eb5229-ab5a-8566-2d40-9f6a74986a81@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).