Re: [NTG-context] Unnecessary loading of lm-mono
On 26/05/21, 15:14, Rik Kabel wrote:
> For a few revisions now, I have seen the following as the very first line of
> log files. It is not coming from my document. Is anybody else seeing it?
>
>fonts > beware: no fonts are loaded yet, using 'lm mono'
>in box
>
> Here is an example document that generates it:
>
>\setupbodyfont[libertinus,10pt]
>\starttext
>Hello world!
>\stoptext
>
> It seems harmless, but it does result in loading an un-needed font.
>
>mkiv lua stats > loaded fonts: 4 files: lmmono10-regular.otf,
>libertinusmath-bold.otf, libertinusmath-regular.otf,
>libertinusserif-regular.otf
Looks like something is accidentally being typeset (maybe stored in a
box) before \starttext. You can reproduce this in MKIV with the
following
\writestatus{debug}{Before}
\setbox\scratchbox=\hbox{oeps}
\writestatus{debug}{After}
\starttext
Hello world!
\stoptext
and in the log you will find
debug > Before
fonts > beware: no fonts are loaded yet, using 'lm mono' in box
debug > After
so it is definitely due to typesetting.
Cheers, Henri
>
> --
> Rik
>
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] Unnecessary loading of lm-mono
For a few revisions now, I have seen the following as the very first line of log files. It is not coming from my document. Is anybody else seeing it? fonts > beware: no fonts are loaded yet, using 'lm mono' in box Here is an example document that generates it: \setupbodyfont[libertinus,10pt] \starttext Hello world! \stoptext It seems harmless, but it does result in loading an un-needed font. mkiv lua stats > loaded fonts: 4 files: lmmono10-regular.otf, libertinusmath-bold.otf, libertinusmath-regular.otf, libertinusserif-regular.otf -- Rik ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] new upload
On 5/26/2021 7:17 PM, Pablo Rodriguez wrote: On 5/25/21 6:20 PM, Hans Hagen wrote: [...] but for those willing to check the alternative, in page-ins.mkxl one can uncomment % \insertmode\plustwo Many thanks for the new upload, Hans. I’m extremely interested in testing this. How can we enable this feature in a permanent way? I mean, how can we avoid that an update disables it? Not ... because we define some inserts (e.g for footnotes) we need to decide what storage model to choose ... technically we can use the runtime 'experiment' feature but i expect to switch rather soon anyway. When users who test it encounter no problems it's okay because the core mechanisms are the same ... read: we still have inserts as usual but a variant engine-metadata storage model permits future - more robust and predictable - extensions; it was one of the more long term pending things to do which i decided to do now. fyi: As we transition to frozen mkiv i'm also removing some hybrid left-overs in lmtx (for instance, years ago the lmtx backend actually started out as an option in mkiv so that i could test the idea, so that resulted in some nasty code in order to deal with both cases ... but at some point I decided that mkiv should not go that dual route. So, every time when I run into some "it's time to move on and clean this up" moment I also check my long term agenda and this insert stuff was one of those items: it permits me to remove some old obsolete code still present in lmtx (that I admit I often already forgot about). 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 / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] new upload
On 5/25/21 6:20 PM, Hans Hagen wrote: > [...] but for those willing to check the alternative, in > page-ins.mkxl one can uncomment > > % \insertmode\plustwo Many thanks for the new upload, Hans. I’m extremely interested in testing this. How can we enable this feature in a permanent way? I mean, how can we avoid that an update disables it? Many thanks for your help, Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Fixed: Unwanted upright math in MkIV
On May 26, 2021, at 9:46 AM, Hans Hagen wrote:
> On 5/26/2021 5:14 PM, Gavin wrote:
>> I have more information on my upright math problem, but still no fix. Here
>> is my new MWE:
>> \starttext
>> \showotfcomposition{bodyfont}{}{a=b \m{a=b}}
>> \stoptext
>> I may not be using this debugging command correctly, but it is returning
>> useful information. The result is correct and the same in TeX Live 2021 MkIV
>> and in the most recent LMTX. Notice that glyphs selected for “a” and “b” are
>> different in the text and math:
>> LuaTeX, Version 1.13.2 (TeX Live 2021)
>> ConTeXt ver: 2021.03.05 19:11 MKIV fmt: 2021.5.11
>>> a=b 푎 = 푏 U+61:a U+3D:= U+62:b [glue][math] U+1D44E:푎 [glue] U+3D:= [glue]
>>> U+1D44F:푏 [math]
>> ConTeXt ver: 2021.05.25 18:03 LMTX fmt: 2021.5.25
>>> a=b 푎 = 푏 U+61:a U+3D:= U+62:b [glue][math] U+1D44E:푎 [glue] U+3D:= [glue]
>>> U+1D44F:푏 [math]
>> However, it is wrong in the most recent MkIV. The glyphs for “a” and “b” are
>> the same in the text and math, even though the switch to math is recognized.
>> (This switch is also evident in the pdf output. There is no space around the
>> “=“ in the text, but it is correct for the math.)
>> LuaTeX, Version 1.13.0 (TeX Live 2021)
>> ConTeXt ver: 2021.05.25 18:03 MKIV fmt: 2021.5.25
>>> a=ba=b U+61:a U+3D:= U+62:b [glue][math] U+61:a [kern][glue] U+3D:= [glue]
>>> U+62:b [math]
>> What could cause MkIV to select upright glyphs when it knows it is
>> typesetting math? One difference is the version of LuaTeX. Could this need
>> to be updated?
> todays upload should be ok (when i adapted some lmtx code i also did that in
> mkiv which should not happen)
Today’s version works great. Thanks!
-Gavin
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Unwanted upright math in MkIV
On 5/26/2021 5:14 PM, Gavin wrote:
I have more information on my upright math problem, but still no fix. Here is
my new MWE:
\starttext
\showotfcomposition{bodyfont}{}{a=b \m{a=b}}
\stoptext
I may not be using this debugging command correctly, but it is returning useful
information. The result is correct and the same in TeX Live 2021 MkIV and in
the most recent LMTX. Notice that glyphs selected for “a” and “b” are different
in the text and math:
LuaTeX, Version 1.13.2 (TeX Live 2021)
ConTeXt ver: 2021.03.05 19:11 MKIV fmt: 2021.5.11
a=b 푎 = 푏 U+61:a U+3D:= U+62:b [glue][math] U+1D44E:푎 [glue] U+3D:= [glue]
U+1D44F:푏 [math]
ConTeXt ver: 2021.05.25 18:03 LMTX fmt: 2021.5.25
a=b 푎 = 푏 U+61:a U+3D:= U+62:b [glue][math] U+1D44E:푎 [glue] U+3D:= [glue]
U+1D44F:푏 [math]
However, it is wrong in the most recent MkIV. The glyphs for “a” and “b” are
the same in the text and math, even though the switch to math is recognized.
(This switch is also evident in the pdf output. There is no space around the
“=“ in the text, but it is correct for the math.)
LuaTeX, Version 1.13.0 (TeX Live 2021)
ConTeXt ver: 2021.05.25 18:03 MKIV fmt: 2021.5.25
a=ba=b U+61:a U+3D:= U+62:b [glue][math] U+61:a [kern][glue] U+3D:= [glue]
U+62:b [math]
What could cause MkIV to select upright glyphs when it knows it is typesetting
math? One difference is the version of LuaTeX. Could this need to be updated?
todays upload should be ok (when i adapted some lmtx code i also did
that in mkiv which should not happen)
-
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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Unwanted upright math in MkIV
I have more information on my upright math problem, but still no fix. Here is
my new MWE:
\starttext
\showotfcomposition{bodyfont}{}{a=b \m{a=b}}
\stoptext
I may not be using this debugging command correctly, but it is returning useful
information. The result is correct and the same in TeX Live 2021 MkIV and in
the most recent LMTX. Notice that glyphs selected for “a” and “b” are different
in the text and math:
LuaTeX, Version 1.13.2 (TeX Live 2021)
ConTeXt ver: 2021.03.05 19:11 MKIV fmt: 2021.5.11
> a=b 푎 = 푏 U+61:a U+3D:= U+62:b [glue][math] U+1D44E:푎 [glue] U+3D:= [glue]
> U+1D44F:푏 [math]
ConTeXt ver: 2021.05.25 18:03 LMTX fmt: 2021.5.25
> a=b 푎 = 푏 U+61:a U+3D:= U+62:b [glue][math] U+1D44E:푎 [glue] U+3D:= [glue]
> U+1D44F:푏 [math]
However, it is wrong in the most recent MkIV. The glyphs for “a” and “b” are
the same in the text and math, even though the switch to math is recognized.
(This switch is also evident in the pdf output. There is no space around the
“=“ in the text, but it is correct for the math.)
LuaTeX, Version 1.13.0 (TeX Live 2021)
ConTeXt ver: 2021.05.25 18:03 MKIV fmt: 2021.5.25
> a=ba=b U+61:a U+3D:= U+62:b [glue][math] U+61:a [kern][glue] U+3D:= [glue]
> U+62:b [math]
What could cause MkIV to select upright glyphs when it knows it is typesetting
math? One difference is the version of LuaTeX. Could this need to be updated?
Gavin
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
