From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: issue mixing font features (LMTX & MkIV)
Date: Mon, 4 Mar 2024 11:09:00 +0100 [thread overview]
Message-ID: <066af2df-e7b1-4902-95c1-38d805147adc@freedom.nl> (raw)
In-Reply-To: <83f1d53a-99ed-0afa-d6c5-743027215700@gmx.es>
On 3/3/2024 11:54 AM, Pablo Rodriguez via ntg-context wrote:
> Dear list,
>
> I have the following sample:
>
> \definefontfeature[wider][extend=2]
>
> \definefontfamily[mainface][rm][TeX Gyre Pagella]
> [features={default, quality, wider},
> it={style: regular, features:{default, slanted, quality}},
> bf={style: regular, features:{default, boldened-30}},
> bi={style: regular, features:{default, boldened-30, slanted}}]
>
> \setupbodyfont
> [mainface, 30pt]
>
> \starttext
> \startTEXpage[offset=1ex]
> a
> {\it a}\\
> {\bf a}
> {\bi a}
> \stopTEXpage
> \stoptext
>
> With current latest (2024.02.27 09:21), LuaTeX gets boldened and slanted
> for regular (but the other fonts cannot inherit the wider feature and
> wider will not mix with boldened-30 [even when specified]).
>
> For some reason, LMTX from current latest cannot get slanted and
> boldened-30 (but it mixes the inherited wider feature in all fonts).
>
> This began to behave differently in latest from 2024.01.08 11:23 (which
> is my next version after the one from 2023.09.26 18:19).
>
> Could anyone confirm the issue?
accumulating these effects is dependent on how the features that you use
are defined
in luametatex we have a bit more advanced mechanism (also relates to
compact mode) because th eengine is a bit more clever
just make sure that you don't add up features where one calcels the
other, so use for instance:
\definefontfeature[wide] [extend=2]
\definefontfeature[wideslant] [extend=2,slant=.2]
\definefontfeature[widebold] [extend=2,weight=.1]
\definefontfeature[wideboldslant][extend=2,weight=.1,slant=.2]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
[tf={style:regular,features:{default,quality,wide}},
it={style:regular,features:{default,quality,wideslant}},
bf={style:regular,features:{default,quality,widebold}},
bi={style:regular,features:{default,quality,wideboldslant}}]
\setupbodyfont
[mainface,30pt]
\starttext
\startTEXpage[offset=1ex]
a
{\it a}
{\bf a}
{\bi a}
\stopTEXpage
\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 / 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
___________________________________________________________________________________
next prev parent reply other threads:[~2024-03-04 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 10:54 [NTG-context] " Pablo Rodriguez via ntg-context
2024-03-04 10:09 ` Hans Hagen via ntg-context [this message]
2024-03-04 18:30 ` [NTG-context] " Pablo Rodriguez 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=066af2df-e7b1-4902-95c1-38d805147adc@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).