\em issue in MkXL (2024.03.05 11:26)
Dear list, the following latest gets differents results when compiled with MkXL and MkIV (in current latest from 2024.03.05 11:26): \definefontfamily[mainface][rm][TeX Gyre Termes] [features={default, quality}, it={style: regular, features:{default, quality, slanted}}, sl={style: regular, features:{default, quality, slanted}}] \setupbodyfontenvironment [default] [em=italic] \setupbodyfont[mainface] \starttext \startTEXpage[offset=1em] a\\ \em b\\ \em c\\ \em d\\ \stopTEXpage \stoptext LMTX gets b, c and d in slanted form. LuaTeX gets only b and c in slanted form. I think LMTX may have an issue here. Could anyone be so kind to confirm this? Many thanks for your help, Pablo
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
Dear list,
the following latest gets differents results when compiled with MkXL and MkIV (in current latest from 2024.03.05 11:26):
\definefontfamily[mainface][rm][TeX Gyre Termes] [features={default, quality}, it={style: regular, features:{default, quality, slanted}}, sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment [default] [em=italic]
\setupbodyfont[mainface] \starttext \startTEXpage[offset=1em] a\\ \em b\\ \em c\\ \em d\\ \stopTEXpage \stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
I think LMTX may have an issue here.
Could anyone be so kind to confirm this?
I get b and d in italic which is the expected output. Wolfgang
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. Then my question is whether this was caused by simply enabling compact fonts or by doing it twice. Many thanks for your help, Pablo
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
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, Pablo
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 -----------------------------------------------------------------
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
Hans Hagen via ntg-context schrieb am 10.03.2024 um 10:46:
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
The problem is that compact mode uses them to apply the slanted feature without any manual use of the commands from a user. \enableexperiments[fonts.compact] \definefontfamily[mainface][rm][TeX Gyre Termes] [it={style:regular, features:{default,slanted}}, sl={style:regular, features:{default,slanted}}] \setupbodyfont[mainface] \starttext \startstyle[style=italic]normal {\em emphasized} normal\stopstyle \stoptext The only way to mask the effect is to create a new fontfeature with the minimum slant value and apply it to the upright style. \definefontfeature [unslanted] [slant=0.001] \definefontfamily[mainface][rm][TeX Gyre Termes] [features={default,unslanted}, it={style:regular, features:{default,slanted}}, sl={style:regular, features:{default,slanted}}] Wolfgang
On 3/10/2024 11:48 AM, Wolfgang Schuster wrote:
Hans Hagen via ntg-context schrieb am 10.03.2024 um 10:46:
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
The problem is that compact mode uses them to apply the slanted feature without any manual use of the commands from a user.
\enableexperiments[fonts.compact]
\definefontfamily[mainface][rm][TeX Gyre Termes] [it={style:regular, features:{default,slanted}}, sl={style:regular, features:{default,slanted}}]
\setupbodyfont[mainface]
\starttext
\startstyle[style=italic]normal {\em emphasized} normal\stopstyle
\stoptext
The only way to mask the effect is to create a new fontfeature with the minimum slant value and apply it to the upright style.
\definefontfeature [unslanted] [slant=0.001]
\definefontfamily[mainface][rm][TeX Gyre Termes] [features={default,unslanted}, it={style:regular, features:{default,slanted}}, sl={style:regular, features:{default,slanted}}] ok, i'll fix that (build is down so no update)
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 -----------------------------------------------------------------
Am 08.03.24 um 18:50 schrieb Pablo Rodriguez via ntg-context:
Dear list,
the following latest gets differents results when compiled with MkXL and MkIV (in current latest from 2024.03.05 11:26):
\definefontfamily[mainface][rm][TeX Gyre Termes] [features={default, quality}, it={style: regular, features:{default, quality, slanted}}, sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment [default] [em=italic]
\setupbodyfont[mainface] \starttext \startTEXpage[offset=1em] a\\ \em b\\ \em c\\ \em d\\ \stopTEXpage \stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
With latest LMTX (2024.03.05), b and d are slanted, as I would expect. This might be just a test case, but I’d avoid switches like \em without grouping. Hraban
participants (5)
-
Hans Hagen -
Hans Hagen -
Henning Hraban Ramm -
Pablo Rodriguez -
Wolfgang Schuster