[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)

2024-03-08 Thread Pablo Rodriguez via ntg-context
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

[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)

2024-03-08 Thread Henning Hraban Ramm
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},

[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)

2024-03-08 Thread Wolfgang Schuster
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},

[NTG-context] \em issue in MkXL (2024.03.05 11:26)

2024-03-08 Thread 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:

[NTG-context] Re: How can I do this?

2024-03-08 Thread Henning Hraban Ramm
Am 08.03.24 um 17:56 schrieb Otared Kavian: Hi Ursula, The reason for which you did not get the expected result is that you have « } » missing in your file, that is the closing brace after your italic command « {\it » at the end of your document. Moreover you did not have a \stoptext in your

[NTG-context] Re: additional font faces

2024-03-08 Thread Henning Hraban Ramm
Am 08.03.24 um 18:02 schrieb Hans Hagen: On 3/8/2024 5:55 PM, Henning Hraban Ramm wrote: Hi, if I need an additional pair of upright and italic font faces, e.g. a Medium or Light version, would it make sense to define them like this: I'd just define a new typeface / bodyfont, using fo

[NTG-context] Re: additional font faces

2024-03-08 Thread Hans Hagen
On 3/8/2024 5:55 PM, Henning Hraban Ramm wrote: Hi, if I need an additional pair of upright and italic font faces, e.g. a Medium or Light version, would it make sense to define them like this: I'd just define a new typeface / bodyfont, using fo rinstance \starttypescript [sans]

[NTG-context] Re: How can I do this?

2024-03-08 Thread Otared Kavian
Hi Ursula, The reason for which you did not get the expected result is that you have « } » missing in your file, that is the closing brace after your italic command « {\it » at the end of your document. Moreover you did not have a \stoptext in your file, and a math command « \m » was not

[NTG-context] additional font faces

2024-03-08 Thread Henning Hraban Ramm
Hi, if I need an additional pair of upright and italic font faces, e.g. a Medium or Light version, would it make sense to define them like this: % adapted from font-pre.mkxl \definefontalternative[md] \definefontalternative[mi] \definefontalternative[ms] \definealternativestyle [medium]

[NTG-context] Re: Log entries about confusing level change

2024-03-08 Thread Hans Hagen
On 3/8/2024 3:38 AM, Rik Kabel wrote: Hello all, The following example produces two log entries that seem a bit odd. The log entries are: backend > bookmarks > confusing level change at level 3 around '1 body1' backend > bookmarks > confusing level change at level