ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Pablo Rodriguez 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: Sat, 9 Mar 2024 16:04:47 +0100	[thread overview]
Message-ID: <2247a2e0-6f36-6bc8-bf53-81e404919400@gmail.com> (raw)
In-Reply-To: <a4891f5c-b371-7b93-a539-7748b8df5b72@gmx.es>

Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
> On 3/8/24 19:09, Wolfgang Schuster wrote:
>> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
>>> [...]
>>> LMTX gets b, c and d in slanted form.
>>>
>>> LuaTeX gets only b and c in slanted form.
>> [...]
>> I get b and d in italic which is the expected output.
> 
> Sorry, my LuaTeX is getting slanted b and d ("c" was my typo).
> 
> But I see what was causing my issue (line from
> ~/texmf/texmf-local/cont-loc.mkxl):
> 
>    \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.

> 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.

\enableexperiments[fonts.compact]

\definefontfamily[mainface][rm][TeX Gyre Termes]
   [it={style:regular, features:{default,slanted}},
    sl={style:regular, features:{default,slanted}}]

\setupbodyfont[mainface]

\starttext
\tf h\showcurrentfont[]\crlf
\it h\showcurrentfont[]\crlf
%\glyphslant\zerocount
\tf h\showcurrentfont[]\crlf
\it h\showcurrentfont[]
\stoptext

Wolfgang
___________________________________________________________________________________
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-09 15:09 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 [this message]
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
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=2247a2e0-6f36-6bc8-bf53-81e404919400@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=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).