From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: expansion / hz
Date: Thu, 15 Oct 2020 18:03:03 +0200 [thread overview]
Message-ID: <82c321e7-a20b-5492-46ff-4ee4a6520954@xs4all.nl> (raw)
Hi,
Because I'll probably forget to mention if, here is some new features
(upcoming lmtx only):
\definefontfeature[default][default,quality]
\setupbodyfont[pagella]
\starttext
{whatever we want to achieve} \input tufte
\setupalign[tolerant,stretch,hz]
{whatever we want to achieve} \input tufte
{\noexpansion whatever we want to achieve} \input tufte
\stoptext
That is: one can mark text to *not* use font expansion in an otherwise
expansion (hz) context. I have no clue how useful it is.
So, the first paragraph has no expansion., the second one has while the
third one has except for the first 5 words. And yes, there's also
similar trickery for protrusion, \noprotrusion, but i didn't test it.
This is in addition the the already mentioned \nokerning and
\noligaturing features that also obey grouping.
All this in the perspective of (luameta)tex giving detailed control over
matters.
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
___________________________________________________________________________________
reply other threads:[~2020-10-15 16:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=82c321e7-a20b-5492-46ff-4ee4a6520954@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).