ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
Date: Sun, 10 Mar 2024 11:45:37 +0100	[thread overview]
Message-ID: <63c35706-351e-39f7-b1d7-3e272e662403@gmx.es> (raw)
In-Reply-To: <6c12b92f-30de-498b-8c41-1520f0fd8ce2@freedom.nl>

On 3/10/24 10:46, Hans Hagen via ntg-context wrote:
> [...]
> using the low level commands
>
> \glyphscale
> \glyphxscale
> \glyphyscale
> \glyphslant
> \glyphweight
>
> directly can have side efects when at an outer level these are also set,
> so you need to accumulate, like
> [...]
> which you will now wikify...

Many thanks for your reply, Hans.

I will wikify this, once I figure out where it can fit in the wiki (in
due time, since ConTeXt is more and more complex for me lately and my
free time is less and less these days).

I only used \enableexperiments[fonts.compact] and then \em.

I thought when I (mis)read your messages that compact fonts is the way
to go in LMTX.

This was the reason I enabled them (the sooner we test new features
today, the less issues will be faced with them tomorrow).

\glyphslant came into the conversation after experiencing an issue
triggered by enabling compact fonts.

Sorry for being explicitly verbose, but I intend to have the \em
behavior also fixed in compact fonts.

Many thanks for your help,

Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2024-03-10 10:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 17:50 [NTG-context] " Pablo Rodriguez via ntg-context
2024-03-08 18:09 ` [NTG-context] " Wolfgang Schuster
2024-03-08 18:39   ` Pablo Rodriguez via ntg-context
2024-03-09 15:04     ` Wolfgang Schuster
2024-03-10  8:32       ` Pablo Rodriguez via ntg-context
2024-03-10  9:46         ` Hans Hagen via ntg-context
2024-03-10 10:45           ` Pablo Rodriguez via ntg-context [this message]
2024-03-10 10:48           ` Wolfgang Schuster
2024-03-10 16:57             ` Hans Hagen
2024-03-08 18:10 ` Henning Hraban Ramm

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=63c35706-351e-39f7-b1d7-3e272e662403@gmx.es \
    --to=ntg-context@ntg.nl \
    --cc=oinos@gmx.es \
    /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).