From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Mia Bikey <redspacecube@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: Inline mathematics is stretched
Date: Mon, 30 Oct 2023 08:28:06 +0100 [thread overview]
Message-ID: <9ac63c54-4230-42e9-9df6-1ae436138ac5@freedom.nl> (raw)
In-Reply-To: <CALdMdOH+5xHa4jN=S-QiQA708G6wdBaO1GR9ej=UfZ=WbfT4WQ@mail.gmail.com>
On 10/30/2023 8:05 AM, Mia Bikey wrote:
> Yes well of course no issue arises if I just change the whole font.
> But I wanted to keep using the mono font thus reporting issues with it.
In that case you have to go for flushleft
\setupalign[verytolerant,nothyphenated,flushleft]
because otherwise tex will try to come to the best solution by using
stretch and shrink and therefore stretch and shrink in interatom spacing
wins over little or none in mono spacing
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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-10-30 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 12:33 [NTG-context] " Mia Bikey
2023-10-29 22:16 ` [NTG-context] " Hans Hagen via ntg-context
[not found] ` <CALdMdOH+5xHa4jN=S-QiQA708G6wdBaO1GR9ej=UfZ=WbfT4WQ@mail.gmail.com>
2023-10-30 7:28 ` Hans Hagen via ntg-context [this message]
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=9ac63c54-4230-42e9-9df6-1ae436138ac5@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.nl \
--cc=redspacecube@gmail.com \
/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).