ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
Date: Sun, 10 Mar 2024 10:46:20 +0100	[thread overview]
Message-ID: <6c12b92f-30de-498b-8c41-1520f0fd8ce2@freedom.nl> (raw)
In-Reply-To: <c00bda6f-4542-0f10-aa70-57b3a3a3e98f@gmx.es>

On 3/10/2024 9:32 AM, Pablo Rodriguez via ntg-context wrote:
> On 3/9/24 16:04, Wolfgang Schuster wrote:
>> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
>>> [...]
>>>     \enableexperiments[fonts.compact]
>>>
>>> Which seeems weird to me. Or at least, I thought I read that Hans
>>> enabled it by default in LMTX.
>>
>> AFAIR Hans uses the setting in his own documents.
> 
> I have been using it for a while.
> 
> I hope the issue with \glyphslant might be fixed to enable it again.
> 
>>> Then my question is whether this was caused by simply enabling compact
>>> fonts or by doing it twice.
>>
>> The results happen when you use compact mode and is a result of
>> \glyphslant which keeps the value of the italic style even when you
>> switch back to the upright style.
> 
> Many thanks for your explaination,
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

\starttext

test {\glyphscale 2000 test \glyphscale \numericscaled1.2\glyphscale 
test} test

test {\glyphslant  500 test \glyphslant \numericscaled2.0\glyphslant 
test} test

test {\glyphweight 100 test \glyphweight\numericscaled2.0\glyphweight 
test} test

\stoptext

which you will now wikify ...

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
___________________________________________________________________________________

  reply	other threads:[~2024-03-10  9:48 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 [this message]
2024-03-10 10:45           ` Pablo Rodriguez via ntg-context
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=6c12b92f-30de-498b-8c41-1520f0fd8ce2@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).