From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Max Chernoff via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: Odd behaviour with Plex typescript
Date: Thu, 30 Jun 2022 20:27:45 +0200 [thread overview]
Message-ID: <572923ca-e8ce-5be8-82ef-d3eaf6a592da@freedom.nl> (raw)
In-Reply-To: <d5af55ec-c9a3-dcc1-aa9e-12448f3e4759@telus.net>
On 6/30/2022 10:36 AM, Max Chernoff via ntg-context wrote:
> If you load the Plex typescript, a spurious space is added on the first
> switch to another font, messing up any alignment. This doesn't happen
> with any other fonts; only with Plex.
>
> MWE:
>
> \setuphead[section][style={\switchtobodyfont[modern]}]
> \setupbodyfont[plex]
>
> \starttext
> \section{A}
> A
> \stoptext
>
> I was able to fix this by removing the space immediately before the "%"
> on line 136 of "type-imp-plex.mkiv", changing it from this (original):
>
>
> \definefontfeature[plexwideneddefault][default][extend=\luaexpr{1/0.85}]
> % An odd floating point number to correct monospace.
>
> to this (fixed):
>
>
> \definefontfeature[plexwideneddefault][default][extend=\luaexpr{1/0.85}]% An
> odd floating point number to correct monospace.
>
> I'm pretty sure that TeX is ignoring spaces at this point, so I have no
> idea why this issue exists or why the fix works.
when you trigger modern it will also process a typescript and that can
itself have spaces introduced
just preload it, as in:
\usebodyfont[modern]
\setupbodyfont[plex]
\setuphead
[section]
[style={\switchtobodyfont[modern]}]
\starttext
\section{A}
A
\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-30 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 8:36 Max Chernoff via ntg-context
2022-06-30 18:27 ` Hans Hagen via ntg-context [this message]
2022-06-30 20:32 ` Max Chernoff 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=572923ca-e8ce-5be8-82ef-d3eaf6a592da@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).