Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
On Tue, Apr 11, 2023 at 11:23:45AM +0200, Hans Hagen via ntg-context wrote:
> On 4/11/2023 11:11 AM, Carlos via ntg-context wrote:
>
> > Hello Alan, my PATH is set to:
> >
> > PATH=/home/ce/context-install/bin:/home/ce/context-install/tex/texmf-linux-64/bin:/opt/texlive/2023/bin/x86_64-linux:$PATH;
> > export PATH
>
> what is that first path doing there
>
okay. Let's remove it. The second one wouldn't hurt it I guess, right?
and it's needed.
> > Do we actually need to list all kpsea variable here ?? fine
>
> doesn't hurt .. also because they can be set badly at the os level (you
> really don't want to knwo when has be encountered in the 20th century)
>
:)
> > Here are some of them, which are really irrelevant by the way, but just
> > adding info
> >
> > $ kpsewhich --var-value TEXMFROOT
> > /opt/texlive/2023
> > $ kpsewhich --var-value TEXMFDIST
> > /opt/texlive/2023/texmf-dist
> > $ kpsewhich --var-value TEXMFLOCAL
> > /opt/texlive/texmf-local
> >
> > Now let's take a peek inside the TeX Live infrastructure-only, shall
> > we? (just for additional info as TeX Live is ocnsidered one of the
> > many scripts out there, right? One is interested in the standalone in
> > the end)
> >
> > LICENSE.CTAN bin install-tl.log texmf-config
> > texmfcnf.lua
> > LICENSE.TL doc.htmlreadme-html.dir texmf-disttlpkg
> > README index.html readme-txt.dir texmf-var
> > README.usergroups install-tl release-texlive.txt texmf.cnf
>
> that si texlive, not standalone
>
> > that texmfcnf.lua only holds
> >
> > return {
> >content = {
> > variables = {
> > },
> >},
> > }
> >
> > which is useless
>
> and harmless (somethign old texlive)
>
> > so, no bueno. Not when the aim is to install a fully functional context
> > standalone
> >
> > Now let's take a peek instide and see the binaries
> >
> > afm2tfm etex kpsereadlink mfmtxrun.lua texluac
> > bibtex extractbb kpsestat mf-nowin pdfetex tlmgr
> > context fmtutil kpsewhichmft pdflatextlshell
> > context.lua fmtutil-sys latexmkindex pdftex updmap
> > dvilualatex fmtutil-user luahbtex mktexfmt pktogf updmap-sys
> > dviluatexgftodvi lualatex mktexlsr pktype
> > updmap-user
> > dvipdfm gftopkluametatex mktexmf rungs xdvi
> > dvipdfmx gftypeluaotfload-tool mktexpk simpdftex xdvi-xaw
> > dvipdft inimf luatex mktextfm tex xdvipdfmx
> > dvipsinitexmakeindexmptopdf texhash
> > ebb kpseaccessman mtxruntexlua
> >
> > Do you see that context and context.lua out there, right? That's
> > only after running tlmgr and installing it, so no bueno, because in
> > the meantime there's no texmfcnf.lua around
>
> comes from the tex live base package ... harmless, just takes bytes (only
> luatex, luametatex, context, mtxrun, context.lua and mtxrun.lua matter)
>
> > Then again, remember in the current state I actually don't have
> > texmfcnf.lua for the simple reason that first-setup.sh never provided
> > it, correct?
>
> aditya pointer that out (and it's one of the files that one doesn't want to
> be overwritten anyway)
>
For clarification, Do you mean the file that consists of
-- the distributed file (.../texlive//texmf-dist/web2c/texmfcnf.lua).
-- And include *only* your changed values, not a copy of the whole thing!
return {
content = {
variables = {
},
},
}
and belongs to TeX Live?
> > Here we go! Back to point A where we were at before
> as alan pointed out: just install with the lmtx installer in a path separate
> from tex live, set the path and you're done; don't try to mix texlive with a
> adapted of standalone, texlive has its own context package and updates etc;
> keep them separated
alright. That's fine. That's what I thought.
So copy over the mtxrun binary on texmf-linux-64/bin to context and call it a
day?
>
> 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
> -
>
> _
Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
On 4/11/2023 11:11 AM, Carlos via ntg-context wrote:
Hello Alan, my PATH is set to:
PATH=/home/ce/context-install/bin:/home/ce/context-install/tex/texmf-linux-64/bin:/opt/texlive/2023/bin/x86_64-linux:$PATH;
export PATH
what is that first path doing there
Do we actually need to list all kpsea variable here ?? fine
doesn't hurt .. also because they can be set badly at the os level (you
really don't want to knwo when has be encountered in the 20th century)
Here are some of them, which are really irrelevant by the way, but just
adding info
$ kpsewhich --var-value TEXMFROOT
/opt/texlive/2023
$ kpsewhich --var-value TEXMFDIST
/opt/texlive/2023/texmf-dist
$ kpsewhich --var-value TEXMFLOCAL
/opt/texlive/texmf-local
Now let's take a peek inside the TeX Live infrastructure-only, shall
we? (just for additional info as TeX Live is ocnsidered one of the
many scripts out there, right? One is interested in the standalone in
the end)
LICENSE.CTAN bin install-tl.log texmf-config texmfcnf.lua
LICENSE.TL doc.htmlreadme-html.dir texmf-disttlpkg
README index.html readme-txt.dir texmf-var
README.usergroups install-tl release-texlive.txt texmf.cnf
that si texlive, not standalone
that texmfcnf.lua only holds
return {
content = {
variables = {
},
},
}
which is useless
and harmless (somethign old texlive)
so, no bueno. Not when the aim is to install a fully functional context
standalone
Now let's take a peek instide and see the binaries
afm2tfm etex kpsereadlink mfmtxrun.lua texluac
bibtex extractbb kpsestat mf-nowin pdfetex tlmgr
context fmtutil kpsewhichmft pdflatextlshell
context.lua fmtutil-sys latexmkindex pdftex updmap
dvilualatex fmtutil-user luahbtex mktexfmt pktogf updmap-sys
dviluatexgftodvi lualatex mktexlsr pktype updmap-user
dvipdfm gftopkluametatex mktexmf rungs xdvi
dvipdfmx gftypeluaotfload-tool mktexpk simpdftex xdvi-xaw
dvipdft inimf luatex mktextfm tex xdvipdfmx
dvipsinitexmakeindexmptopdf texhash
ebb kpseaccessman mtxruntexlua
Do you see that context and context.lua out there, right? That's
only after running tlmgr and installing it, so no bueno, because in
the meantime there's no texmfcnf.lua around
comes from the tex live base package ... harmless, just takes bytes
(only luatex, luametatex, context, mtxrun, context.lua and mtxrun.lua
matter)
Then again, remember in the current state I actually don't have
texmfcnf.lua for the simple reason that first-setup.sh never provided
it, correct?
aditya pointer that out (and it's one of the files that one doesn't want
to be overwritten anyway)
Here we go! Back to point A where we were at before
as alan pointed out: just install with the lmtx installer in a path
separate from tex live, set the path and you're done; don't try to mix
texlive with a adapted of standalone, texlive has its own context
package and updates etc; keep them separated
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
On Mon, Apr 10, 2023 at 10:01:55PM -0600, Alan Braslau via ntg-context wrote:
> On Mon, 10 Apr 2023 20:51:58 -0400 (EDT)
> Aditya Mahajan via ntg-context wrote:
>
> > Did you source the `setuptex` script, which sets the correct path.
>
> My PATH is set to
> PATH=./context/tex/texmf-freebsd-amd64/bin:/home/MyAccount/context/tex/texmf-freebsd-amd64/bin:...
>
> If my current working directory ("./") is a project that contains its
> very own subdirectory ./context/, then this is used to typeset the
> project. If not, it falls back on my own general standalone
> $HOME/context/, and if that does not exist, then it falls back on, say,
> a systemwide TeXlive installation.
>
> This is all that is needed to have many versions coexist.
>
> Alan
Hello Alan, my PATH is set to:
PATH=/home/ce/context-install/bin:/home/ce/context-install/tex/texmf-linux-64/bin:/opt/texlive/2023/bin/x86_64-linux:$PATH;
export PATH
because not by going by TeX Live infrastructure only, but rather
by standalone resolvers that's exactly what the additional steps to
install that very same standalone required, a folder
texmf-linux-64/bin, which it's pretty much self-explanatory
And I already mentioned the above earlier
Again
Do we actually need to list all kpsea variable here ?? fine
Here are some of them, which are really irrelevant by the way, but just
adding info
$ kpsewhich --var-value TEXMFROOT
/opt/texlive/2023
$ kpsewhich --var-value TEXMFDIST
/opt/texlive/2023/texmf-dist
$ kpsewhich --var-value TEXMFLOCAL
/opt/texlive/texmf-local
Now let's take a peek inside the TeX Live infrastructure-only, shall
we? (just for additional info as TeX Live is ocnsidered one of the
many scripts out there, right? One is interested in the standalone in
the end)
LICENSE.CTAN bin install-tl.log texmf-config texmfcnf.lua
LICENSE.TL doc.htmlreadme-html.dir texmf-disttlpkg
README index.html readme-txt.dir texmf-var
README.usergroups install-tl release-texlive.txt texmf.cnf
that texmfcnf.lua only holds
return {
content = {
variables = {
},
},
}
which is useless
so, no bueno. Not when the aim is to install a fully functional context
standalone
Now let's take a peek instide and see the binaries
afm2tfm etex kpsereadlink mfmtxrun.lua texluac
bibtex extractbb kpsestat mf-nowin pdfetex tlmgr
context fmtutil kpsewhichmft pdflatextlshell
context.lua fmtutil-sys latexmkindex pdftex updmap
dvilualatex fmtutil-user luahbtex mktexfmt pktogf updmap-sys
dviluatexgftodvi lualatex mktexlsr pktype updmap-user
dvipdfm gftopkluametatex mktexmf rungs xdvi
dvipdfmx gftypeluaotfload-tool mktexpk simpdftex xdvi-xaw
dvipdft inimf luatex mktextfm tex xdvipdfmx
dvipsinitexmakeindexmptopdf texhash
ebb kpseaccessman mtxruntexlua
Do you see that context and context.lua out there, right? That's
only after running tlmgr and installing it, so no bueno, because in
the meantime there's no texmfcnf.lua around
Then again, remember in the current state I actually don't have
texmfcnf.lua for the simple reason that first-setup.sh never provided
it, correct?
So, wwith that in mind and in place, even that context binary from TeX
Live infrastructure as shown before is a known fact that texmfcnf.lua
is nowhere to be found
So let me see if I can copy one from an otherwise fully functional TeX Live
with almost 5g of space taken over and copy it over to this TeX Live
infrastrcutre so
everything checks out in the end
What happens then is not really surprising
If I were to copy over a copy that I found elsewhere over to web2c
of the TeX Live-infrastructure-only installation, this is what happens:
$ context --generate --luatex
mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'
Here we go! Back to point A where we were at before
>
> P.S. It can be a good practice to keep a ConTeXt standalone version
> associated with each project, which can be "frozen" with the project,
> assuring that the sources can always be typeset in the future "as is".
>
> P.P.S. This per-project ./context/ subdirectory can include multiple
> tex/texmf-system-architecture subdirectories and the project shared
> between different machines, all in happy coexistence. (Hans told me a
> while ago that they all use unique luametatex caches.)
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
On 4/11/2023 1:58 AM, Carlos via ntg-context wrote: I'm just following some of the standalone installation instructions as per the wiki alongside a TeX Live installation, but there are a few things that don't add up or I can't seem to add them up :). first, while I was trying to mtxrun --generate it returned /usr/bin/env texlua no such file or directory So I thought heck, perhaps by creating a symbolic link we'll call it a day, but that wasn't enough, nope. That # line will go away or change because per 2023 we assume that the script is run by luametatex and we're in a sort of transition This is is circa 21st century ladies and gentlemen! And tex survived more that 4 decades so ... it operates in an eco system (tds, installations) ... todays fashion is not yesterdays and tomorrows so I thought, alright, since there seems ot be a a problem with texlua, let's also add it to path somehow. i'm not sure what you installed but the stand alone installer installs luametatex / luatex and therefore has luametatex mtxrun -> luametatex context -> luametatex mtxrun.lua context.lua in the same path (the links are stubs, not uncommon in the tex world where they are also used to launch macro packages like latex) it can't be more portable and simple than that, is efficient and works ok unless one wants some different setup, and spend time on that So with that out of the way, we'll move on to the next step and change to a directory and try to call out mtxrun --generate again It returns: > ... But this is the catch. I don't have texmfcnf.lua anymore . Not on the TeX Live installation anyway if that might've ever materialize as a question maybe that was not copied? the fact that we need a configuration and file database is also pretty much the way a tex installation works (with allits resources) If I were to invoke an mtxrun --script cache --erase Of course and going solely by the above the part whenever it says resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/ce/context/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c' wont' find it anywhere because that dir does not exist. should be there with the installer; if one just installs the 'zip' it has to come from elsewhere (like texlive, where actually most lives in texmf-dist) and one has to copy a configuration file to there But remember that earlier, adding bin to path was necessary to avoid /usr/bin/env texlua no such file or directory message But even now while trying to find plain.tex I've come to the conclusion that it needs it or else fails altogether The problem is that I don't have plain.tex though. As a matter of fact the TeX Live installation I currently have, plain tex is nowhere to be seen, heck, not even latex but only a handful set of fmtutil fmtuitl-sys mktexfmt and updmap updmap-sys and the whole remainder of kpathsea but then again this in practice would not even be needed if at all. indeed, context doesn't rely on fmtutil etc In other words, only the TeX Live infrastructure needed which shouldn't be a problem, right? But itis: a problem that is. Besides. The reason I mentioned it is only to serve reference material , but that's it. to recap, mtxrun looks for a texmfcnf.lua (which I don't have) and also for a plain.tex which I don't have either, and also presumably for a contextcnf.lua (which I have) but the script concept is not so smart, and finishes off with a final note that says warning: no lua configuration files found. No shit Sherlock! Of course it can't find it, because it doesn't exist, resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/ce/texmf/web2c' from specification 'home:texmf/web2c' But at this point and without sugar coating it, the standalone installation of context proves to be a chore more problematic than waiting to install over 5gb of TeX Live alone. hm, worked for quite a while for users; and did you try oen from https://www.pragma-ade.com/install.htm The only thing that the installation instructions got right from the start was the part about running the script with all modules. I'll probably… and eventually will try to install the whole TeX Live. But going solely by what the current TeX Live on my machine looks like, , with just the infrastcucture, while anything mtx was dropped like a hot potato really, it's a predicament... not sure what you mean here .. mtxrun was not dropped, tl 2313 just moved on to lmtx which is even less demanding (unless one starts moveing files around in the tex infrastruture and then expects stuff to keep working) -- Systems programmers are the high priests of a low cult. -- R.S. Barton dunno, don't know any of them -- Real computer scientists don't write code. They occasionally tinker with `programming systems', but those are so high level that they hardly count (and rarely count accurately; precision is for app
Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
Hi Carlos, I think that you may be installing the old ConTeXt MkIV distribution instead of the new ConTeXt LMTX. ConTeXt LMTX doesn't distribute "texlua" at all, and running "./install --modules=all" doesn't make sense with LMTX (since the installer can't install modules). From what link did you download your ConTeXt? If it started with "minimals.contextgarden.net", then that's the old ConTeXt; if it started with "lmtx.pragma-ade.com" then it's the new LMTX. The wiki page that you want is https://wiki.contextgarden.net/Installation#Unix All the other wiki pages are outdated. This is just a wild guess, so I may be very wrong here. If this doesn't work, then what do you get when you run type -ap context type -ap luatex type -ap texlua type -ap luametatex /full/path/to/texlive/2023/context --version /full/path/to/context/standalone/context --version ls -la /full/path/to/texlive/2023/context ls -la /full/path/to/context/standalone/context (I'll also add that I have both the ConTeXt and TeX Live versions of "context" installed on Linux, so it's definitely possible.) Thanks, -- Max ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
On Mon, 10 Apr 2023 20:51:58 -0400 (EDT)
Aditya Mahajan via ntg-context wrote:
> Did you source the `setuptex` script, which sets the correct path.
My PATH is set to
PATH=./context/tex/texmf-freebsd-amd64/bin:/home/MyAccount/context/tex/texmf-freebsd-amd64/bin:...
If my current working directory ("./") is a project that contains its
very own subdirectory ./context/, then this is used to typeset the
project. If not, it falls back on my own general standalone
$HOME/context/, and if that does not exist, then it falls back on, say,
a systemwide TeXlive installation.
This is all that is needed to have many versions coexist.
Alan
P.S. It can be a good practice to keep a ConTeXt standalone version
associated with each project, which can be "frozen" with the project,
assuring that the sources can always be typeset in the future "as is".
P.P.S. This per-project ./context/ subdirectory can include multiple
tex/texmf-system-architecture subdirectories and the project shared
between different machines, all in happy coexistence. (Hans told me a
while ago that they all use unique luametatex caches.)
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
On Mon, Apr 10, 2023 at 08:51:58PM -0400, Aditya Mahajan via ntg-context wrote: > On Mon, 10 Apr 2023, Carlos via ntg-context wrote: > > > I'm just following some of the standalone installation instructions > > as per the wiki alongside a TeX Live installation, but there are a > > few things that don't add up or I can't seem to add them up :). > > > > first, while I was trying to mtxrun --generate it returned > > > > /usr/bin/env texlua no such file or directory > > > > So I thought heck, perhaps by creating a symbolic link we'll call it > > a day, but that wasn't enough, nope. > > > > This is is circa 21st century ladies and gentlemen! > > > > so I thought, alright, since there seems ot be a a problem with texlua, > > let's also add it to path somehow. > > Did you source the `setuptex` script, which sets the correct path. > > > So with that out of the way, we'll move on to the next step and change > > to a directory and try to call out mtxrun --generate again > > > > It returns: > > > > mtxrun --generate resolvers | resolving | variable 'SELFAUTOLOC' > > set to '/home/ce/context/bin' resolvers | resolving | variable > > This appears to be the wrong mtxrun binary. You should include the PATH > variable listed as part of the installation. It should point to > `/home/ce/context/texmf-linux-64/bin` or something similar. with texmfcnf.lua and the contextbinary from just hte TeX Live infrastructure there is an interesting conflict with the same ol' same ol' anyhow [2/2, 00:02/02:56] install: context [92021k] running mktexlsr ... done running mktexlsr. running mtxrun --generate ... done running mtxrun --generate. running context --luatex --generate ... done running context --luatex --generate. running updmap-sys ... done running updmap-sys. then context mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' context --luatex --generate mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' same as with context --generate mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' so it's an either or. texmfcnf.lua in place mtxrun would definitely go through but breaks context calls, while without it, a context call is just ostracized to a context --generate --luatex mtx-context | redirect luametatex -> luatex: luatex --luaonly "/opt/texlive/2023/bin/x86_64-linux/mtxrun.lua" --generate --redirected but that's not what I had in mind. mtxrun --script cache --erase mtxrun | unknown script 'cache.lua' or 'mtx-cache.lua' -- Real Programmers think better when playing Adventure or Rogue. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Problems with building texlive/context from its sources
Dear developers, I am/become one of the texlive mantainers on flathub a more or less recent and new approach for establishing a linux packaging format. The flatpak packages are usually build from source and so is the texlive package. You can find it under https://github.com/flathub/org.freedesktop.Sdk.Extension.texlive/tree/branch/22.08 . The file https://github.com/flathub/org.freedesktop.Sdk.Extension.texlive/blob/branch/22.08/org.freedesktop.Sdk.Extension.texlive.yml is the build manifest which lists the files and commands/additional steps needed for the build process. The current build of texlive works well with pdflatex/lualatex/xelatex but with the context part I have some problems. Therefore, I would appreciate any help with the following questions: 1) Is context included in the texlive-20230313* tarballs or do I have to download it in an extra step? 2) If context is included in the texlive-20230313* tarballs, do I have to additionally download luametatex or is luametatex a part of context? 3) If luametatex is via context in the texlive-20230313* tarballs, how do I build it? Sorry for those (perhaps obvious) questions but I have to admit that I find the texlive building process quite confusing. Also, I could not find any installation guide that covers the scenario of building context within a texlive 2023 installation from its sources on linux. Thanks in advance and regards Jakob ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
On Fri, Mar 31, 2023 at 04:40:27PM +0200, Hans Hagen via ntg-context wrote: > On 3/31/2023 1:40 PM, Carlos via ntg-context wrote: > > > > so why not use lucida math fonts? > > > > I have. But only with a couple of math fonts. I don't have all these fonts. > > It really pays off to buy the official lucida opentype package. I'll do that eventually. > > > mkiv lua stats > loaded fonts: 3 files: lucidanewmathitalic.ttf, > > lucidanewmathsymbol.ttf, lucidabrightregular.otf > > mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 6 > > instances, 3 shared in backend, 1 common vectors, 2 common hashes, load > > time 16.733 seconds > > I never heard of these math ones. Did you get these from yandytex (no longer > around) or TUG (the official distributer of lucida opentype math)? Anyway, > as we fine tune math fonts for sure you get suboptimal results (or even > wrong output). Mikael and I put quite a bit of care into lucida opentype > math. > > > I do agree with you in that that loading time is perhaps unacceptable but… > > ... > > You ought to specify that must be only after subsequent callbacks. I just > > tried it with a one liner file of \setupbodyfont[lucida] and (looking > > around in disbelief) it took a whooping ahem > > fonts > names > skipped files: 164 > > fonts > names > duplicate files : 164 > > fonts > names > total scan time : 16.487 seconds > > I have no clue, unless that relates to your font path including some home > dir which gets scanned every time for whatever reason and that has tens of > thousands of files. I can process the 350+ page luametatex manual twice in > these 16 seconds and that one loads quite some (also math) fonts and my > laptop is not a fancy 2023 one > > > before it produced even error messages. > > > > beating me for 2 seconds. Great. And then it restricted my freedom by saying > > > > «Sorry, but I can't typeset math unless various parameters have been set. > > This is > > normally done by loading special math fonts into the math family slots. > > Your font > > set is lacking at least the parameter mentioned earlier.» > > that's pretty clear: you don't load a math font at all, maybe some text font > pretending it is math > > > Sorry, but sorry doesn't cut it here. > > it does: no proper math font found so reason to complain > > > I guess it must have been referring to \strc_formulas_place_number > > \strc_formulas_flush_number \dostarttagged \t!formulacontent \empty > > \dotagregisterformula \c_strc_formulas_n \csname \e!stop \formulaparameter > > \c!alternative \v!formula \endcsname > > dunno, that's numbering, not math > > > Okay. So I tried another file. This time around with only > > > > \setupbodyfont[lucida] > > > > \starttext > > $ test $ > > \stoptext > > > > and then the output message was «Somewhere in the math formula just ended, > > you used the stated character from an > > undefined font family. For example, plain TeX doesn't allow \it or \sl in > > subscripts. Proceed, and I'll try to forget that I needed that character.» > > > > There's not even a fallback to cmr or any other font. > > sure, why should it, you want lucida so better quit with an error than > kicking in some font; actually cmr math fonts have been obsoleted for way > over a decade by latin modern math fonts in 32 bit font engines I was actually thinking to ask you about that, and by falling back to cmr math font that perhaps would expedite loading time along the way. Thank you for the info on that last sentence. I didn't know. > > > There was not even a personalized touch in the output. That message sounds > > like one of these new GPT-chat features. Dry. When I read that «Proceed, > > and I'll try to forget it…» part the first thing I thought was: yeah, I'll > > proceed by removing that file altogether and you'll forget it for sure . > > that message is part of 'reference tex the program' for over 40 years so if > chatgpt would come up with it, it would do so by having parsed plenty of tex > sources instead of inventing it (and when it comes to answering tex related > questions chargpt is pretty unreliable, but that's another topic) > > > But instaed I looked at it and though to myself «how much has changed?!» In > > plain TeX (I have forgotten it a bit) but I can still type > > > \par > > > $test$ > > > \end > > > > and it'll produce a dvi file in return. > > a lot has changed: opentyp
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
On 3/31/2023 1:40 PM, Carlos via ntg-context wrote: so why not use lucida math fonts? I have. But only with a couple of math fonts. I don't have all these fonts. It really pays off to buy the official lucida opentype package. mkiv lua stats > loaded fonts: 3 files: lucidanewmathitalic.ttf, lucidanewmathsymbol.ttf, lucidabrightregular.otf mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 6 instances, 3 shared in backend, 1 common vectors, 2 common hashes, load time 16.733 seconds I never heard of these math ones. Did you get these from yandytex (no longer around) or TUG (the official distributer of lucida opentype math)? Anyway, as we fine tune math fonts for sure you get suboptimal results (or even wrong output). Mikael and I put quite a bit of care into lucida opentype math. I do agree with you in that that loading time is perhaps unacceptable but… > ... You ought to specify that must be only after subsequent callbacks. I just tried it with a one liner file of \setupbodyfont[lucida] and (looking around in disbelief) it took a whooping ahem fonts > names > skipped files: 164 fonts > names > duplicate files : 164 fonts > names > total scan time : 16.487 seconds I have no clue, unless that relates to your font path including some home dir which gets scanned every time for whatever reason and that has tens of thousands of files. I can process the 350+ page luametatex manual twice in these 16 seconds and that one loads quite some (also math) fonts and my laptop is not a fancy 2023 one before it produced even error messages. beating me for 2 seconds. Great. And then it restricted my freedom by saying «Sorry, but I can't typeset math unless various parameters have been set. This is normally done by loading special math fonts into the math family slots. Your font set is lacking at least the parameter mentioned earlier.» that's pretty clear: you don't load a math font at all, maybe some text font pretending it is math Sorry, but sorry doesn't cut it here. it does: no proper math font found so reason to complain I guess it must have been referring to \strc_formulas_place_number \strc_formulas_flush_number \dostarttagged \t!formulacontent \empty \dotagregisterformula \c_strc_formulas_n \csname \e!stop \formulaparameter \c!alternative \v!formula \endcsname dunno, that's numbering, not math Okay. So I tried another file. This time around with only \setupbodyfont[lucida] \starttext $ test $ \stoptext and then the output message was «Somewhere in the math formula just ended, you used the stated character from an undefined font family. For example, plain TeX doesn't allow \it or \sl in subscripts. Proceed, and I'll try to forget that I needed that character.» There's not even a fallback to cmr or any other font. sure, why should it, you want lucida so better quit with an error than kicking in some font; actually cmr math fonts have been obsoleted for way over a decade by latin modern math fonts in 32 bit font engines There was not even a personalized touch in the output. That message sounds like one of these new GPT-chat features. Dry. When I read that «Proceed, and I'll try to forget it…» part the first thing I thought was: yeah, I'll proceed by removing that file altogether and you'll forget it for sure . that message is part of 'reference tex the program' for over 40 years so if chatgpt would come up with it, it would do so by having parsed plenty of tex sources instead of inventing it (and when it comes to answering tex related questions chargpt is pretty unreliable, but that's another topic) But instaed I looked at it and though to myself «how much has changed?!» In plain TeX (I have forgotten it a bit) but I can still type > \par > $test$ > \end and it'll produce a dvi file in return. a lot has changed: opentype math, unicode, more demands but indeed there is nothing against using plain tex with cmr and dvi fonts if that suits well; and plain tex will always be faster than context (or latex) just like pdftex with 8 bit fonts is faster than luatex with 32 bit fonts (with luametatex sitting in between wrt performance) anyway, i bet that if you want to use lucida with plain you also have to do some work and it will complain as loud as luametatex when th efont parameters are not set 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 / htt
Re: [NTG-context] tikz error upgrading to texlive version (artix)
On 3/30/2023 11:56 PM, Xavier B. via ntg-context wrote:
Thanks, Max, for finding the problem. It is related to two more bugs:
https://github.com/pgf-tikz/pgf/issues/990
and
https://github.com/pgf-tikz/pgf/issues/958
Perhaps Hans or other people could help tikz staff to do the pending and
definitive solution.
It's annoying to have to put workarrounds in production documents.
There is just a glad mkiv user ;-)
\usemodule[tikz]
\starttext
Hello World.
\stoptext
works ok here
\usemodule[tikz]
\starttext
\starttikzpicture
\node [left color=red, right color=yellow] {Hello};
\stoptikzpicture
\stoptext
fails on
\setbox \pgfutil@tempboxa =\hbox dir
TLT to\pgfmathresult pt{\vbox
because we don't have 'dir TLT' in luametatex (and more engines don't so
i would expect tikz to have some abstraction for that)
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] tikz error upgrading to texlive version (artix)
If I run the minimal context distro
[https://wiki.contextgarden.net/Installation], I get this:
$ context a.tex
resolvers | formats | executing runner 'run luametatex format':
/home/xan/bin/context-minimal/tex/texmf-linux-64/bin/luametatex
--jobname="./a.tex"
--fmt=/home/xan/bin/context-minimal/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt
--lua=/home/xan/bin/context-minimal/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui
--c:currentrun=1 --c:fulljobname="./a.tex" --c:input="./a.tex"
--c:kindofrun=1 --c:maxnofruns=9
--c:texmfbinpath="/home/xan/bin/context-minimal/tex/texmf-linux-64/bin"
job > passes > version mismatch: 1.32 <> 1.33
system >
system > ConTeXt ver: 2023.03.20 17:07 LMTX fmt: 2023.3.30 int:
english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name
'/home/xan/bin/context-minimal/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source> level 1, order 1, name
'/home/xan/bin/context-minimal/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './a', input './a.tex', result './a'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 2, name './a.tex'
modules > 'tikz' is loaded
open source > level 2, order 3, name
'/home/xan/bin/context-minimal/tex/texmf-context/tex/context/modules/mkxl/m-tikz.mkxl'
runtime error : input file 'pgfutil-common.tex' is not found, quitting
mtx-context | fatal error: return code: 1
So, the problem is not the package or the distro, it's something more basic
which causes the error.
Thanks in advance,
On Thu, 30 Mar 2023 20:52:51 +0200
"Xavier B." ha escrit:
> Hi,
>
> I use artix linux (a fork of arch with systemd alternative init systems).
> During the texlive package, I get this error:
>
> return {
>
> ["filename"]="/usr/share/texmf-dist/tex/generic/pgf/basiclayer/pgfcorepoints.code.tex",
> ["lastcontext"]="\n \n \\inaccessible \n \n
> \"\n\\pgfmath@catcodes ->\\catcode `\\==12 \\catcode `\\,=12 \\catcode
> `\\|=12 \\catcode `\\&=12 \\let \"\n
> \\pgfmath@char@quote \n\\pgfmathparse
> ->\\begingroup \\pgfmath@catcodes \n
> \\pgfmath@quickparsefalse \\ifpgfmathfloat \\let \\pgfmath@parse@next
> =\\pgfmathfloatparsenumber \\else \\let \\pgfmath@parse@next =\\pgfmathparse@
> \\fi \\pgfmath@parse@next \n \\pgfmathparse \n
> {1cm}\\ifpgfmathmathunitsdeclared \\pgf@x \\pgfmathresult mu\\relax \\else
> \\pgf@x \\pgfmathresult pt\\relax \\fi \n\\pgfmath@next #1#2->#2\n
> \n...\nl.926 \\pgfsetxvec{\\pgfpoint{1cm}{0cm}}\n
> ",
> ["lastluaerror"]="?",
> ["lasttexerror"]="! Missing control sequence inserted",
> ["linenumber"]=926,
> ["offset"]=10,
> }
>
> I simply run context to this file:
>
> \usemodule[tikz]
>
> \starttext
> {\bf a} \tikz (0,0) -- (1,0);
> \stoptext
>
> My version of context is:
>
> [xan@coronari ~]$ context --version
> mtx-context | ConTeXt Process Management 1.04
> mtx-context |
> mtx-context | main context file:
> /usr/share/texmf-dist/tex/context/base/mkiv/context.mkiv
> mtx-context | current version: 2023.03.10 12:15
> mtx-context | main context file:
> /usr/share/texmf-dist/tex/context/base/mkxl/context.mkxl
> mtx-context | current version: 2023.03.10 12:15
>
> My packages are:
>
> $ pacman -Qs texlive
> local/texlive-bibtexextra 2023.66579-1 (texlive-most)
> TeX Live - Additional BibTeX styles and bibliography databases
> local/texlive-bin 2023.66539-1
> TeX Live binaries
> local/texlive-core 2023.66587-1 (texlive-most)
> TeX Live core distribution
> local/texlive-pictures 2023.66549-1 (texlive-most)
> TeX Live - Packages for drawings graphics
> local/texlive-publishers 2023.66550-1 (texlive-most)
> TeX Live - LaTeX classes and packages for specific publishers
> local/texlive-science 2023.66461-1 (texlive-most)
> TeX Live - Typesetting for mathematics, natural and computer sciences
>
>
>
> I also posted the message in Artix mailing list
> [https://lists.artixlinux.org/archives/artix-general/2023-March/000977.html]
>
>
> Thanks in advance,
&g
Re: [NTG-context] Spacing problem around decimal point
Hi all, I d/l'ed that binary, replaced the TeXlive version (which is dated March 11, even though I just updated texlive 5 minutes ago) and, lo and behold, the PDF now looks like it should. So from my point of view, that particular issue is resolved. Sorry about your issues with Mac security. I have this feeling that Apple is slowly iterating towards a state where they sell you an expensive computer with a beautiful acrylic and polished stainless steel stand and ask you just to admire it, but don't touch it. :-) Jim On Tue, Mar 28, 2023 at 14:56 (-0600), Gavin via ntg-context wrote: > Hi Hans, Jim, Bruce, et.al. > Han’s asked me >> can you pick up a binary from: >> https://dl.contextgarden.net/build/luametatex/work/ >> and test it? > Maybe. I picked up the binary, but testing it is not quite as easy as it > might be due to the MacOS security settings. I’ll see what I can do, but I > know very little about Unix/Darwin. > Since this appears to be an issue across multiple platforms, I’d welcome > anyone else checking the new binary. (Thanks, Günter!) > Best, > Gavin > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > maillist : ntg-context@ntg.nl / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > ___ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Spacing problem around decimal point
> On 28 Mar 2023, at 21:56, Gavin via ntg-context wrote:
>
> Hi Hans, Jim, Bruce, et.al.
>
> Han’s asked me
>
>> can you pick up a binary from:
>>
>> https://dl.contextgarden.net/build/luametatex/work/
>>
>> and test it?
>
> Maybe. I picked up the binary, but testing it is not quite as easy as it
> might be due to the MacOS security settings. I’ll see what I can do, but I
> know very little about Unix/Darwin.
>
> Since this appears to be an issue across multiple platforms, I’d welcome
> anyone else checking the new binary. (Thanks, Günter!)
The x86_64-darwinlegacy from that download link version has fixed the problem
on the Mac. Thank-you all involved.
\starttext
\startformula
v = \frac{1.32}{1.41} = 0.935
\stopformula
\stoptext
gives the attached.
—
Bruce Horrocks
Hampshire, UK
tt.pdf
Description: Adobe PDF document
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Spacing problem around decimal point
Hi Hans, Jim, Bruce, et.al. Han’s asked me > can you pick up a binary from: > > https://dl.contextgarden.net/build/luametatex/work/ > > and test it? Maybe. I picked up the binary, but testing it is not quite as easy as it might be due to the MacOS security settings. I’ll see what I can do, but I know very little about Unix/Darwin. Since this appears to be an issue across multiple platforms, I’d welcome anyone else checking the new binary. (Thanks, Günter!) Best, Gavin ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Text editors
HI!
I’ve been using emacs and played around with configuration and finally found a
good and very useful setup using LMTX installation.
Also I’ve customized with help from YAsnippet my own snippets så it goes very
fast.
Below I have a setup on my macos that uses
- ConTeXt LMTX
- emacs-lisp setting in ~/.emacs.d/init.el
- customized setting for preview with Skim pdf reader
- YASnippet snippets on my dropbox cloudstoring so I can use it on several
computers and has a macro syntax easy to learn.
- Bind-keys for fast build and preview on two pane "side by side editor and
previewer" in "TeXshop style”.
C-å Build document and C-c C-v for fast preview in Skim
Something to start playing with below to put in your init.el file
;; This is for getting preferred position and size of the emacs editor frame
(add-to-list 'default-frame-alist '(top . 25))
(add-to-list 'default-frame-alist '(left . 1))
(add-to-list 'default-frame-alist '(height . 56))
(add-to-list 'default-frame-alist '(width . 120))
;; For solving path issues install: do M-x package-install RET
exec-path-from-shel RETl
(when (memq window-system '(mac ns x))
(exec-path-from-shell-initialize))
;; For configuring context
(add-to-list 'auto-mode-alist '("\\.tex\\'" . context-mode))
(eval-after-load 'tex '(add-to-list 'TeX-command-list
'("LuaMetaTeX"
"mtxrun --autogenerate --script context %t" TeX-run-command nil
(context-mode) :help "Run LuaMetaTeX")))
(defun myctx ()
"Saves the current buffer and runs ConTeXt, all with no prompts or further
interaction."
(interactive)
(save-buffer)
(TeX-command "LuaMetaTeX" 'TeX-master-file -1))
;; (add-hook 'ConTeXt-mode-hook 'turn-on-smartparens-strict-mode)
(add-hook 'ConTeXt-mode-hook (lambda () (define-key ConTeXt-mode-map (kbd
"C-å") 'myctx)))
(setq TeX-output-view-style '("^pdf$" "." "open -a Skim.app %o"))
(setq TeX-view-program-list
'(("Skim" "open -a Skim.app %o")
))
(add-hook 'ConTeXt-mode-hook (lambda () (setq TeX-view-program-selection
'((output-pdf "Skim")
;; YASnippet config
(use-package yasnippet
:config
(setq yas-snippet-dirs '("~/Dropbox/filer/system/emacsgrejer/snippets"))
(yas-global-mode 1)
(setq yas/triggers-in-field t))
Hope this helps and gives some inspiration to get started if you choose emacs
/Jan-Erik
> 26 mars 2023 kl. 10:22 skrev Alexandre Christe via ntg-context
> :
>
> Dear ConTeXt users,
>
> I'm wondering what kind of typesetting system / syntax highlighting /
> completion you're using.
>
> I've been using myself the simple_Context package for SublimeText which I
> scavenged a while ago before it was made unavailable (I wanted to attach but
> it's too big for the list). But it's sort of a dead-end.
>
> Open to anything from vim/neovim to emacs or more exotic. Maybe it would be
> nice to show the config. (And yes I've seen the Wiki page
> https://wiki.contextgarden.net/Text_Editors but I've the feeling some content
> is outdated.)
>
> Thanks in advance,
> Alex
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
On Sat, Mar 25, 2023 at 09:26:36PM +0100, Hans Hagen via ntg-context wrote: > On 3/25/2023 8:55 PM, Carlos via ntg-context wrote: > > Hello list: > > > > This is under a fresh TeXLive installation. Sort as to put aside any > > texlive prepackaged issues. > > > > And the followign lines is the output of the error I've been having with > > the call of context on a recent texlive installation by both mtxrun > > --generate and luatools --generate right after. > > there i no need to use luatools (it's something old from the early days) > > what does > > mtxrun --generate --verbose > > report (whre does it fail) > > > 57 \starttext > > 58 > > 59 \usetypescriptfile[type-lucida] > > 60 \usetypescript[Lucida][texnansi] > > 61 >> \setupbodyfont[MyLucida, 10pt] > > 62 > > 63 \input zapf > > 64 > > 65 \input tufte > > fwiw, lucida type one makes no sense any more because the opentype version > is way better (and in the updated math setup in lmtx we didn't even look at > it) > Hans, your advice for using otf fonts worked. Thanks. system > lua > compiling '/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tma' into '/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tmd' system > lua > dumping '/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tma' into '/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tmd' stripped Not how I wanted it originally as in Void Linux with texnansi encoding and a TeXLive2021 prepackaged mkiv lua stats > loaded fonts: 4 files: lucidabrightregular.otf, lucidasansregular.otf, latinmodern-math.otf, lmroman12-regular.otf mkiv lua stats > font engine: otf 3.113, afm 1.513, tfm 1.000, 12 instances, 6 shared in backend, 4 common vectors, 2 common hashes, load time 0.413 seconds mkiv lua stats > used platform: linux-64, type: unix, binary subtree: usr mkiv lua stats > used engine: luatex version: 1.13, functionality level: 7418, banner: this is luatex, version 1.13.0 (tex live 2021/voidlinux) mkiv lua stats > used hash slots: 48145 of 65536 + 20 mkiv lua stats > lua properties: engine: lua 5.3, used memory: 158 MB, ctx: 158 MB, max: unknown MB, hash chars: min(64,40), symbol mask: utf (τεχ) Or with otf under Alpine. but yes. otf rather than ttf backend > fonts > width units in 'SGVYNL+LucidaBright-Italic' are 2048, forcing 1000 instead backend > fonts > width units in 'QRVECH+LucidaBright' are 2048, forcing 1000 instead system > start used files system > text: atestinlucida-OTF system > stop used files system > start used files > > Is LuaLaTeX behaving the same way? > > > > Answer: no. > > no surprise because it doesn't use the same setup > > what cache path does > > mtxrun --variables > > report > > 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 / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > ___ -- The New Testament offers the basis for modern computer coding theory, in the form of an affirmation of the binary number system. But let your communication be Yea, yea; nay, nay: for whatsoever is more than these cometh of evil. -- Matthew 5:37 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Spacing problem around decimal point
I also get the incorrect spacing on a Mac.
system > ConTeXt ver: 2023.03.20 17:07 LMTX fmt: 2023.3.22 int:
english/english
> On 26 Mar 2023, at 22:16, Jim via ntg-context wrote:
>
> Hi all,
>
> Regrettably, I see the same problem and Gavin.
>
> I am using TeXlive 2023 on Slackware64 15.0, for what that is worth.
>
>
>Jim
>
> On Sun, Mar 26, 2023 at 17:36 (+0200), Günter Kolousek via ntg-context wrote:
>
>
>> Hi,
>
>> I can confirm that the x64_64-linux from
>
>> https://dl.contextgarden.net/build/luametatex/work/
>
>> version works correctly. So, no excess spaces around the
>> decimal points at all.
>
>> HTH
>> Günter
>
>> Hans Hagen via ntg-context @ 2023-03-26 13:22 +02:
>
>>> On 3/26/2023 4:20 AM, Gavin via ntg-context wrote:
>>>> Hi List,
>>>> I’m getting strange spaces around some decimal points after a clean
>>>> LMTX
>>>> install. MWE:
>>>> \starttext
>>>> \startformula
>>>> v = \frac{1.32}{1.41} = 0.935
>>>> \stopformula
>>>> \stoptext
>>>> This produces the result attached below. The 1.32 looks fine, but
>>>> the next two
>>>> numbers have excess space around the decimal point. Adding the line
>>>> \showmakeup[mathglue] %\mathspacingmode=1
>>>> to the preamble reveals that the second and third decimal points are
>>>> being
>>>> treated as binary operators. It’s very strang. Are others getting
>>>> this?
>>> can you pick up a binary from:
>
>>> https://dl.contextgarden.net/build/luametatex/work/
>
>>> and test it?
>
>>> Hans
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___
—
Bruce Horrocks
Hampshire, UK
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Spacing problem around decimal point
Hi all,
Regrettably, I see the same problem and Gavin.
I am using TeXlive 2023 on Slackware64 15.0, for what that is worth.
Jim
On Sun, Mar 26, 2023 at 17:36 (+0200), Günter Kolousek via ntg-context wrote:
> Hi,
> I can confirm that the x64_64-linux from
> https://dl.contextgarden.net/build/luametatex/work/
> version works correctly. So, no excess spaces around the
> decimal points at all.
> HTH
> Günter
> Hans Hagen via ntg-context @ 2023-03-26 13:22 +02:
>> On 3/26/2023 4:20 AM, Gavin via ntg-context wrote:
>>> Hi List,
>>> I’m getting strange spaces around some decimal points after a clean
>>> LMTX
>>> install. MWE:
>>> \starttext
>>> \startformula
>>> v = \frac{1.32}{1.41} = 0.935
>>> \stopformula
>>> \stoptext
>>> This produces the result attached below. The 1.32 looks fine, but
>>> the next two
>>> numbers have excess space around the decimal point. Adding the line
>>>\showmakeup[mathglue] %\mathspacingmode=1
>>> to the preamble reveals that the second and third decimal points are
>>> being
>>> treated as binary operators. It’s very strang. Are others getting
>>> this?
>> can you pick up a binary from:
>> https://dl.contextgarden.net/build/luametatex/work/
>> and test it?
>> Hans
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Spacing problem around decimal point
Hi,
I can confirm that the x64_64-linux from
https://dl.contextgarden.net/build/luametatex/work/
version works correctly. So, no excess spaces around the
decimal points at all.
HTH
Günter
Hans Hagen via ntg-context @ 2023-03-26 13:22 +02:
On 3/26/2023 4:20 AM, Gavin via ntg-context wrote:
Hi List,
I’m getting strange spaces around some decimal points after a
clean LMTX
install. MWE:
\starttext
\startformula
v = \frac{1.32}{1.41} = 0.935
\stopformula
\stoptext
This produces the result attached below. The 1.32 looks fine,
but the next two
numbers have excess space around the decimal point. Adding the
line
\showmakeup[mathglue] %\mathspacingmode=1
to the preamble reveals that the second and third decimal
points are being
treated as binary operators. It’s very strang. Are others
getting this?
can you pick up a binary from:
https://dl.contextgarden.net/build/luametatex/work/
and test it?
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 /
https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Spacing problem around decimal point
On 3/26/2023 4:20 AM, Gavin via ntg-context wrote:
Hi List,
I’m getting strange spaces around some decimal points after a clean LMTX
install. MWE:
\starttext
\startformula
v = \frac{1.32}{1.41} = 0.935
\stopformula
\stoptext
This produces the result attached below. The 1.32 looks fine, but the next two
numbers have excess space around the decimal point. Adding the line
\showmakeup[mathglue] %\mathspacingmode=1
to the preamble reveals that the second and third decimal points are being
treated as binary operators. It’s very strang. Are others getting this?
can you pick up a binary from:
https://dl.contextgarden.net/build/luametatex/work/
and test it?
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
On Sat, Mar 25, 2023 at 09:45:25PM +0100, Hans Hagen via ntg-context wrote: > On 3/25/2023 8:55 PM, Carlos via ntg-context wrote: > > > ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: > > in upvalue 'walk_tree' > Maybe your OSFONTDIR is pointing to empty. Does Good call. Thank you for the reminder Hans. But no. That variable was set long ago . Even appended it to both the bash initialization file and also under /etc/profile (just in case here). Alpine uses ash so shells must be changed > > mtxrun --script font --reload > fonts | names | 3092 afm files checked, okay fonts | names | identifying tree font files with suffix 'AFM' fonts | names | scanning path '/home/ce/.texlive2023/texmf-config' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/home/ce/texmf' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-config' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-var' for AFM files fonts | names | 0 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-local' for AFM files fonts | names | 24 AFM files checked, okay fonts | names | scanning path '/usr/local/texlive/2023/texmf-dist' for AFM files fonts | names | 3092 AFM files checked, okay fonts | names | 6232 tree files identified, 14 skipped, 14 duplicates, 6218 hash entries added, runtime 8.458 seconds fonts | names | identifying system font files with suffix 'otf' fonts | names | variable 'OSFONTDIR' specifies path '/home/ce' fonts | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts' fonts | names | globbing path '/home/ce/**.otf' lua error : function call: /usr/local/texlive/2023/bin/x86_64-linuxmusl/mtxrun.lua:649: cannot open /home/ce/cache/headers/imaps:@gmail@imap.gmail.com/[Gmail]/.: Permission denied Recall that the other folders owned by root had to be moved out of the way So it seems it wasn't enough, nope. Now it wants access elsewhere bottom line: it wants root permissions or else fails flat out Even with sudo privileges the best it can do is: resolvers | formats | executing runner 'run luametatex format': /usr/local/texlive/2023/bin/x86_64-linuxmusl/luametatex --jobname="./atestinlucida-context-55.mkiv" --fmt=/usr/local/texlive/2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/formats/luametatex/cont-en.fmt --lua=/usr/local/texlive/2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/formats/luametatex/cont-en.lui --c:currentrun=1 --c:fulljobname="./atestinlucida-context-55.mkiv" --c:input="./atestinlucida-context-55.mkiv" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/usr/local/texlive/2023/bin/x86_64-linuxmusl" system > system > ConTeXt ver: 2023.03.10 12:15 LMTX fmt: 2023.3.25 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 1, order 1, name '/usr/local/texlive/2023/texmf-dist/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source> level 1, order 1, name '/usr/local/texlive/2023/texmf-dist/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname './atestinlucida-context-55', input './atestinlucida-context-55.mkiv', result './atestinlucida-context-55' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './atestinlucida-context-55.mkiv' fonts > preloading latin modern fonts (second stage) mathematics > tweak > 'LatinModernMath-Regular', size 6, math size 3, version 'Version 1.959' found, version 'Version 1.958' expected fonts > 'fallback modern rm 12pt' is loaded open source > level 2, order 3, name '/usr/local/texlive/2023/texmf-dist/tex/context/fonts/mkiv/type-imp-lucida.mkiv' close source> level 2, order 3, name '/usr/local/texlive/2023/texmf-dist/tex/context/fonts/mkiv/type-imp-lucida.mkiv' fonts > defining > forced type 'otf' of 'LucidaBrightOT' not found fonts > defining > unable to define 'LucidaBrightOT.otf' as 'MyLucida-10pt-rm-tf-0--0' open source > level 2, order 4, name 'zapf.tex' close source> level 2, order 4, name 'zapf.tex' open source > level 2, order 5, name 'tufte.tex' close source> level 2, order 5, name 'tufte.tex' backend > xmp > using file '/usr/local/texlive/2023/texmf-dist/tex/context/bas
Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
On Sat, Mar 25, 2023 at 09:26:36PM +0100, Hans Hagen via ntg-context wrote:
> On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
> > Hello list:
> >
> > This is under a fresh TeXLive installation. Sort as to put aside any
> > texlive prepackaged issues.
> >
> > And the followign lines is the output of the error I've been having with
> > the call of context on a recent texlive installation by both mtxrun
> > --generate and luatools --generate right after.
>
> there i no need to use luatools (it's something old from the early days)
>
> what does
>
> mtxrun --generate --verbose
It doesn't.
This is under the same folder in question. Recall I moved the other group owned
files elsewhere out of the way
This is the output
system | lua | compiling
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/73630a261795d9c53610a28af4550cbc.lua'
into
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/73630a261795d9c53610a28af4550cbc.lud'
system | lua | dumping
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/73630a261795d9c53610a28af4550cbc.lua'
into
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/73630a261795d9c53610a28af4550cbc.lud'
stripped
resolvers | caching | 'files' compiled to
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/73630a261795d9c53610a28af4550cbc.lud'
resolvers | resolving | saving tree 'selfautoparent:texmf-dist'
resolvers | caches | hashing tree 'selfautoparent:texmf-dist', hash
'929f6dbc83f6d3b65dab91f1efa4aacb'
resolvers | caching | preparing 'files' for 'selfautoparent:texmf-dist'
resolvers | caching | category 'files', cachename
'selfautoparent:texmf-dist' saved in
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/929f6dbc83f6d3b65dab91f1efa4aacb.lua'
system | lua | compiling
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/929f6dbc83f6d3b65dab91f1efa4aacb.lua'
into
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/929f6dbc83f6d3b65dab91f1efa4aacb.lud'
system | lua | dumping
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/929f6dbc83f6d3b65dab91f1efa4aacb.lua'
into
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/929f6dbc83f6d3b65dab91f1efa4aacb.lud'
stripped
resolvers | caching | 'files' compiled to
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/929f6dbc83f6d3b65dab91f1efa4aacb.lud'
mtxrun |
mtxrun | elapsed lua time: 4.327 seconds
> > 58
> > 59 \usetypescriptfile[type-lucida]
> > 60 \usetypescript[Lucida][texnansi]
> > 61 >> \setupbodyfont[MyLucida, 10pt]
> > 62
> > 63 \input zapf
> > 64
> > 65 \input tufte
>
> fwiw, lucida type one makes no sense any more because the opentype version
> is way better (and in the updated math setup in lmtx we didn't even look at
> it)
>
It goes throught without a problem under Void Linux. pfm and afm files on this
one are right there in place. On this one: Alpine. It's a problem. or a given
:) depending how one looks at it.
> > Is LuaLaTeX behaving the same way?
> >
> > Answer: no.
>
> no surprise because it doesn't use the same setup
>
> what cache path does
>
> mtxrun --variables
>
> report
mtxrun --variables
resolvers | lists | AFMFONTS
resolvers | lists | env: unset
resolvers | lists | var: AFMFONTS
resolvers | lists | exp: .\{home:.texlive2023/texmf-config, home:texmf,
!!selfautoparent:texmf-config, !!selfautoparent:texmf-var,
!!selfautoparent:texmf-project, !!selfautoparent:texmf-fonts,
!!selfautoparent:texmf-local, !!selfautoparent:texmf-dist}/fonts/{data,
afm}//\/home/ce\/usr/share/fonts
resolvers | lists | res: .\{/home/ce/.texlive2023/texmf-config,
/home/ce/texmf, !!/usr/local/texlive/2023/texmf-config,
!!/usr/local/texlive/2023/texmf-var, !!/usr/local/texlive/2023/texmf-project,
!!/usr/local/texlive/2023/texmf-fonts, !!/usr/local/texlive/2023/texmf-local,
!!/usr/local/texlive/2023/texmf-dist}/fonts/{data,
afm}//\/home/ce\/usr/share/fonts
resolvers | lists | BIBINPUTS
resolvers | lists | env: unset
resolvers | lists | var: BIBINPUTS
resolvers | lists | exp: .\{home:.texlive2023/texmf-config, home:texmf,
!!selfautoparent:texmf-config, !!selfautoparent:texmf-var,
!!selfautoparent:texmf-project, !!selfautoparent:texmf-font
Re: [NTG-context] building from source
Hans Hagen via ntg-context writes: > On 3/21/2023 12:14 PM, Rainer J.H. Brandt via ntg-context wrote: > > Dear Context developers, > > > > I want to build Context MkXL from source and use that. I went to the [...] > First define 'build from source'. The lmtx (mkxl) installation can be Building from source is the production of executables from source code files, using the appropriate tools for the chosen type of source code, e.g. compilers, linkers, and other build tools like GNU autotools, make, cmake, or other build mechanisms. With regard to complete software packages, the process usually also takes care of moving other support files to where they are expected at run-time. (Coming from LaTeX, I would expect e.g. formats, fonts, style files etc.) > installed using an installer. If there is not one for the platform one > uses, then one can download the cont-lmt zip and build the binary in > /source/luametatex usign the build.sh script in there. Thanks. That's the first step of what I was looking for. Using "bash build.sh", the build succeeded. The output gives hints about what to put where. I'll see if I can turn it into something that resembles what you offer via the installer packages. Thanks, Rainer ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] building from source
On 3/21/2023 12:14 PM, Rainer J.H. Brandt via ntg-context wrote: Dear Context developers, I want to build Context MkXL from source and use that. I went to the download page http://www.pragma-ade.com/download-1.htm and downloaded the 2023-03-20 version: http://www.pragma-ade.com/context/latest/cont-tmf.zip This contains README.adoc which tells me that information can be found on https://wiki.contextgarden.net. I don't find any further information about building from source, either in the dowloaded material, or on the wiki or the pragma-ade.com site. What am I overlooking? First define 'build from source'. The lmtx (mkxl) installation can be installed using an installer. If there is not one for the platform one uses, then one can download the cont-lmt zip and build the binary in /source/luametatex usign the build.sh script in there. 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] update
Hi,
I updated LMTX. Most improvements are in 'math' as Mikael and I keep
mailing down some details that bother us. We also have some updates in
the math fonts that Daniel Flipo maintains so the repertoire of
alternatives with all-right math support grows.
As a side note: lmtx installs nicely on my android (12) phone (userland
ubuntu) and luametatex compiles nicely from source (as it's aarch64) in
about a minute. No decent editor to text real documents but who knows
what a properly dockable (linux supporting) phone can do in a few years.
A simple
\starttext \dorecurse{1000}{\samplefile{tufte}\par} \stoptext
runs at over 55 pps (85 pps on my laptop). Making a format takes 4
seconds (second time, after caching, which is about twice the time my
laptop takes).
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Description together with itemize, luametatex
Am Montag, 6. März 2023, 14:34:28 CET schrieb Aditya Mahajan via ntg-context:
> On Mon, 6 Mar 2023, Gerion Entrup via ntg-context wrote:
>
> > Hi,
> >
> > I'm trying to use a description environment in conjunction with an
> > itemize with the latest luametatex. Is this supposed to work?
> >
> > Here is an MWE:
> > ```
> > \definedescription[desc][headstyle=bold]
> >
> > \starttext
> > Foo
> >
> > \desc{Some title} Some text
> > \startitemize
> > \item Some item
> > \stopitemize
> >
> > \stoptext
>
> Use \startdesc ... \stopdesc
>
> \definedescription[desc][headstyle=bold]
>
> \starttext
> Foo
>
> \startdesc[title={Some title}]
> Some text
> \startitemize
> \item Some item
> \stopitemize
> \stopdesc
>
> \stoptext
That worked. Thank you!
signature.asc
Description: This is a digitally signed message part.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Description together with itemize, luametatex
On Mon, 6 Mar 2023, Gerion Entrup via ntg-context wrote:
> Hi,
>
> I'm trying to use a description environment in conjunction with an
> itemize with the latest luametatex. Is this supposed to work?
>
> Here is an MWE:
> ```
> \definedescription[desc][headstyle=bold]
>
> \starttext
> Foo
>
> \desc{Some title} Some text
> \startitemize
> \item Some item
> \stopitemize
>
> \stoptext
Use \startdesc ... \stopdesc
\definedescription[desc][headstyle=bold]
\starttext
Foo
\startdesc[title={Some title}]
Some text
\startitemize
\item Some item
\stopitemize
\stopdesc
\stoptext
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Description together with itemize, luametatex
Hi,
I'm trying to use a description environment in conjunction with an
itemize with the latest luametatex. Is this supposed to work?
Here is an MWE:
```
\definedescription[desc][headstyle=bold]
\starttext
Foo
\desc{Some title} Some text
\startitemize
\item Some item
\stopitemize
\stoptext
```
This currently fails with:
```
resolvers | formats | executing runner 'run luametatex format':
/home/gerion/context/tex/texmf-linux-64/bin/luametatex --jobname="./test.tex"
--fmt=/home/gerion/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt
--lua=/home/gerion/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui
--c:currentrun=1 --c:fulljobname="./test.tex" --c:input="./test.tex"
--c:kindofrun=1 --c:maxnofruns=9
--c:texmfbinpath="/home/gerion/context/tex/texmf-linux-64/bin"
system >
system > ConTeXt ver: 2023.02.23 21:26 LMTX fmt: 2023.3.4 int:
english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name
'/home/gerion/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source> level 1, order 1, name
'/home/gerion/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './test', input './test.tex', result './test'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 2, name './test.tex'
fonts > preloading latin modern fonts (second stage)
fonts > 'fallback modern rm 12pt' is loaded
lua error > lua error on line 8 in file ./test.tex:
registered function call [809]:
...ext/tex/texmf-context/tex/context/base/mkiv/strc-num.lua:448: attempt to
index a nil value (local 'd')
stack traceback:
...ext/tex/texmf-context/tex/context/base/mkiv/strc-num.lua:448: in
function <...ext/tex/texmf-context/tex/context/base/mkiv/strc-num.lua:442>
(...tail calls...)
1 \definedescription[desc][headstyle=bold]
2
3 \starttext
4 Foo
5
6 \desc{Some title} Some text
7 \startitemize
8 >> \item Some item
9 \stopitemize
10
11 \stoptext
12
mtx-context | fatal error: return code: 1
```
Best,
Gerion
signature.asc
Description: This is a digitally signed message part.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Problem with LMTX on macOS: no format file given, quitting
In my MacOSX Ventura 13.2 on M1, ConTeXt work fine. $ context --version mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /Users/monty/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2023.01.15 14:04 mtx-context | main context file: /Users/monty/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2023.01.15 14:04 $ luametatex --version This is LuaMetaTeX, Version 2.10.05 Execute 'luametatex --credits' for credits and version details. There is NO warranty. Redistribution of this software is covered by the terms of the GNU General Public License, version 2 or (at your option) any later version. For more information about these matters, see the file named COPYING and the LuaMetaTeX source. Functionality : level 20230112 Support : cont...@ntg.nl Copyright : The Lua(Meta)TeX Team(s) (2005-2022+) The LuaMetaTeX project is related to ConTeXt development. This macro package tightly integrates TeX and MetaPost in close cooperation with Lua. Updates will happen in sync with ConTeXt and when needed. Don't be fooled by unchanged dates: long term stability is the objective. $ context ex100.tex $ more ex100.log system > system > ConTeXt ver: 2023.02.07 19:06 LMTX fmt: 2023.2.13 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 1, order 1, name '/Users/monty/context-osx-64/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' ... All in order. Greetings. Luis El lun, 13 feb 2023 a las 2:36, Hans Hagen via ntg-context (< ntg-context@ntg.nl>) escribió: > On 2/12/2023 4:28 PM, Tommaso Gordini via ntg-context wrote: > > > The curious thing is that even by launching the ConTeXt present in TeX > > Live, what really works is always MkIV Standalone. > There should be > > mtxrun -> luametatex > context -> luametatex > > links plus > > mxtrun.lua > context.lua > > in the binary path. > > I have no mac so i cannot check these things (i can test windows intel > and linux intel/arm but osx is a gamble) > > 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 / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > > ___ > ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Problem with LMTX on macOS: no format file given, quitting
On 2/13/2023 8:23 AM, Jean-Pierre Delange via ntg-context wrote: Tommaso, Most likely you're not the only one looking to properly install CTX on MacOSX. Also all the tricks that allow to do it may interest other people... also keep in mind that when you install both lmtx and mkiv that luametatex will be the runner for luatex, so in order to run mkiv one then needs: context --luatex on texlive (2023) that will be the way to go now which basically means that as mkii is frozen, mkiv is now frozen in favor of mkxl (aka lmtx) 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Problem with LMTX on macOS: no format file given, quitting
On 2/12/2023 4:28 PM, Tommaso Gordini via ntg-context wrote: The curious thing is that even by launching the ConTeXt present in TeX Live, what really works is always MkIV Standalone. There should be mtxrun -> luametatex context -> luametatex links plus mxtrun.lua context.lua in the binary path. I have no mac so i cannot check these things (i can test windows intel and linux intel/arm but osx is a gamble) 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Problem with LMTX on macOS: no format file given, quitting
On 2/12/2023 5:34 PM, Pablo Rodriguez via ntg-context wrote: On 2/12/23 16:28, Tommaso Gordini via ntg-context wrote: [...] However, I also get this: charlie@Air-di-Tommaso ~ % luametatex startup error : no format file given, quitting Hi Tommaso, my ConTeXt LMTX is fully functional and I get this message too. sure, because that message is okay: luametatex cannot do anything useful until it is properly initialized so you need to either run it in ini mode or provide a format file (made in ini mode) just ask yourself: what would you expect the 'luametatex' command (without any commandline argumment) to do ... it has to be told how to read files, what primitives to enable, how to locate and load fonts, how to produce backend code ... not much different from running 'lua' or whatever scripting language that expects some source to work with the 'mtxrun' and 'context' commands are basically 'luametatex' with a different name so that it knows what script / format to load 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Problem with LMTX on macOS: no format file given, quitting
On 2/12/23 16:28, Tommaso Gordini via ntg-context wrote: > [...] > However, I also get this: > > charlie@Air-di-Tommaso ~ % luametatex > startup error : no format file given, quitting Hi Tommaso, my ConTeXt LMTX is fully functional and I get this message too. > Also, I created the TeXShop engine as indicated on the page (I've done > it before with no problems). > However, now when I run LMTX from editor to compose a source, the source > is compiled with MkIV Standalone, which I have in another folder > (/Users/charlie/Documents/ConTeXt/ConTeXt-MkIV). LMTX doesn't even work > from a terminal, of course. I’m on Linux, so no TeXShop here. BTW, I’m not sure "luametatex" may work as you intend (without any format file). > The curious thing is that even by launching the ConTeXt present in TeX > Live, what really works is always MkIV Standalone. I don‘t think ConTeXt from TeX Live includes LMTX (https://ctan.org/search?phrase=luametatex). > Do you have any idea where I might have gone wrong? My guess is that when you invoke ConTeXt, you are running it from TeX Live (or from other than the wiki installation). To check that, what do you get from "which context"? Which is your output from "context --version"? My system reads: mtx-context | current version: 2023.02.07 19:06 When in doubt run the following (given the paths you provided): cd ~/Documents/ConTeXt/ConTeXt-LMTX/ sh ./install.sh cd && context --version And you should get what my system reads (unless there is an update today). I hope it helps, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Problem with LMTX on macOS: no format file given, quitting
Hello list, I am writing to you about a problem with ConTeXt LMTX and TeXShop 5.11 on macOS 12.6.3 (MacBook Air M2). Yesterday I installed LMTX on my computer following the instructions here: https://wiki.contextgarden.net/Installing_ConTeXt_LMTX_on_MacOS The LMTX tree is correctly installed in the directory I've chosen: charlie@Air-di-Tommaso ~ % which luametatex /Users/charlie/Documents/ConTeXt/ConTeXt-LMTX/tex/texmf-osx-arm64/bin/luametatex charlie@Air-di-Tommaso ~ % type luametatex luametatex is /Users/charlie/Documents/ConTeXt/ConTeXt-LMTX/tex/texmf-osx-arm64/bin/luametatex charlie@Air-di-Tommaso ~ % luametatex --version This is LuaMetaTeX, Version 2.10.06 Execute 'luametatex --credits' for credits and version details. There is NO warranty. Redistribution of this software is covered by the terms of the GNU General Public License, version 2 or (at your option) any later version. For more information about these matters, see the file named COPYING and the LuaMetaTeX source. Functionality : level 20230126 Support : cont...@ntg.nl Copyright : The Lua(Meta)TeX Team(s) (2005-2022+) The LuaMetaTeX project is related to ConTeXt development. This macro package tightly integrates TeX and MetaPost in close cooperation with Lua. Updates will happen in sync with ConTeXt and when needed. Don't be fooled by unchanged dates: long-term stability is the objective. However, I also get this: charlie@Air-di-Tommaso ~ % luametatex startup error : no format file given, quitting Also, I created the TeXShop engine as indicated on the page (I've done it before with no problems). However, now when I run LMTX from editor to compose a source, the source is compiled with MkIV Standalone, which I have in another folder ( /Users/charlie/Documents/ConTeXt/ConTeXt-MkIV). LMTX doesn't even work from a terminal, of course. The curious thing is that even by launching the ConTeXt present in TeX Live, what really works is always MkIV Standalone. Do you have any idea where I might have gone wrong? Thank you very much Tommaso ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] autospacing and colonequals (was Lucida-1.901 (2023-01-21) available)
Hi Hans and Mikael,
Thank you both for your attention to my reply and the clarification and hints
regarding the comman \colonequals and
\setupmathematics[autospacing=yes]
Indeed the command \colonequals give the precise expected alignment for the
combination glyph « := ». Befors changing the combination « := » to
\columnequals in my documents, I am wondering whether one could add a small lua
code in order to make an automatic replacement at run time. Actually, since I
don’t know of any other instance in which the combination « := » is used to
mean something else, would it not be reasonnable to make « := » synonym to
\colonequals?
I played a little bit with
\setupmathematics[autospacing=yes]
and it seems to me that without this command one gets automatic spacing in math
mode, while with the above command the spacing obeys what has been inserted in
the source. Is this behaviour intended, or is there a mismatch between
\setupmathematics[autospacing=yes]
and
\setupmathematics[autospacing=no]
Best regards: Otared
> On 26 Jan 2023, at 10:33, Hans Hagen via ntg-context <mailto:ntg-context@ntg.nl>> wrote:
>
> On 1/25/2023 6:24 PM, Mikael Sundqvist via ntg-context wrote:
>> On Wed, Jan 25, 2023 at 11:02 AM Otared Kavian via ntg-context
>> mailto:ntg-context@ntg.nl>> wrote:
>>>
>>> Hi,
>>>
>>> Thanks Hraban for the information and the link to the article by Hans and
>>> Mikael about the math fonts in Lucida.
>>>
>>> I very much appreciated that article: one sees how the handling of almost
>>> impercebtile details in ConTeXt make us to adhere to and love LuaMetaTeX…
>>> So a great thank you to Hans and Mikael for all this work!
>>>
>>> Regarding the details of vertical alignment in math, I wonder whether the
>>> column « : » in front of the equal sign « = », in the combination « := »
>>> (used to define for instance a new variable) should be alos centered around
>>> the math axis, as explained in the article. For instance in the following
>>> example
>>>
>>> \setupbodyfont[lucidaot,12pt]
>>> \starttext
>>> \startformula
>>> f(x) := -(u|x) := - \langle u, x \rangle
>>> \stopformula
>>> \stopformula
>>> \startformula
>>> f : A \longrightarrow B
>>> \stopformula
>>> \stoptext
>>>
>>> it seems to me that the lower dot (or square…) in the semicolumn of the
>>> first formula (in front of the equal sign) is lower than in the second
>>> formula.
>>>
>>> Best regards: Otared
>> Thank you for the kind words, Otared,
>> Regarding the colons (and other symbols with "dots"), I would say it
>> is still not optimal in Lucida (and difficult to make it "consistent",
>> there are too many symbols that are at the moment different). But in
>> your example you can use \colonequals and \colon if you prefer. They
>> are centered around the math axis.
>> Best, Mikael
>> \setupbodyfont[lucidaot,12pt]
>> \starttext
>> \startformula
>> f(x) := -(u|x) \colonequals - \langle u, x \rangle
>> \stopformula
>> \startformula
>> f : A \longrightarrow B \breakhere
>> f \colon A \longrightarrow B
>> \stopformula
>> \startformula
>> \mathaxisbelow := \colonequals : \colon
>> \stopformula
>> \stoptext
> There is a (experimental as we played with it and then got distracted)
> feature that makes some symbols adapt to spacing in the input.
>
> \starttext
>
>\setupmathematics[autospacing=yes]
>
>\setupmathematics[collapsing=2]
>
>\im{A:B} and \im{A : B}\par
>\im{A:=B} and \im{A := B}\par
>\im{A\colonequals B} and \im{A {\colonequals} B}\par
>
> \stoptext
>
> the second line is not yet ok as collapsing the := (old feature) comes at the
> wrong time when we do autospacing (something Mikasl and I now need to discuss
> and test)
>
> This autospacing is part of some larger effort, for instance we can also auto
> handle fences and so. All this relates to minimizing the input and make it a
> bit more natural. Think (1,2) vb (1, 2) where we - due to the many more
> classes that we have - want spacing to be right.
>
> All will be revealed in the upcoming releases and the upcoming 3145 page math
> manual.
>
> Hans
>
> -
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl <http://www.pragma-ade.nl/> |
Re: [NTG-context] Lucida-1.901 (2023-01-21) available
On 1/25/2023 6:24 PM, Mikael Sundqvist via ntg-context wrote:
On Wed, Jan 25, 2023 at 11:02 AM Otared Kavian via ntg-context
wrote:
Hi,
Thanks Hraban for the information and the link to the article by Hans and
Mikael about the math fonts in Lucida.
I very much appreciated that article: one sees how the handling of almost
impercebtile details in ConTeXt make us to adhere to and love LuaMetaTeX… So a
great thank you to Hans and Mikael for all this work!
Regarding the details of vertical alignment in math, I wonder whether the
column « : » in front of the equal sign « = », in the combination « := » (used
to define for instance a new variable) should be alos centered around the math
axis, as explained in the article. For instance in the following example
\setupbodyfont[lucidaot,12pt]
\starttext
\startformula
f(x) := -(u|x) := - \langle u, x \rangle
\stopformula
\stopformula
\startformula
f : A \longrightarrow B
\stopformula
\stoptext
it seems to me that the lower dot (or square…) in the semicolumn of the first
formula (in front of the equal sign) is lower than in the second formula.
Best regards: Otared
Thank you for the kind words, Otared,
Regarding the colons (and other symbols with "dots"), I would say it
is still not optimal in Lucida (and difficult to make it "consistent",
there are too many symbols that are at the moment different). But in
your example you can use \colonequals and \colon if you prefer. They
are centered around the math axis.
Best, Mikael
\setupbodyfont[lucidaot,12pt]
\starttext
\startformula
f(x) := -(u|x) \colonequals - \langle u, x \rangle
\stopformula
\startformula
f : A \longrightarrow B \breakhere
f \colon A \longrightarrow B
\stopformula
\startformula
\mathaxisbelow := \colonequals : \colon
\stopformula
\stoptext
There is a (experimental as we played with it and then got distracted)
feature that makes some symbols adapt to spacing in the input.
\starttext
\setupmathematics[autospacing=yes]
\setupmathematics[collapsing=2]
\im{A:B} and \im{A : B}\par
\im{A:=B} and \im{A := B}\par
\im{A\colonequals B} and \im{A {\colonequals} B}\par
\stoptext
the second line is not yet ok as collapsing the := (old feature) comes
at the wrong time when we do autospacing (something Mikasl and I now
need to discuss and test)
This autospacing is part of some larger effort, for instance we can also
auto handle fences and so. All this relates to minimizing the input and
make it a bit more natural. Think (1,2) vb (1, 2) where we - due to the
many more classes that we have - want spacing to be right.
All will be revealed in the upcoming releases and the upcoming 3145 page
math manual.
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Lucida-1.901 (2023-01-21) available
On Wed, Jan 25, 2023 at 11:02 AM Otared Kavian via ntg-context wrote: > > Hi, > > Thanks Hraban for the information and the link to the article by Hans and > Mikael about the math fonts in Lucida. > > I very much appreciated that article: one sees how the handling of almost > impercebtile details in ConTeXt make us to adhere to and love LuaMetaTeX… So > a great thank you to Hans and Mikael for all this work! > > Regarding the details of vertical alignment in math, I wonder whether the > column « : » in front of the equal sign « = », in the combination « := » > (used to define for instance a new variable) should be alos centered around > the math axis, as explained in the article. For instance in the following > example > > \setupbodyfont[lucidaot,12pt] > \starttext > \startformula > f(x) := -(u|x) := - \langle u, x \rangle > \stopformula > \stopformula > \startformula > f : A \longrightarrow B > \stopformula > \stoptext > > it seems to me that the lower dot (or square…) in the semicolumn of the first > formula (in front of the equal sign) is lower than in the second formula. > > Best regards: Otared Thank you for the kind words, Otared, Regarding the colons (and other symbols with "dots"), I would say it is still not optimal in Lucida (and difficult to make it "consistent", there are too many symbols that are at the moment different). But in your example you can use \colonequals and \colon if you prefer. They are centered around the math axis. Best, Mikael \setupbodyfont[lucidaot,12pt] \starttext \startformula f(x) := -(u|x) \colonequals - \langle u, x \rangle \stopformula \startformula f : A \longrightarrow B \breakhere f \colon A \longrightarrow B \stopformula \startformula \mathaxisbelow := \colonequals : \colon \stopformula \stoptext ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Lucida-1.901 (2023-01-21) available
Hi, Thanks Hraban for the information and the link to the article by Hans and Mikael about the math fonts in Lucida. I very much appreciated that article: one sees how the handling of almost impercebtile details in ConTeXt make us to adhere to and love LuaMetaTeX… So a great thank you to Hans and Mikael for all this work! Regarding the details of vertical alignment in math, I wonder whether the column « : » in front of the equal sign « = », in the combination « := » (used to define for instance a new variable) should be alos centered around the math axis, as explained in the article. For instance in the following example \setupbodyfont[lucidaot,12pt] \starttext \startformula f(x) := -(u|x) := - \langle u, x \rangle \stopformula \stopformula \startformula f : A \longrightarrow B \stopformula \stoptext it seems to me that the lower dot (or square…) in the semicolumn of the first formula (in front of the equal sign) is lower than in the second formula. Best regards: Otared > On 23 Jan 2023, at 09:39, Henning Hraban Ramm via ntg-context > wrote: > > https://tug.org/pipermail/lucida/2023-January/000921.html > > A new version (1.901) of the Lucida OpenType fonts from TUG is > available. As with previous updates, there's no additional charge if > you've already purchased licenses; you can use the same download > information sent to you at the time of purchase to get the new fonts. > (If you've lost the download info, you can email us at > lucida-admin at tug.org.) > > I will append the changes for this release. The same information is also > online at https://tug.org/store/lucida/NEWS.txt. > > To summarize, the most significant changes have been to the math fonts, > especially the regular-weight LucidaBrightMathOT. Many of these changes > were discussed in greater detail in the recent article about Lucida math > by Hans Hagen and Mikael Sundqvist: > https://tug.org/TUGboat/tb43-3/tb135hagen-lucida.pdf > > The four Lucida Sans fonts and the three specialized fonts (Blackletter, > Calligraphy, Handwriting) are not changed at all from the last release > (not even version numbers or dates). All other fonts were changed. > > On behalf of TUG, I thank Hans, Mikael, and Michael Sharpe, who among > them did essentially all of the technical font editing for this > release. And we must thank Chuck Bigelow and Kris Holmes (they approved > this release, as always), without whom nothing could be done. > > Bug reports and character/feature requests are welcome (email to this > list is best), though, as usual, we cannot promise any particular > timeline for the next release. > > Happy typesetting, > Karl [Berry] > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > ___ Otared Kavian e-mail: ota...@gmail.com Phone: +33 6 88 26 70 95 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] pgfplots module wrecks in latest
On Mon, 16 Jan 2023, Hans Hagen via ntg-context wrote: > make sure to get rid of the t-tikz modules Tested again. Downloaded the latest context and pgf.tds.zip from ctan. Unizip pgf by using 'unzip -x "**/t-*.*" so that no t- modules from tikz are unzipped but still get the following error on a simple hello world example: \usemodule[tikz] \starttext Hello \stoptext gives the attached log. Does the latest pgf/tikz run at your end? Adityajob > passes > version mismatch: 1.32 <> 1.33 system > system > ConTeXt ver: 2023.01.15 14:04 LMTX fmt: 2023.1.16 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 1, order 1, name '/opt/luametatex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source > level 1, order 1, name '/opt/luametatex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname './test', input './test.tex', result './test' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './test.tex' modules > 'tikz' is loaded open source > level 2, order 3, name '/opt/luametatex/texmf-context/tex/context/modules/mkxl/m-tikz.mkxl' open source > level 3, order 4, name 'pgfutil-common.tex' close source> level 3, order 4, name 'pgfutil-common.tex' open source > level 3, order 5, name 'pgfutil-context.def' close source> level 3, order 5, name 'pgfutil-context.def' open source > level 3, order 6, name 'pgfrcs.code.tex' open source > level 4, order 7, name 'pgf.revision.tex' close source> level 4, order 7, name 'pgf.revision.tex' close source> level 3, order 7, name 'pgfrcs.code.tex' open source > level 3, order 8, name 'pgfsys.code.tex' open source > level 4, order 9, name 'pgfkeys.code.tex' open source > level 5, order 10, name 'pgfkeyslibraryfiltered.code.tex' close source> level 5, order 10, name 'pgfkeyslibraryfiltered.code.tex' close source> level 4, order 10, name 'pgfkeys.code.tex' cld > stack > cld > stack > use : slot = context.functions.register(f) cld > stack > and : context.functions.unregister(slot) cld > stack > open source > level 4, order 11, name 'pgf.cfg' close source> level 4, order 11, name 'pgf.cfg' Driver file for pgf: pgfsys-luatex.def open source > level 4, order 12, name 'pgfsys-luatex.def' open source > level 5, order 13, name 'pgfsys-common-pdf.def' close source> level 5, order 13, name 'pgfsys-common-pdf.def' close source> level 4, order 13, name 'pgfsys-luatex.def' open source > level 4, order 14, name 'test.pgf' close source> level 4, order 14, name 'test.pgf' close source> level 3, order 14, name 'pgfsys.code.tex' open source > level 3, order 15, name 'pgfkeys.code.tex' close source> level 3, order 15, name 'pgfkeys.code.tex' open source > level 3, order 16, name 'pgfsyssoftpath.code.tex' close source> level 3, order 16, name 'pgfsyssoftpath.code.tex' open source > level 3, order 17, name 'pgfsysprotocol.code.tex' close source> level 3, order 17, name 'pgfsysprotocol.code.tex' open source > level 3, order 18, name 'pgfcore.code.tex' open source > level 4, order 19, name 'pgfmath.code.tex' open source > level 5, order 20, name 'pgfmathutil.code.tex' close source> level 5, order 20, name 'pgfmathutil.code.tex' open source > level 5, order 21, name 'pgfmathparser.code.tex' close source> level 5, order 21, name 'pgfmathparser.code.tex' open source > level 5, order 22, name 'pgfmathfunctions.code.tex' close source> level 5, order 22, name 'pgfmathfunctions.code.tex' open source > level 5, order 23, name 'pgfmathfunctions.basic.code.tex' close source> level 5, order 23, name 'pgfmathfunctions.basic.code.tex' open source > level 5, order 24, name 'pgfmathfunctions.trigonometric.code.tex' close source> level 5, order 24, name 'pgfmathfunctions.trigonometric.code.tex' open source > level 5, order 25, name 'pgfmathfunctions.random.code.tex' close source> level 5, order 25, name 'pgfmathfunctions.random.code.tex' open source > level 5, order 26, name 'pgfmathfunctions.comparison.code.tex' close source> level 5, order 26, name 'pgfmathfunctions.comparison.code.tex' open source > level 5, order 27, name 'pgfmathfunctions.base.code.tex' close source> level 5, order 27, name 'pgfmathfunctions.base.code.tex' open source > level 5, order 28, name 'pgfmathfunctions.round.code.tex' close source> level 5, order
Re: [NTG-context] pgfplots module wrecks in latest
On Mon, 16 Jan 2023, Hans Hagen via ntg-context wrote: > just load tikz first so that the right loader helpers are there > > \usemodule[tikz] > \usemodule[pgfplots] > > \starttext > Hello > \stoptext > > seems to work here I did a fresh install of context and downloaded the latest version of pgf/tikz and pgfplots from ctan. Now, something is wrong with tikz: \usemodule[tikz] \starttext Hello \stoptext gives the attached log file. Not sure what changed on the tikz end. Thanks, Aditya system > system > ConTeXt ver: 2023.01.15 14:04 LMTX fmt: 2023.1.16 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 1, order 1, name '/opt/luametatex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source> level 1, order 1, name '/opt/luametatex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname './test', input './test.tex', result './test' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './test.tex' modules > 'tikz' is loaded open source > level 2, order 3, name '/opt/luametatex/texmf-context/tex/context/modules/mkxl/m-tikz.mkxl' open source > level 3, order 4, name 'pgfutil-common.tex' close source> level 3, order 4, name 'pgfutil-common.tex' open source > level 3, order 5, name 'pgfutil-context.def' close source> level 3, order 5, name 'pgfutil-context.def' open source > level 3, order 6, name 'pgfrcs.code.tex' open source > level 4, order 7, name 'pgf.revision.tex' close source> level 4, order 7, name 'pgf.revision.tex' close source> level 3, order 7, name 'pgfrcs.code.tex' open source > level 3, order 8, name 'pgfsys.code.tex' open source > level 4, order 9, name 'pgfkeys.code.tex' open source > level 5, order 10, name 'pgfkeyslibraryfiltered.code.tex' close source> level 5, order 10, name 'pgfkeyslibraryfiltered.code.tex' close source> level 4, order 10, name 'pgfkeys.code.tex' cld > stack > cld > stack > use : slot = context.functions.register(f) cld > stack > and : context.functions.unregister(slot) cld > stack > open source > level 4, order 11, name 'pgf.cfg' close source> level 4, order 11, name 'pgf.cfg' Driver file for pgf: pgfsys-luatex.def open source > level 4, order 12, name 'pgfsys-luatex.def' open source > level 5, order 13, name 'pgfsys-common-pdf.def' close source> level 5, order 13, name 'pgfsys-common-pdf.def' close source> level 4, order 13, name 'pgfsys-luatex.def' open source > level 4, order 14, name 'test.pgf' close source> level 4, order 14, name 'test.pgf' close source> level 3, order 14, name 'pgfsys.code.tex' open source > level 3, order 15, name 'pgfkeys.code.tex' close source> level 3, order 15, name 'pgfkeys.code.tex' open source > level 3, order 16, name 'pgfsyssoftpath.code.tex' close source> level 3, order 16, name 'pgfsyssoftpath.code.tex' open source > level 3, order 17, name 'pgfsysprotocol.code.tex' close source> level 3, order 17, name 'pgfsysprotocol.code.tex' open source > level 3, order 18, name 'pgfcore.code.tex' open source > level 4, order 19, name 'pgfmath.code.tex' open source > level 5, order 20, name 'pgfmathutil.code.tex' close source> level 5, order 20, name 'pgfmathutil.code.tex' open source > level 5, order 21, name 'pgfmathparser.code.tex' close source> level 5, order 21, name 'pgfmathparser.code.tex' open source > level 5, order 22, name 'pgfmathfunctions.code.tex' close source> level 5, order 22, name 'pgfmathfunctions.code.tex' open source > level 5, order 23, name 'pgfmathfunctions.basic.code.tex' close source> level 5, order 23, name 'pgfmathfunctions.basic.code.tex' open source > level 5, order 24, name 'pgfmathfunctions.trigonometric.code.tex' close source> level 5, order 24, name 'pgfmathfunctions.trigonometric.code.tex' open source > level 5, order 25, name 'pgfmathfunctions.random.code.tex' close source> level 5, order 25, name 'pgfmathfunctions.random.code.tex' open source > level 5, order 26, name 'pgfmathfunctions.comparison.code.tex' close source> level 5, order 26, name 'pgfmathfunctions.comparison.code.tex' open source > level 5, order 27, name 'pgfmathfunctions.base.code.tex' close source> level 5, order 27, name 'pgfmathfunctions.base.code.tex' open source > level 5, order 28, name 'pgfmathfunctions.round.code.tex' close source> level 5,
Re: [NTG-context] Trouble with latest...
On Mon, 9 Jan 2023 19:08:54 -0700 Alan Braslau via ntg-context wrote: > On Mon, 9 Jan 2023 18:40:08 +0100 > Alain Delmotte via ntg-context wrote: > > > Anytime a new upload is announced, I download the > > context-win64.zip unpack it and run install.bat and setpath.bat. > > > > Is it a fresh installation? Or should I from time to time > > erase my installation and run install.bat to create a new > > distribution? > > This is not a *fresh* install. In fact, you can simply run > ./install.bat - there is no need to download context-win64.zip. > > Having said that, the latest problem with the update has to do with an > updated luametatex binary, so your method might have worked by > updating the binary with the unzip, even if it is not a "fresh" > install. For information: I tried updating by downloading a fresh zip and unpacking it over an existing installation, then running ./install.bat. This failed with the latest upload, although unzipping to a new location and running ./install.bat resulting in a good, updated distribution. The install/update and mtxrun scripts could possibly be improved to 1. start by updating the luametatex binary in a first step, then rerunning to update the rest of the distribution; 2. systematically clear the luametatex-cache upon update (I believe that this is a small price to pay for robustness). However, such changes clearly are not a priority to work out, for now. Alan ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Trouble with latest...
On Mon, 9 Jan 2023 18:40:08 +0100 Alain Delmotte via ntg-context wrote: > Anytime a new upload is announced, I download the > context-win64.zip unpack it and run install.bat and setpath.bat. > > Is it a fresh installation? Or should I from time to time > erase my installation and run install.bat to create a new > distribution? This is not a *fresh* install. In fact, you can simply run ./install.bat - there is no need to download context-win64.zip. Having said that, the latest problem with the update has to do with an updated luametatex binary, so your method might have worked by updating the binary with the unzip, even if it is not a "fresh" install. Alan -- Alan Braslau 816 West Mountain Avenue Fort Collins, CO 80521 USA mobile: (970) 237-0957 Conserve energy! ;-) ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Trouble with latest...
Hi! Le 8/01/2023 à 21:02, Wolfgang Schuster via ntg-context a écrit : Thomas A. Schmitz via ntg-context schrieb am 08.01.2023 um 20:02: Hi all, I tried upgrading to the 2023 version, but generating the format fails with lots of these messages: [...] But I was surprised that nobody else had seen it yet. Can anyone confirm (or yell “works for me!”)? You luametatex binary is too old and fails on the new \advanceby command. When I tried to update my current installation a few moments ago the updater also failed to load the new luametatex binary (I haven't tried to regenerate the format files) but a fresh installation works without problems. Wolfgang I am working on Windows 10. Anytime a new upload is announced, I download the context-win64.zip unpack it and run install.bat and setpath.bat. Is it a fresh installation? Or should I from time to time erase my installation and run install.bat to create a new distribution? Thanks for the advices! Happy New Year to everybody! Alain ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Trouble with latest...
On 1/8/2023 9:32 PM, Thomas A. Schmitz via ntg-context wrote: On 1/8/23 21:02, Wolfgang Schuster via ntg-context wrote: You luametatex binary is too old and fails on the new \advanceby command. When I tried to update my current installation a few moments ago the updater also failed to load the new luametatex binary (I haven't tried to regenerate the format files) but a fresh installation works without problems. Wolfgang Thank you, Wolfgang, will try with a fresh installation. Now that you mention it, I see some error messages in the log mtx-install | changed : 0 % : 3360848 : tex/texmf-linux-64/bin/luametatex mtx-install | tex/texmf-linux-64/bin/luametatex, try again later: this is indeed an indication that an old binary is used 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Trouble with latest...
On 1/8/23 21:02, Wolfgang Schuster via ntg-context wrote: You luametatex binary is too old and fails on the new \advanceby command. When I tried to update my current installation a few moments ago the updater also failed to load the new luametatex binary (I haven't tried to regenerate the format files) but a fresh installation works without problems. Wolfgang Thank you, Wolfgang, will try with a fresh installation. Now that you mention it, I see some error messages in the log mtx-install | changed : 0 % : 3360848 : tex/texmf-linux-64/bin/luametatex mtx-install | tex/texmf-linux-64/bin/luametatex, try again later: All best Thomas ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Trouble with latest...
Thomas A. Schmitz via ntg-context schrieb am 08.01.2023 um 20:02:
Hi all,
I tried upgrading to the 2023 version, but generating the format fails with
lots of these messages:
! Control sequence expected instead of undefined.
\syst_basics_allocate_yes #1#2#3#4#5->\ifnum #1<#4\relax \global
\advanceby #1\plusone \permanent \global #3#5=#1\relax \else \writestatus {warning}{no
room f
\newmuskip \scratchmuskip
\newmuskip \globalscratchmuskip \newmuskip \privatescratchmuskip
! Control sequence expected instead of undefined.
\syst_basics_allocate_yes #1#2#3#4#5->\ifnum #1<#4\relax \global
\advanceby #1\plusone \permanent \global #3#5=#1\relax \else \writestatus {warning}{no
room f
But I was surprised that nobody else had seen it yet. Can anyone confirm (or
yell “works for me!”)?
You luametatex binary is too old and fails on the new \advanceby command.
When I tried to update my current installation a few moments ago the
updater also failed to load the new luametatex binary (I haven't tried
to regenerate the format files) but a fresh installation works without
problems.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Problem with latest version ?
The problem seems to come from pgfplots ... Le mer. 4 janv. 2023 à 17:35, Fabrice Couvreur a écrit : > > Hi, > I just installed the latest version of LMTX and also updated to texlive > 2022 and I get this error message which was not the case before. > Thank you. > Fabrice > > > Running `lmtX' on `complexes_2' with > ``/home/fabrice/LMTX/tex/texmf-linux-64/bin/mtxrun --autogenerate --script > context --autopdf --purgeall complexes_2'' > > resolvers | formats | executing runner 'run luametatex format': > /home/fabrice/LMTX/tex/texmf-linux-64/bin/luametatex > --jobname="./complexes_2.tex" > --fmt=/home/fabrice/LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt > --lua=/home/fabrice/LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui > --c:autopdf --c:currentrun=1 --c:fulljobname="./complexes_2.tex" > --c:input="./complexes_2.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:purgeall > --c:texmfbinpath="/home/fabrice/LMTX/tex/texmf-linux-64/bin" > system > > system > ConTeXt ver: 2023.01.04 11:35 LMTX fmt: 2023.1.4 int: > english/english > system > > system > 'cont-new.mkxl' loaded > open source > level 1, order 1, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' > system > beware: some patches loaded from cont-new.mkiv > close source> level 1, order 1, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' > system > files > jobname './complexes_2', input > './complexes_2.tex', result './complexes_2' > fonts > latin modern fonts are not preloaded > languages > language 'en' is active > open source > level 1, order 2, name './complexes_2.tex' > open source > level 2, order 3, name 'exercises.mkiv' > open source > level 3, order 4, name 'terminale-modules.tex' > open source > level 4, order 5, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/symb-imp-mvs.mkiv' > close source> level 4, order 5, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/symb-imp-mvs.mkiv' > fonts > symbols > library 'mvs' loaded > open source > level 4, order 6, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/colo-imp-xwi.mkiv' > close source> level 4, order 6, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/colo-imp-xwi.mkiv' > colors > system 'xwi' is loaded > modules > 'tikz' is loaded > open source > level 4, order 7, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/modules/mkxl/m-tikz.mkxl' > open source > level 5, order 8, name 'pgfutil-common.tex' > open source > level 6, order 9, name 'pgfutil-common-lists.tex' > close source> level 6, order 9, name 'pgfutil-common-lists.tex' > close source> level 5, order 9, name 'pgfutil-common.tex' > open source > level 5, order 10, name 'pgfutil-context.def' > close source> level 5, order 10, name 'pgfutil-context.def' > open source > level 5, order 11, name 'pgfrcs.code.tex' > close source> level 5, order 11, name 'pgfrcs.code.tex' > open source > level 5, order 12, name 'pgfsys.code.tex' > open source > level 6, order 13, name 'pgfkeys.code.tex' > open source > level 7, order 14, name 'pgfkeysfiltered.code.tex' > close source> level 7, order 14, name 'pgfkeysfiltered.code.tex' > close source> level 6, order 14, name 'pgfkeys.code.tex' > open source > level 6, order 15, name 'pgf.cfg' > close source> level 6, order 15, name 'pgf.cfg' > Driver file for pgf: pgfsys-pdftex.def > > open source > level 6, order 16, name 'pgfsys-pdftex.def' > open source > level 7, order 17, name 'pgfsys-common-pdf.def' > close source> level 7, order 17, name 'pgfsys-common-pdf.def' > close source> level 6, order 17, name 'pgfsys-pdftex.def' > close source> level 5, order 17, name 'pgfsys.code.tex' > open source > level 5, order 18, name 'pgfkeys.code.tex' > close source> level 5, order 18, name 'pgfkeys.code.tex' > open source > level 5, order 19, name 'pgfsyssoftpath.code.tex' > close source> level 5, order 19, name 'pgfsyssoftpath.code.tex' > open source > level 5, order 20, name 'pgfsysprotocol.code.tex' > close source> level 5, order 20, name 'pgfsysprotocol.code.tex' > open source > level 5, order 21, name 'pgfcore.code.tex' > open source > level 6, order 22, name 'pgfmath.code.
[NTG-context] Problem with latest version ?
Hi, I just installed the latest version of LMTX and also updated to texlive 2022 and I get this error message which was not the case before. Thank you. Fabrice Running `lmtX' on `complexes_2' with ``/home/fabrice/LMTX/tex/texmf-linux-64/bin/mtxrun --autogenerate --script context --autopdf --purgeall complexes_2'' resolvers | formats | executing runner 'run luametatex format': /home/fabrice/LMTX/tex/texmf-linux-64/bin/luametatex --jobname="./complexes_2.tex" --fmt=/home/fabrice/LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=/home/fabrice/LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui --c:autopdf --c:currentrun=1 --c:fulljobname="./complexes_2.tex" --c:input="./complexes_2.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:purgeall --c:texmfbinpath="/home/fabrice/LMTX/tex/texmf-linux-64/bin" system > system > ConTeXt ver: 2023.01.04 11:35 LMTX fmt: 2023.1.4 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 1, order 1, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source> level 1, order 1, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname './complexes_2', input './complexes_2.tex', result './complexes_2' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './complexes_2.tex' open source > level 2, order 3, name 'exercises.mkiv' open source > level 3, order 4, name 'terminale-modules.tex' open source > level 4, order 5, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/symb-imp-mvs.mkiv' close source> level 4, order 5, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/symb-imp-mvs.mkiv' fonts > symbols > library 'mvs' loaded open source > level 4, order 6, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/colo-imp-xwi.mkiv' close source> level 4, order 6, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/colo-imp-xwi.mkiv' colors > system 'xwi' is loaded modules > 'tikz' is loaded open source > level 4, order 7, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/modules/mkxl/m-tikz.mkxl' open source > level 5, order 8, name 'pgfutil-common.tex' open source > level 6, order 9, name 'pgfutil-common-lists.tex' close source> level 6, order 9, name 'pgfutil-common-lists.tex' close source> level 5, order 9, name 'pgfutil-common.tex' open source > level 5, order 10, name 'pgfutil-context.def' close source> level 5, order 10, name 'pgfutil-context.def' open source > level 5, order 11, name 'pgfrcs.code.tex' close source> level 5, order 11, name 'pgfrcs.code.tex' open source > level 5, order 12, name 'pgfsys.code.tex' open source > level 6, order 13, name 'pgfkeys.code.tex' open source > level 7, order 14, name 'pgfkeysfiltered.code.tex' close source> level 7, order 14, name 'pgfkeysfiltered.code.tex' close source> level 6, order 14, name 'pgfkeys.code.tex' open source > level 6, order 15, name 'pgf.cfg' close source> level 6, order 15, name 'pgf.cfg' Driver file for pgf: pgfsys-pdftex.def open source > level 6, order 16, name 'pgfsys-pdftex.def' open source > level 7, order 17, name 'pgfsys-common-pdf.def' close source> level 7, order 17, name 'pgfsys-common-pdf.def' close source> level 6, order 17, name 'pgfsys-pdftex.def' close source> level 5, order 17, name 'pgfsys.code.tex' open source > level 5, order 18, name 'pgfkeys.code.tex' close source> level 5, order 18, name 'pgfkeys.code.tex' open source > level 5, order 19, name 'pgfsyssoftpath.code.tex' close source> level 5, order 19, name 'pgfsyssoftpath.code.tex' open source > level 5, order 20, name 'pgfsysprotocol.code.tex' close source> level 5, order 20, name 'pgfsysprotocol.code.tex' open source > level 5, order 21, name 'pgfcore.code.tex' open source > level 6, order 22, name 'pgfmath.code.tex' open source > level 7, order 23, name 'pgfmathcalc.code.tex' open source > level 8, order 24, name 'pgfmathutil.code.tex' fonts > beware: no fonts are loaded yet, using 'lm mono' in box close source> level 8, order 24, name 'pgfmathutil.code.tex' open source > level 8, order 25, name 'pgfmathparser.code.tex' close source> level 8, order 25, name 'pgfmathparser.code.tex' open source > level 8, order 26, name 'pgfmat
Re: [NTG-context] Math bug (maybe) - prime
On 12/27/2022 6:33 PM, Alan Braslau via ntg-context wrote:
MWE:
\starttext
$a^2′$
$a′^2$
$\mathord{a′}^2$
$a^*^2$
\stoptext
Should the \mathord{} be necessary to get the desired result?
(I would expect the second line to work, just like $a^*^2$.)
primes are kind of special and a pain in tex
- traditional tex sees them as superscripts and therefore expects soem
active character and parsing magick for successive scripts
- that assumes a special way of havign these primes in the font (read:
is it a text size thing already raised or a script one not yet raised)
- it also sort of spoils spacing (as one can end up with an empty
nucleus inserted)
- in mkiv we use different magick than in mkii
anyway, in lmtx (luametatex) primes have been promoted to first class
citizens which means that a nucleus can have
- super(post)script
- sub(post)script
- superprescript
- subprescript
- prime
and each comes with spacing and positioning properties cf opentype and
our own additions for the pre/prime)
there is some magick wrt subscripts as these often are indices (which is
why we have for instance ^^^ and ___ too)
What you can do is:
$\primed{a}^2$
which basically makes the prime an operation .. a small price to pay for
more robust handling of primes (also across fonts)
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] new upload
On 12/27/2022 6:44 PM, Pablo Rodriguez via ntg-context wrote: On 12/27/22 18:04, Hans Hagen via ntg-context wrote: Hi, I uploaded lmtx. There have been some additions to tabulate. Hi Hans, many thanks for the new upload, but I’m afraid I get this error in LMTX (MkIV works fine): \starttext \null \stoptext resolvers | formats | executing runner 'run luametatex format': ~/context/tex/texmf-linux-64/bin/luametatex --jobname="./a.tex" --fmt=~/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=~/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui --c:currentrun=1 --c:fulljobname="./a.tex" --c:input="./a.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="~/context/tex/texmf-linux-64/bin" mtx-context | fatal error: return code: 1 I have erased and generated the cache with "mtxrun --generate". I don’t know what may be wrong here. me neither so i need to check it - 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://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] new upload
On 12/27/22 18:04, Hans Hagen via ntg-context wrote: > Hi, > > I uploaded lmtx. There have been some additions to tabulate. Hi Hans, many thanks for the new upload, but I’m afraid I get this error in LMTX (MkIV works fine): \starttext \null \stoptext resolvers | formats | executing runner 'run luametatex format': ~/context/tex/texmf-linux-64/bin/luametatex --jobname="./a.tex" --fmt=~/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=~/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui --c:currentrun=1 --c:fulljobname="./a.tex" --c:input="./a.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="~/context/tex/texmf-linux-64/bin" mtx-context | fatal error: return code: 1 I have erased and generated the cache with "mtxrun --generate". I don’t know what may be wrong here. Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] new upload
the latest update broke my installation on linux. How can I revert to a working version? .F $ context context18.tex resolvers | globbing | confusing filename, name: 'CHANGELOG', lower: 'changelog', already: 'ChangeLog' resolvers | formats | executing runner 'run luametatex format': /home/vm/context/tex/texmf-linux-64/bin/luametatex --jobname="./context18.tex" --fmt=/home/vm/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=/home/vm/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui --c:currentrun=1 --c:fulljobname="./context18.tex" --c:input="./context18.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/home/vm/context/tex/texmf-linux-64/bin" Segmentation fault (core dumped) mtx-context | fatal error: return code: 1 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] new upload
i get an error running the sample code:
\starttext
\defineorientation[test][orientation=down,vertical=top]
\startbuffer[b]
\definetabulatemove[a][xoffset=40pt]
\definetabulatemove[b][orientation=test,yoffset=depth]
\starttabulate[|c|c|]
\TM[a] \NC \darkred cell one \NC \darkgray cell one \NC \NR
\TM[b] \NC \darkgreen cell one \NC \darkblue cell one \NC \NR
\TM[a] \NC \darkred cell two \NC \darkgray cell two \NC \NR
\TM[b] \NC \darkgreen cell two \NC \darkblue cell two \NC \NR
\TM[a] \NC \darkred cell three \NC \darkgray cell three \NC \NR
\TM[b] \NC \darkgreen cell three \NC \darkblue cell three \NC \NR
\TM[a] \NC \darkred cell four \NC \darkgray cell four \NC \NR
\TM[b] \NC \darkgreen cell four \NC \darkblue cell four \NC \NR
\stoptabulate
\stopbuffer
\start \showmakeup[line] \showstruts \ruledvbox{\getbuffer[b]} \stop
\start \showstruts \ruledvbox{\getbuffer[b]} \stop
\start \ruledvbox{\getbuffer[b]} \stop
\startbuffer[b]
\definetabulatemove[a][xoffset=20pt]
\starttabulate[|p|p|]
\TM[a] \NC \darkred \samplefile{tufte} \NC \darkgray \samplefile{ward}
\NC \NR
\NC \darkgreen \samplefile{tufte} \NC \darkblue
\samplefile{ward} \NC \NR
\TM[a] \NC \darkred \samplefile{tufte} \NC \darkgray \samplefile{ward}
\NC \NR
\NC \darkgreen \samplefile{tufte} \NC \darkblue
\samplefile{ward} \NC \NR
\stoptabulate
\stopbuffer
\start \small \small \showmakeup[line] \showstruts \getbuffer[b] \stop
\stoptext
$ context context\ 17.tex
resolvers | globbing | confusing filename, name: 'CHANGELOG',
lower: 'changelog', already: 'ChangeLog'
resolvers | formats | executing runner 'run luametatex format':
/home/vm/context/tex/texmf-linux-64/bin/luametatex --jobname="./context
17.tex"
--fmt=/home/vm/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt
--lua=/home/vm/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui
--c:currentrun=1 --c:fulljobname="./context 17.tex"
--c:input="./context 17.tex" --c:kindofrun=1 --c:maxnofruns=9
--c:texmfbinpath="/home/vm/context/tex/texmf-linux-64/bin"
Segmentation fault (core dumped)
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] new upload
Hi,
I uploaded lmtx. There have been some additions to tabulate.
\starttext
% \showboxes
% \showstruts
\starttabulate[|w(top,3cm)|w(top,3cm)|]
\NC test \NC test \par test \NC \NR
\NC test \NC test \par test \NC \NR
\stoptabulate
\starttabulate[|w(top,packed,3cm)|w(top,packed,3cm)|]
\NC test \NC test \par test \NC \NR
\NC test \NC test \par test \NC \NR
\stoptabulate
\starttabulate[interlinespace=no,format={|w(bottom,3cm)|w(bottom,3cm)|}]
\NC test \NC test \par test \NC \NR
\NC test \NC test \par test \NC \NR
\stoptabulate
\starttabulate[format={|w(3cm)|w(3cm)|}]
\NC \vtop{\strut test} \NC \vtop{\strut test\par \strut test} \NC \NR
\NC \vtop{\strut test} \NC \vtop{\strut test\par \strut test} \NC \NR
\stoptabulate
\starttabulate[interlinespace=no,format={|w(3cm)|w(3cm)|}]
\NC \vtop{\strut test} \NC \vtop{\strut test\par \strut test} \NC \NR
\NC \vtop{\strut test} \NC \vtop{\strut test\par \strut test} \NC \NR
\stoptabulate
\starttabulate[interlinespace=no,format={|w(3cm)|w(3cm)|}]
\NC \vbox{\strut test} \NC \vbox{\strut test\par \strut test} \NC \NR
\NC \vbox{\strut test} \NC \vbox{\strut test\par \strut test} \NC \NR
\stoptabulate
\starttabulate[interlinespace=no,format={|w(3cm)|w(3cm)|}]
\NC \vtop{\strut test} \NC \vbox{\strut test\par \strut test} \NC \NR
\NC \vbox{\strut test} \NC \vtop{\strut test\par \strut test} \NC \NR
\stoptabulate
\stoptext
This permits top and bottom alignments of text blobs without interrow
spacing being disturbed.
A bit more weird addition is the new \TM (move) option:
\starttext
\defineorientation[test][orientation=down,vertical=top]
\startbuffer[b]
\definetabulatemove[a][xoffset=40pt]
\definetabulatemove[b][orientation=test,yoffset=depth]
\starttabulate[|c|c|]
\TM[a] \NC \darkred cell one \NC \darkgray cell one \NC \NR
\TM[b] \NC \darkgreen cell one \NC \darkblue cell one \NC \NR
\TM[a] \NC \darkred cell two \NC \darkgray cell two \NC \NR
\TM[b] \NC \darkgreen cell two \NC \darkblue cell two \NC \NR
\TM[a] \NC \darkred cell three \NC \darkgray cell three \NC \NR
\TM[b] \NC \darkgreen cell three \NC \darkblue cell three \NC \NR
\TM[a] \NC \darkred cell four \NC \darkgray cell four \NC \NR
\TM[b] \NC \darkgreen cell four \NC \darkblue cell four \NC \NR
\stoptabulate
\stopbuffer
\start \showmakeup[line] \showstruts \ruledvbox{\getbuffer[b]} \stop
\start \showstruts \ruledvbox{\getbuffer[b]} \stop
\start \ruledvbox{\getbuffer[b]} \stop
\startbuffer[b]
\definetabulatemove[a][xoffset=20pt]
\starttabulate[|p|p|]
\TM[a] \NC \darkred \samplefile{tufte} \NC \darkgray \samplefile{ward}
\NC \NR
\NC \darkgreen \samplefile{tufte} \NC \darkblue
\samplefile{ward} \NC \NR
\TM[a] \NC \darkred \samplefile{tufte} \NC \darkgray \samplefile{ward}
\NC \NR
\NC \darkgreen \samplefile{tufte} \NC \darkblue
\samplefile{ward} \NC \NR
\stoptabulate
\stopbuffer
\start \small \small \showmakeup[line] \showstruts \getbuffer[b] \stop
\stoptext
This uses some new low level alignment options that operate on rows as a
whole. As usual, I have no clue what users will come up with but the
idea is that these 'moves' are independent of the alignment so the in
this case shifted columns actually keeps their alignment. (It is mostly
about consistent support luametatex engine features but it might come in
handy.)
Some other 'new' things are too obscure to mention now,
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] upload
On 12/21/22 17:20, Hans Hagen via ntg-context wrote:
> [...]
> Some other possible speedups are on-hold till I have better test cases.
Many thanks for the improvements in the new release, Hans.
I have some documents, but I should be reluctant to send longs, because
I’m almost confident that my code is poorly written (to say the least).
The attachment contains a log for a 72 page document with just text
(from XML sources [XHTML generated by pandoc from Markdown file]).
[Since attachments over 100KB aren’t allowed, only the last two runs are
included in the log file.]
With current latest from today, I get:
mkiv lua stats > runtime: 2.167 seconds, 72 processed pages, 72 shipped
pages, 33.225 pages/second
mtx-context | purged files: xml-context.log, xml-context.tuc
system | total runtime: 8.779 seconds of 8.818 seconds
Exactly the same sources with previous latest (from 2022.12.15):
mkiv lua stats > runtime: 2.410 seconds, 72 processed pages, 72 shipped
pages, 29.877 pages/second
mtx-context | purged files: xml-context.log, xml-context.tuc
system | total runtime: 9.310 seconds of 9.350 seconds
So, the improvement is clear in current latest.
Many thanks again for the improvement,
Pabloresolvers | formats | executing runner 'run luametatex format': ~/context/tex/texmf-linux-64/bin/luametatex --jobname="./xml-context.xml" --fmt=~/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=~/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui --c:currentrun=3 --c:environment="xml-context.tex" --c:fulljobname="./xml-context.xml" --c:input="./xml-context.xml" --c:kindofrun=2 --c:maxnofruns=9 --c:purgeall --c:texmfbinpath="~/context/tex/texmf-linux-64/bin"
structure > lists > out of order sectionsblocks, maybe use \setsectionblock
structure > lists > out of order sectionsblocks, maybe use \setsectionblock
structure > lists > out of order sectionsblocks, maybe use \setsectionblock
structure > lists > out of order sectionsblocks, maybe use \setsectionblock
system >
system > ConTeXt ver: 2022.12.21 17:13 LMTX fmt: 2022.12.21 int: english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name '~/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source> level 1, order 1, name '~/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > 'cont-loc.mkxl' loaded
open source > level 1, order 2, name '~/context/tex/texmf-local/cont-loc.mkxl'
close source> level 1, order 2, name '~/context/tex/texmf-local/cont-loc.mkxl'
system > files > jobname './xml-context', input './xml-context.xml', result './xml-context'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 3, name 'xml-context.tex'
open source > level 2, order 4, name '~/from-pandoc-to-context/pandoc-xhtml.tex'
close source> level 2, order 4, name '~/from-pandoc-to-context/pandoc-xhtml.tex'
colors > 'rgb' color space is supported
colors > 'cmyk' color space is supported
fonts > checks > registering extra script 'auto'
fonts > bodyfont '15pt' is defined (can better be done global)
fonts > bodyfont '18pt' is defined (can better be done global)
close source> level 1, order 4, name 'xml-context.tex'
system > processing as xml: ./xml-context.xml
xml > core > ignoring public entities 'html' as '-//W3C//DTD XHTML 1.0 Transitional//EN' from 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'
structures > begin of sectionblock 'whatcomesfirst'
structures > bookmark: [Portada]
structure > sectioning > hiddentitle @ level 2 : 0.0 -> [Portada]
fonts > bodyfont '25pt' is defined (can better be done global)
fonts > bodyfont '30pt' is defined (can better be done global)
fonts > bodyfont '20pt' is defined (can better be done global)
backend > xmp > using file '~/context/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1, subpage 1
pages > flushing realpage 2, userpage 2, subpage 2
structures > bookmark: [Título]
structure > sectioning > hiddentitle @ level 2 : 0.0 -> [Título]
pages > flushing realpage 3, userpage 3, subpage 3
structures > bookmark: [Derechos de autor]
structure > sectioning > hiddentitle @ level 2 : 0.0 -> \xmlflush {main::24}
pages > f
Re: [NTG-context] bottlenecks
On 12/18/2022 4:21 PM, mf via ntg-context wrote: Il 18/12/22 14:49, Hans Hagen via ntg-context ha scritto: On 12/18/2022 2:14 PM, mf via ntg-context wrote: > ... So we gained a lot in the meantime. mkiv lua stats > loaded fonts: 27 files: lmmono10-regular.otf, texgyrepagella-math.otf, dejavusansmono.ttf, gfsneohellenic.otf, firasans-bolditalic.otf, firasans-regular.otf, firasans-regularitalic.otf, firasanscondensed-bold.otf, firasanscondensed-regular.otf, garamondpremrpro-bdit.otf, garamondpremrpro-med.otf, garamondpremrpro-medcapt.otf, garamondpremrpro-meddisp.otf, garamondpremrpro-medit.otf, garamondpremrpro-meditcapt.otf, garamondpremrpro-medsubh.otf, garamondpremrpro-smbdit.otf, myriadpro-bold.otf, myriadpro-boldcond.otf, myriadpro-boldcondit.otf, myriadpro-cond.otf, myriadpro-condit.otf, myriadpro-it.otf, myriadpro-regular.otf, myriadpro-semiboldit.otf, quivira.otf, sileot.ttf mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 533 instances, 501 shared in backend, 6 common vectors, 495 common hashes, load time 0.196 seconds How does that report with compact font mode? mkiv lua stats > resource resolver: loadtime 0.005 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 107 found files, scanned paths: mkiv lua stats > stored bytecode data: 507 modules (0.285 sec), 106 tables (0.017 sec), 613 chunks (0.302 sec) mkiv lua stats > traced context: maxstack: 1923, freed: 246, unreachable: 1677 mkiv lua stats > cleaned up reserved nodes: 76 nodes, 9 lists of 504 mkiv lua stats > node memory usage: 1684 attribute, 110 fontspec, 419 glue, 87 gluespec, 3 kern, 647 mathspec, 4 penalty, 2 temp, 591 whatsit mkiv lua stats > node list callback tasks: 13 unique task lists, 17 instances (re)created, 325895 calls mkiv lua stats > h-node processing time: 10.654 seconds including kernel mkiv lua stats > attribute processing time: 2.810 seconds front- and backend mkiv lua stats > driver time: 11.714 seconds mkiv lua stats > used backend: pdf mkiv lua stats > jobdata time: 0.810 seconds saving, 0.194 seconds loading mkiv lua stats > callbacks: file: 5439, saved: 644924, direct: 1386, function: 534140, value: 1033, message: 0, bytecode: 613, late 0, total: 1187535 (1151 per page) mkiv lua stats > randomizer: resumed with value 0.58701179146283 mkiv lua stats > v-node processing time: 1.480 seconds mkiv lua stats > loaded patterns: en::1 it::66, load time: 0.000 mkiv lua stats > xml load time: 0.444 seconds, 1 files, 1 converted mkiv lua stats > lxml preparation time: 26.359 seconds, 47936 nodes, 24702 lpath calls, 24331 cached calls mkiv lua stats > interactive elements: 9327 references, 12951 destinations mkiv lua stats > margin data: 6 entries, 0 pending mkiv lua stats > loaded fonts: 27 files: lmmono10-regular.otf, texgyrepagella-math.otf, dejavusansmono.ttf, gfsneohellenic.otf, firasans-bolditalic.otf, firasans-regular.otf, firasans-regularitalic.otf, firasanscondensed-bold.otf, firasanscondensed-regular.otf, garamondpremrpro-bdit.otf, garamondpremrpro-med.otf, garamondpremrpro-medcapt.otf, garamondpremrpro-meddisp.otf, garamondpremrpro-medit.otf, garamondpremrpro-meditcapt.otf, garamondpremrpro-medsubh.otf, garamondpremrpro-smbdit.otf, myriadpro-bold.otf, myriadpro-boldcond.otf, myriadpro-boldcondit.otf, myriadpro-cond.otf, myriadpro-condit.otf, myriadpro-it.otf, myriadpro-regular.otf, myriadpro-semiboldit.otf, quivira.otf, sileot.ttf mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 46 instances, 16 shared in backend, 4 common vectors, 12 common hashes, load time 0.148 seconds mkiv lua stats > text directions: 5.911 seconds mkiv lua stats > metapost: 1.180 seconds, loading: 0.083, execution: 1.109, n: 1039, average: 0.002, instances: 2, luacalls: 46885 (file: 34713, text: 0, script: 5932, log: 6240), memory: 8.995 M mkiv lua stats > math tweaking time: 0.462 seconds, 8 math goodie tables mkiv lua stats > math processing time: 0.211 seconds mkiv lua stats > pdf annotations: 9327 links (9316 unique), 0 special mkiv lua stats > font embedding time: 0.104 seconds, 23 fonts mkiv lua stats > result saved in file: v32.pdf, compresslevel 0, objectcompresslevel 0 mkiv lua stats > positions: 8572 collected, 4774 deltas, 8565 shared partials, 305 partial entries mkiv lua stats > used platform: linux-64, type: unix, binary subtree: texmf-linux-64 mkiv lua stats > used engine: luametatex version: 2.1004, functionality level: 20221214, format id: 679, compiler: gcc mkiv lua stats > tex properties: 740852 hash slots used of 2097152, 93821 control sequences, approximate memory usage: 65 MB mkiv lua stats > lua properties: engine: lua 5.4, used memory: 338 MB, ctx: 266 MB, max: 415 MB, symbol mask: utf (τεχ) mkiv lua stats > runtime: 114.917 seconds, 1032 processed pages, 1032 shipped pag
Re: [NTG-context] bottlenecks
Il 18/12/22 14:49, Hans Hagen via ntg-context ha scritto: On 12/18/2022 2:14 PM, mf via ntg-context wrote: > ... So we gained a lot in the meantime. mkiv lua stats > loaded fonts: 27 files: lmmono10-regular.otf, texgyrepagella-math.otf, dejavusansmono.ttf, gfsneohellenic.otf, firasans-bolditalic.otf, firasans-regular.otf, firasans-regularitalic.otf, firasanscondensed-bold.otf, firasanscondensed-regular.otf, garamondpremrpro-bdit.otf, garamondpremrpro-med.otf, garamondpremrpro-medcapt.otf, garamondpremrpro-meddisp.otf, garamondpremrpro-medit.otf, garamondpremrpro-meditcapt.otf, garamondpremrpro-medsubh.otf, garamondpremrpro-smbdit.otf, myriadpro-bold.otf, myriadpro-boldcond.otf, myriadpro-boldcondit.otf, myriadpro-cond.otf, myriadpro-condit.otf, myriadpro-it.otf, myriadpro-regular.otf, myriadpro-semiboldit.otf, quivira.otf, sileot.ttf mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 533 instances, 501 shared in backend, 6 common vectors, 495 common hashes, load time 0.196 seconds How does that report with compact font mode? mkiv lua stats > resource resolver: loadtime 0.005 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 107 found files, scanned paths: mkiv lua stats > stored bytecode data: 507 modules (0.285 sec), 106 tables (0.017 sec), 613 chunks (0.302 sec) mkiv lua stats > traced context: maxstack: 1923, freed: 246, unreachable: 1677 mkiv lua stats > cleaned up reserved nodes: 76 nodes, 9 lists of 504 mkiv lua stats > node memory usage: 1684 attribute, 110 fontspec, 419 glue, 87 gluespec, 3 kern, 647 mathspec, 4 penalty, 2 temp, 591 whatsit mkiv lua stats > node list callback tasks: 13 unique task lists, 17 instances (re)created, 325895 calls mkiv lua stats > h-node processing time: 10.654 seconds including kernel mkiv lua stats > attribute processing time: 2.810 seconds front- and backend mkiv lua stats > driver time: 11.714 seconds mkiv lua stats > used backend: pdf mkiv lua stats > jobdata time: 0.810 seconds saving, 0.194 seconds loading mkiv lua stats > callbacks: file: 5439, saved: 644924, direct: 1386, function: 534140, value: 1033, message: 0, bytecode: 613, late 0, total: 1187535 (1151 per page) mkiv lua stats > randomizer: resumed with value 0.58701179146283 mkiv lua stats > v-node processing time: 1.480 seconds mkiv lua stats > loaded patterns: en::1 it::66, load time: 0.000 mkiv lua stats > xml load time: 0.444 seconds, 1 files, 1 converted mkiv lua stats > lxml preparation time: 26.359 seconds, 47936 nodes, 24702 lpath calls, 24331 cached calls mkiv lua stats > interactive elements: 9327 references, 12951 destinations mkiv lua stats > margin data: 6 entries, 0 pending mkiv lua stats > loaded fonts: 27 files: lmmono10-regular.otf, texgyrepagella-math.otf, dejavusansmono.ttf, gfsneohellenic.otf, firasans-bolditalic.otf, firasans-regular.otf, firasans-regularitalic.otf, firasanscondensed-bold.otf, firasanscondensed-regular.otf, garamondpremrpro-bdit.otf, garamondpremrpro-med.otf, garamondpremrpro-medcapt.otf, garamondpremrpro-meddisp.otf, garamondpremrpro-medit.otf, garamondpremrpro-meditcapt.otf, garamondpremrpro-medsubh.otf, garamondpremrpro-smbdit.otf, myriadpro-bold.otf, myriadpro-boldcond.otf, myriadpro-boldcondit.otf, myriadpro-cond.otf, myriadpro-condit.otf, myriadpro-it.otf, myriadpro-regular.otf, myriadpro-semiboldit.otf, quivira.otf, sileot.ttf mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 46 instances, 16 shared in backend, 4 common vectors, 12 common hashes, load time 0.148 seconds mkiv lua stats > text directions: 5.911 seconds mkiv lua stats > metapost: 1.180 seconds, loading: 0.083, execution: 1.109, n: 1039, average: 0.002, instances: 2, luacalls: 46885 (file: 34713, text: 0, script: 5932, log: 6240), memory: 8.995 M mkiv lua stats > math tweaking time: 0.462 seconds, 8 math goodie tables mkiv lua stats > math processing time: 0.211 seconds mkiv lua stats > pdf annotations: 9327 links (9316 unique), 0 special mkiv lua stats > font embedding time: 0.104 seconds, 23 fonts mkiv lua stats > result saved in file: v32.pdf, compresslevel 0, objectcompresslevel 0 mkiv lua stats > positions: 8572 collected, 4774 deltas, 8565 shared partials, 305 partial entries mkiv lua stats > used platform: linux-64, type: unix, binary subtree: texmf-linux-64 mkiv lua stats > used engine: luametatex version: 2.1004, functionality level: 20221214, format id: 679, compiler: gcc mkiv lua stats > tex properties: 740852 hash slots used of 2097152, 93821 control sequences, approximate memory usage: 65 MB mkiv lua stats > lua properties: engine: lua 5.4, used memory: 338 MB, ctx: 266 MB, max: 415 MB, symbol mask: utf (τεχ) mkiv lua stats > runtime: 114.917 seconds, 1032 processed pages, 1032 shipped pages, 8.980 pages/second It's better, but the
Re: [NTG-context] bottlenecks
latest ConTeXt 2022.12.15 18:12: mkiv lua stats > resource resolver: loadtime 0.009 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 107 found files, scanned paths: mkiv lua stats > stored bytecode data: 507 modules (0.346 sec), 106 tables (0.023 sec), 613 chunks (0.369 sec) mkiv lua stats > traced context: maxstack: 1923, freed: 246, unreachable: 1677 mkiv lua stats > cleaned up reserved nodes: 76 nodes, 9 lists of 504 mkiv lua stats > node memory usage: 1684 attribute, 419 glue, 87 gluespec, 3 kern, 647 mathspec, 4 penalty, 2 temp, 591 whatsit mkiv lua stats > node list callback tasks: 13 unique task lists, 17 instances (re)created, 325602 calls mkiv lua stats > h-node processing time: 10.442 seconds including kernel mkiv lua stats > attribute processing time: 2.783 seconds front- and backend mkiv lua stats > driver time: 11.187 seconds mkiv lua stats > used backend: pdf mkiv lua stats > jobdata time: 0.747 seconds saving, 0.195 seconds loading mkiv lua stats > callbacks: file: 5438, saved: 644352, direct: 1374, function: 540269, value: 1027, message: 0, bytecode: 613, late 0, total: 1193073 (1163 per page) mkiv lua stats > randomizer: resumed with value 0.58701179146283 mkiv lua stats > v-node processing time: 1.955 seconds mkiv lua stats > loaded patterns: en::1 it::66, load time: 0.000 mkiv lua stats > xml load time: 0.416 seconds, 1 files, 1 converted mkiv lua stats > lxml preparation time: 29.478 seconds, 47936 nodes, 24702 lpath calls, 24331 cached calls mkiv lua stats > interactive elements: 9336 references, 12951 destinations mkiv lua stats > margin data: 6 entries, 0 pending mkiv lua stats > loaded fonts: 27 files: lmmono10-regular.otf, texgyrepagella-math.otf, dejavusansmono.ttf, gfsneohellenic.otf, firasans-bolditalic.otf, firasans-regular.otf, firasans-regularitalic.otf, firasanscondensed-bold.otf, firasanscondensed-regular.otf, garamondpremrpro-bdit.otf, garamondpremrpro-med.otf, garamondpremrpro-medcapt.otf, garamondpremrpro-meddisp.otf, garamondpremrpro-medit.otf, garamondpremrpro-meditcapt.otf, garamondpremrpro-medsubh.otf, garamondpremrpro-smbdit.otf, myriadpro-bold.otf, myriadpro-boldcond.otf, myriadpro-boldcondit.otf, myriadpro-cond.otf, myriadpro-condit.otf, myriadpro-it.otf, myriadpro-regular.otf, myriadpro-semiboldit.otf, quivira.otf, sileot.ttf mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 533 instances, 501 shared in backend, 6 common vectors, 495 common hashes, load time 0.196 seconds mkiv lua stats > text directions: 5.754 seconds mkiv lua stats > metapost: 1.182 seconds, loading: 0.129, execution: 1.112, n: 1033, average: 0.002, instances: 2, luacalls: 46777 (file: 34671, text: 0, script: 5902, log: 6204), memory: 8.992 M mkiv lua stats > math tweaking time: 5.640 seconds, 126 math goodie tables mkiv lua stats > math processing time: 0.251 seconds mkiv lua stats > pdf annotations: 9336 links (9326 unique), 0 special mkiv lua stats > font embedding time: 0.049 seconds, 23 fonts mkiv lua stats > result saved in file: v32.pdf, compresslevel 0, objectcompresslevel 0 mkiv lua stats > positions: 8563 collected, 4775 deltas, 8556 shared partials, 304 partial entries mkiv lua stats > used platform: linux-64, type: unix, binary subtree: texmf-linux-64 mkiv lua stats > used engine: luametatex version: 2.1004, functionality level: 20221214, format id: 679, compiler: gcc mkiv lua stats > tex properties: 740852 hash slots used of 2097152, 94301 control sequences, approximate memory usage: 385 MB mkiv lua stats > lua properties: engine: lua 5.4, used memory: 1527 MB, ctx: 1436 MB, max: 1585 MB, symbol mask: utf (τεχ) mkiv lua stats > runtime: 130.080 seconds, 1026 processed pages, 1026 shipped pages, 7.887 pages/second system | total runtime: 130.269 seconds of 130.342 seconds ConTeXt 2020-04-22: mkiv lua stats > resource resolver: loadtime 0.005 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 124 found files, scanned paths: mkiv lua stats > stored bytecode data: 468 modules (0.349 sec), 93 tables (0.030 sec), 561 chunks (0.378 sec) mkiv lua stats > traced context: maxstack: 2799, freed: 246, unreachable: 2553 mkiv lua stats > cleaned up reserved nodes: 61 nodes, 11 lists of 512 mkiv lua stats > node memory usage: 200320 attribute, 23928 attribute_list, 419 glue, 368 glue_spec, 27234 glyph, 3 kern, 4 penalty, 2 temp, 1159 whatsit mkiv lua stats > node list callback tasks: 8 unique task lists, 14 instances (re)created, 236679 calls mkiv lua stats > h-node processing time: 13.188 seconds including kernel mkiv lua stats > attribute processing time: 5.444 seconds front- and backend mkiv lua stats > driver time: 12.650 seconds mkiv lua stats > used backend: lmtx version 0.10, pdf (backend for directly gener
Re: [NTG-context] bottlenecks
With lots of MetaPost, lots of references, lots of figures, lots of tables, lots of bibliography entries, lots of chemical structures, ... mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua mkiv lua stats > used cache path: /home/braslau/context/beta/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e mkiv lua stats > resource resolver: loadtime 0.003 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 98 found files, scanned paths: mkiv lua stats > stored bytecode data: 507 modules (0.117 sec), 106 tables (0.000 sec), 613 chunks (0.117 sec) mkiv lua stats > traced context: maxstack: 5959, freed: 2352, unreachable: 3607 mkiv lua stats > cleaned up reserved nodes: 101 nodes, 15 lists of 439 mkiv lua stats > node memory usage: 2491 attribute, 76 boundary, 84 dir, 1167 glue, 85 gluespec, 430 glyph, 242 hlist, 333 kern, 32 math, 647 mathspec, 238 par, 328 penalty, 88 rule, 2 temp, 100 vlist, 18 whatsit mkiv lua stats > node list callback tasks: 13 unique task lists, 376 instances (re)created, 147276 calls mkiv lua stats > h-node processing time: 4.724 seconds including kernel mkiv lua stats > attribute processing time: 0.202 seconds front- and backend mkiv lua stats > driver time: 1.419 seconds mkiv lua stats > used backend: pdf mkiv lua stats > jobdata time: 0.224 seconds saving, 0.068 seconds loading mkiv lua stats > callbacks: file: 32365, saved: 278423, direct: 486, function: 259776, value: 579, message: 0, bytecode: 613, late 0, total: 572242 (990 per page) mkiv lua stats > randomizer: resumed with value 0.86690391712354 mkiv lua stats > v-node processing time: 0.186 seconds mkiv lua stats > loaded tex modules: 2 requested, all found (*-graph *-three) mkiv lua stats > loaded patterns: de::3 en::1 fr::63, load time: 0.000 mkiv lua stats > interactive elements: 12106 references, 5886 destinations mkiv lua stats > loaded fonts: 5 files: cambria.ttc, cambriab.ttf, cambriai.ttf, dejavusansmono-oblique.ttf, dejavusansmono.ttf mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 73 instances, 65 shared in backend, 5 common vectors, 60 common hashes, load time 1.571 seconds mkiv lua stats > body font sizes: defined: 10pt 11pt 12pt 14.4pt 17.3pt 20.7pt 4pt 5pt 6pt 7pt 8pt 9pt, undefined: 18pt 21.6pt mkiv lua stats > metapost: 1.277 seconds, loading: 0.083, execution: 1.260, n: 881, average: 0.003, instances: 6, luacalls: 108876 (file: 90144, text: 0, script: 10120, log: 8568), memory: 30.514 M mkiv lua stats > math tweaking time: 0.852 seconds, 96 math goodie tables mkiv lua stats > math processing time: 0.158 seconds mkiv lua stats > chemical formulas: 58 chemical structure formulas mkiv lua stats > graphics processing time: 0.414 seconds including tex, 264 processed images, 220 unique asked, 200 bad names mkiv lua stats > publications load time: 0.026 seconds, 584341 bytes, 835 definitions, 14 shortcuts mkiv lua stats > pdf annotations: 12106 links (11765 unique), 0 special mkiv lua stats > font embedding time: 0.016 seconds, 7 fonts mkiv lua stats > result saved in file: Cristaux_Liquides_tome2.pdf, compresslevel 1, objectcompresslevel 3 mkiv lua stats > positions: 2708 collected, 769 deltas, 2645 shared partials, 484 partial entries mkiv lua stats > cross referencing: 13943 identified, 34 unknown mkiv lua stats > used platform: freebsd-amd64, type: unix, binary subtree: texmf-freebsd-amd64 mkiv lua stats > used engine: luametatex version: 2.1004, functionality level: 20221214, format id: 679, compiler: clang mkiv lua stats > tex properties: 740852 hash slots used of 2097152, 50741 control sequences, approximate memory usage: 125 MB mkiv lua stats > lua properties: engine: lua 5.4, used memory: 301 MB, ctx: 275 MB, max: 445 MB, symbol mask: utf (τεχ) mkiv lua stats > runtime: 17.027 seconds, 578 processed pages, 578 shipped pages, 33.946 pages/second system | total runtime: 68.547 seconds of 68.576 seconds Alan ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] bottlenecks
On 12/17/2022 4:05 PM, Rik Kabel via ntg-context wrote: On 2022-12-17 04:48, Hans Hagen via ntg-context wrote: On 12/17/2022 1:05 AM, Rik Kabel via ntg-context wrote: The laptop was hot stuff in 2017 with 16GB RAM, 1TB SSD, and a 4K touch screen -- today, not so hot. Due to be replaced next year. so a bit like the surface i have as spare (which was slower than the 2013 precission that i recently replaced by a 2018 one) Here are the numbers without compact fonts enabled. Not much difference. mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 84 instances, 67 shared in backend, 3 common vectors, 64 common hashes, load time 1.076 seconds which means that you don't run in compact mode Indeed, I had a typo. Running with compact fonts, I get: mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua mkiv lua stats > used cache path: C:/ConTeXt_LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e mkiv lua stats > resource resolver: loadtime 0.045 seconds, 1 scans with scantime 0.037 seconds, 0 shared scans, 37 found files, scanned paths: C:/Users/micro/texmf mkiv lua stats > stored bytecode data: 507 modules (0.267 sec), 106 tables (0.015 sec), 613 chunks (0.282 sec) mkiv lua stats > traced context: maxstack: 4108, freed: 2453, unreachable: 1655 mkiv lua stats > cleaned up reserved nodes: 78 nodes, 8 lists of 438 mkiv lua stats > node memory usage: 6860 attribute, 4602 dir, 69 fontspec, 4606 glue, 84 gluespec, 2301 glyph, 3068 hlist, 3 kern, 647 mathspec, 5 penalty, 2 temp mkiv lua stats > node list callback tasks: 13 unique task lists, 37 instances (re)created, 87134 calls mkiv lua stats > h-node processing time: 3.146 seconds including kernel mkiv lua stats > inserted spaces in output: 106025 mkiv lua stats > attribute processing time: 0.248 seconds front- and backend mkiv lua stats > driver time: 2.425 seconds mkiv lua stats > used backend: pdf mkiv lua stats > jobdata time: 0.198 seconds saving, 0.059 seconds loading mkiv lua stats > callbacks: file: 34385, saved: 191160, direct: 8, function: 173538, value: 345, message: 0, bytecode: 613, late 0, total: 400049 (1184 per page) mkiv lua stats > randomizer: resumed with value 0.88558194690977 mkiv lua stats > v-node processing time: 0.208 seconds mkiv lua stats > loaded patterns: agr:gr:62 cn::58 de::3 deo:de:9 en::1 es::64 fr::63 it::66 la::67 ru::22, load time: 0.000 mkiv lua stats > structure elements: 28148 element chains identified mkiv lua stats > interactive elements: 3983 references, 4873 destinations mkiv lua stats > margin data: 497 entries, 0 pending mkiv lua stats > loaded fonts: 14 files: antykwatorunska-bold.otf, antykwatorunskacond-bold.otf, antykwatorunskacond-regular.otf, libertinusmath-regular.otf, libertinusmono-regular.otf, libertinussans-italic.otf, libertinussans-regular.otf, libertinusserif-italic.otf, libertinusserif-regular.otf, libertinusserif-semibold.otf, zentb___.otf, keteraramtsova.ttf, msjh.ttc, times.ttf *mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 18 instances, 2 shared in backend, 2 common vectors, 0 common hashes, load time 0.534 seconds * mkiv lua stats > text directions: 4.229 seconds mkiv lua stats > math tweaking time: 0.023 seconds, 2 math goodie tables mkiv lua stats > pdf annotations: 3983 links (3983 unique), 0 special mkiv lua stats > font embedding time: 0.055 seconds, 13 fonts mkiv lua stats > result saved in file: misquotation_bodyonly.pdf, compresslevel 1, objectcompresslevel 3 mkiv lua stats > positions: 4034 collected, 1723 deltas, 4025 shared partials, 111 partial entries mkiv lua stats > used platform: win64, type: windows, binary subtree: texmf-win64 mkiv lua stats > used engine: luametatex version: 2.1004, functionality level: 20221214, format id: 679, compiler: gcc mkiv lua stats > tex properties: 740852 hash slots used of 2097152, 51822 control sequences, approximate memory usage: 41 MB mkiv lua stats > lua properties: engine: lua 5.4, used memory: 225 MB, ctx: 200 MB, max: 200 MB, symbol mask: utf (τεχ) mkiv lua stats > runtime: 19.993 seconds, 338 processed pages, 338 shipped pages, 16.906 pages/second but the overall runtime is essentially unchanged. interesting, normally we gain something (ok, at least one gains memory) I do have some macros that are likely to make you (and others who are more adept at such things) cringe. Happy to share more of the source if it is helpful. sure I have also run with --profile and have attached that log as well as the complete execution log (zipped together as logs.zip). here are a few: 0.613002300 s 0.138 % 0.609968531 s 0.160 % 3674 # prerollreference 0.420704300 s 0.095 % 0.420702649 s 0.110 % 2 # analyzeregister 0.425307400 s 0.096 %
Re: [NTG-context] bottlenecks
On 2022-12-17 04:48, Hans Hagen via ntg-context wrote: On 12/17/2022 1:05 AM, Rik Kabel via ntg-context wrote: The laptop was hot stuff in 2017 with 16GB RAM, 1TB SSD, and a 4K touch screen -- today, not so hot. Due to be replaced next year. so a bit like the surface i have as spare (which was slower than the 2013 precission that i recently replaced by a 2018 one) Here are the numbers without compact fonts enabled. Not much difference. mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 84 instances, 67 shared in backend, 3 common vectors, 64 common hashes, load time 1.076 seconds which means that you don't run in compact mode Indeed, I had a typo. Running with compact fonts, I get: mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua mkiv lua stats > used cache path: C:/ConTeXt_LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e mkiv lua stats > resource resolver: loadtime 0.045 seconds, 1 scans with scantime 0.037 seconds, 0 shared scans, 37 found files, scanned paths: C:/Users/micro/texmf mkiv lua stats > stored bytecode data: 507 modules (0.267 sec), 106 tables (0.015 sec), 613 chunks (0.282 sec) mkiv lua stats > traced context: maxstack: 4108, freed: 2453, unreachable: 1655 mkiv lua stats > cleaned up reserved nodes: 78 nodes, 8 lists of 438 mkiv lua stats > node memory usage: 6860 attribute, 4602 dir, 69 fontspec, 4606 glue, 84 gluespec, 2301 glyph, 3068 hlist, 3 kern, 647 mathspec, 5 penalty, 2 temp mkiv lua stats > node list callback tasks: 13 unique task lists, 37 instances (re)created, 87134 calls mkiv lua stats > h-node processing time: 3.146 seconds including kernel mkiv lua stats > inserted spaces in output: 106025 mkiv lua stats > attribute processing time: 0.248 seconds front- and backend mkiv lua stats > driver time: 2.425 seconds mkiv lua stats > used backend: pdf mkiv lua stats > jobdata time: 0.198 seconds saving, 0.059 seconds loading mkiv lua stats > callbacks: file: 34385, saved: 191160, direct: 8, function: 173538, value: 345, message: 0, bytecode: 613, late 0, total: 400049 (1184 per page) mkiv lua stats > randomizer: resumed with value 0.88558194690977 mkiv lua stats > v-node processing time: 0.208 seconds mkiv lua stats > loaded patterns: agr:gr:62 cn::58 de::3 deo:de:9 en::1 es::64 fr::63 it::66 la::67 ru::22, load time: 0.000 mkiv lua stats > structure elements: 28148 element chains identified mkiv lua stats > interactive elements: 3983 references, 4873 destinations mkiv lua stats > margin data: 497 entries, 0 pending mkiv lua stats > loaded fonts: 14 files: antykwatorunska-bold.otf, antykwatorunskacond-bold.otf, antykwatorunskacond-regular.otf, libertinusmath-regular.otf, libertinusmono-regular.otf, libertinussans-italic.otf, libertinussans-regular.otf, libertinusserif-italic.otf, libertinusserif-regular.otf, libertinusserif-semibold.otf, zentb___.otf, keteraramtsova.ttf, msjh.ttc, times.ttf *mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 18 instances, 2 shared in backend, 2 common vectors, 0 common hashes, load time 0.534 seconds * mkiv lua stats > text directions: 4.229 seconds mkiv lua stats > math tweaking time: 0.023 seconds, 2 math goodie tables mkiv lua stats > pdf annotations: 3983 links (3983 unique), 0 special mkiv lua stats > font embedding time: 0.055 seconds, 13 fonts mkiv lua stats > result saved in file: misquotation_bodyonly.pdf, compresslevel 1, objectcompresslevel 3 mkiv lua stats > positions: 4034 collected, 1723 deltas, 4025 shared partials, 111 partial entries mkiv lua stats > used platform: win64, type: windows, binary subtree: texmf-win64 mkiv lua stats > used engine: luametatex version: 2.1004, functionality level: 20221214, format id: 679, compiler: gcc mkiv lua stats > tex properties: 740852 hash slots used of 2097152, 51822 control sequences, approximate memory usage: 41 MB mkiv lua stats > lua properties: engine: lua 5.4, used memory: 225 MB, ctx: 200 MB, max: 200 MB, symbol mask: utf (τεχ) mkiv lua stats > runtime: 19.993 seconds, 338 processed pages, 338 shipped pages, 16.906 pages/second but the overall runtime is essentially unchanged. I do have some macros that are likely to make you (and others who are more adept at such things) cringe. Happy to share more of the source if it is helpful. sure I have also run with --profile and have attached that log as well as the complete execution log (zipped together as logs.zip). here are a few: 0.613002300 s 0.138 % 0.609968531 s 0.160 % 3674 # prerollreference 0.420704300 s 0.095 % 0.420702649 s 0.110 % 2 # analyzeregister 0.425307400 s 0.096 % 0.425299968 s 0.111 % 9 # action 1358 ...MTX/tex/texmf-context/tex/con
Re: [NTG-context] bottlenecks
On 2022-12-16 17:07, Hans Hagen via ntg-context wrote: On 12/16/2022 10:08 PM, Rik Kabel via ntg-context wrote: Hans, Here are the stats for a 346 page book. Fonts are all cached. Compilation is via a make file which processes this as: context --noconsole --overloadmode=error --batchmode --nonstopmode --nosynctex misquotation_bodyonly.mkvi > nul and is run under W11 x64 on an i7-8550U. The only tables are contents ok, not the fastest i7 out there, more the tablet one, right? and acronyms, and such, nothing complex. No graphics. Compact fonts are enabled. can you check compact mode .. when compact fonts are not enabled, do you get the same > mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 84 > instances, 67 shared in backend, 3 common vectors, 64 common hashes, i wonder why so many instances mkiv lua stats > node memory usage: 6869 attribute, 4608 dir, 4612 glue, 84 gluespec, 2304 glyph, 3072 hlist, 3 kern, 647 mathspec, 5 penalty, 2 temp this is suspicious ... i fixed a dir leak recently but having 3K boxes dangling ... In neither case do the sum of the times listed in the stats come close to the total runtime (in the second example, 14.774 seconds of 23.057 are accounted), so there are other unidentified processes involved. these stats are an indication because below a threshold (time accuracy) nothing is measured In any case, the processing time has been improving greatly over the last couple of years, and LMTX is significantly faster that MkIV in all of my work. sure, that is to be expected although it depends a bit on the use case, for instance the backend is slower (but does much more) so initially lmtx was actually slower but at some point we started gaining (and i can probably gain a little more) i wonder why directions bump time because much of what tex does is sort of agnostic for directions (the backend needs more time but i don't see that in your stats) when you run with --profile you get a much slower run but might get some info from the extra log Hans The laptop was hot stuff in 2017 with 16GB RAM, 1TB SSD, and a 4K touch screen -- today, not so hot. Due to be replaced next year. Here are the numbers without compact fonts enabled. Not much difference. mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua mkiv lua stats > used cache path: C:/ConTeXt_LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e mkiv lua stats > resource resolver: loadtime 0.045 seconds, 1 scans with scantime 0.037 seconds, 0 shared scans, 37 found files, scanned paths: C:/Users/micro/texmf mkiv lua stats > stored bytecode data: 507 modules (0.243 sec), 106 tables (0.016 sec), 613 chunks (0.259 sec) mkiv lua stats > traced context: maxstack: 4107, freed: 2452, unreachable: 1655 mkiv lua stats > cleaned up reserved nodes: 78 nodes, 8 lists of 438 mkiv lua stats > node memory usage: 6869 attribute, 4608 dir, 4612 glue, 84 gluespec, 2304 glyph, 3072 hlist, 3 kern, 647 mathspec, 5 penalty, 2 temp mkiv lua stats > node list callback tasks: 13 unique task lists, 37 instances (re)created, 87130 calls mkiv lua stats > h-node processing time: 3.454 seconds including kernel mkiv lua stats > inserted spaces in output: 106016 mkiv lua stats > attribute processing time: 0.295 seconds front- and backend mkiv lua stats > driver time: 2.487 seconds mkiv lua stats > used backend: pdf mkiv lua stats > jobdata time: 0.290 seconds saving, 0.053 seconds loading mkiv lua stats > callbacks: file: 34388, saved: 191153, direct: 8, function: 173574, value: 345, message: 0, bytecode: 613, late 0, total: 400081 (1184 per page) mkiv lua stats > randomizer: resumed with value 0.88558194690977 mkiv lua stats > v-node processing time: 0.250 seconds mkiv lua stats > loaded patterns: agr:gr:62 cn::58 de::3 deo:de:9 en::1 es::64 fr::63 it::66 la::67 ru::22, load time: 0.000 mkiv lua stats > structure elements: 28145 element chains identified mkiv lua stats > interactive elements: 3982 references, 4873 destinations mkiv lua stats > margin data: 497 entries, 0 pending mkiv lua stats > loaded fonts: 14 files: antykwatorunska-bold.otf, antykwatorunskacond-bold.otf, antykwatorunskacond-regular.otf, libertinusmath-regular.otf, libertinusmono-regular.otf, libertinussans-italic.otf, libertinussans-regular.otf, libertinusserif-italic.otf, libertinusserif-regular.otf, libertinusserif-semibold.otf, zentb___.otf, keteraramtsova.ttf, msjh.ttc, times.ttf mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 84 instances, 67 shared in backend, 3 common vectors, 64 common hashes, load time 1.076 seconds mkiv lua stats > text directions: 4.987 seconds mkiv lua
Re: [NTG-context] bottlenecks
Hans, Here are the stats for a 346 page book. Fonts are all cached. Compilation is via a make file which processes this as: context --noconsole --overloadmode=error --batchmode --nonstopmode --nosynctex misquotation_bodyonly.mkvi > nul and is run under W11 x64 on an i7-8550U. The only tables are contents and acronyms, and such, nothing complex. No graphics. Compact fonts are enabled. mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua mkiv lua stats > used cache path: C:/ConTeXt_LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e mkiv lua stats > resource resolver: loadtime 0.042 seconds, 1 scans with scantime 0.035 seconds, 0 shared scans, 37 found files, scanned paths: C:/Users/micro/texmf mkiv lua stats > stored bytecode data: 507 modules (0.236 sec), 106 tables (0.015 sec), 613 chunks (0.251 sec) mkiv lua stats > traced context: maxstack: 4107, freed: 2452, unreachable: 1655 mkiv lua stats > cleaned up reserved nodes: 78 nodes, 8 lists of 438 mkiv lua stats > node memory usage: 6869 attribute, 4608 dir, 4612 glue, 84 gluespec, 2304 glyph, 3072 hlist, 3 kern, 647 mathspec, 5 penalty, 2 temp mkiv lua stats > node list callback tasks: 13 unique task lists, 37 instances (re)created, 87130 calls mkiv lua stats > h-node processing time: 3.010 seconds including kernel mkiv lua stats > inserted spaces in output: 106016 mkiv lua stats > attribute processing time: 0.236 seconds front- and backend mkiv lua stats > driver time: 2.099 seconds mkiv lua stats > used backend: pdf mkiv lua stats > jobdata time: 0.191 seconds saving, 0.051 seconds loading mkiv lua stats > callbacks: file: 34388, saved: 191153, direct: 8, function: 173575, value: 345, message: 0, bytecode: 613, late 0, total: 400082 (1184 per page) mkiv lua stats > randomizer: resumed with value 0.88558194690977 mkiv lua stats > v-node processing time: 0.194 seconds mkiv lua stats > loaded patterns: agr:gr:62 cn::58 de::3 deo:de:9 en::1 es::64 fr::63 it::66 la::67 ru::22, load time: 0.000 mkiv lua stats > structure elements: 28145 element chains identified mkiv lua stats > interactive elements: 3982 references, 4873 destinations mkiv lua stats > margin data: 497 entries, 0 pending mkiv lua stats > loaded fonts: 14 files: antykwatorunska-bold.otf, antykwatorunskacond-bold.otf, antykwatorunskacond-regular.otf, libertinusmath-regular.otf, libertinusmono-regular.otf, libertinussans-italic.otf, libertinussans-regular.otf, libertinusserif-italic.otf, libertinusserif-regular.otf, libertinusserif-semibold.otf, zentb___.otf, keteraramtsova.ttf, msjh.ttc, times.ttf mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 84 instances, 67 shared in backend, 3 common vectors, 64 common hashes, load time 0.947 seconds mkiv lua stats > text directions: 4.273 seconds mkiv lua stats > math tweaking time: 0.152 seconds, 18 math goodie tables mkiv lua stats > pdf annotations: 3982 links (3982 unique), 0 special mkiv lua stats > font embedding time: 0.058 seconds, 13 fonts mkiv lua stats > result saved in file: misquotation_bodyonly.pdf, compresslevel 1, objectcompresslevel 3 mkiv lua stats > positions: 4034 collected, 1722 deltas, 4025 shared partials, 112 partial entries mkiv lua stats > used platform: win64, type: windows, binary subtree: texmf-win64 mkiv lua stats > used engine: luametatex version: 2.1004, functionality level: 20221214, format id: 679, compiler: gcc mkiv lua stats > tex properties: 740852 hash slots used of 2097152, 51846 control sequences, approximate memory usage: 73 MB mkiv lua stats > lua properties: engine: lua 5.4, used memory: 315 MB, ctx: 288 MB, max: 288 MB, symbol mask: utf (τεχ) mkiv lua stats > runtime: 19.332 seconds, 338 processed pages, 338 shipped pages, 17.484 pages/second and here are the stats for the same book with pdf images replacing some of the text (I still don't have rights to some images, so preparing either way): mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua mkiv lua stats > used cache path: C:/ConTeXt_LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e mkiv lua stats > resource resolver: loadtime 0.044 seconds, 1 scans with scantime 0.037 seconds, 0 shared scans, 62 found files, scanned paths: C:/Users/micro/texmf mkiv lua stats > stored bytecode data: 507 modules (0.236 sec), 106 tables (0.015 sec), 613 chunks (0.251 sec) mkiv lua stats > traced context: maxstack: 4112, freed: 2457, unreachable: 1655 mkiv lua stats > cleaned up reserved nodes: 78 nodes, 8 lists of 438 mkiv lua stats > node me
Re: [NTG-context] bottlenecks
On 12/16/2022 8:36 PM, Henning Hraban Ramm via ntg-context wrote: Am 16.12.22 um 18:10 schrieb Hans Hagen via ntg-context: So the challenge is how to determine bottlenecks. Are there users on this list that have document runs of more than 10 seconds (as reference: the luametatex manual takes < 9 seconds for 350 pages and loads plenty fonts and has many tables) or have many (small) runs and are annoyed by the runtime? And if so, what does one guess are the bottlenecks? (1) This is my 366 page ConTeXt book: mkiv lua stats > runtime: 30.592 seconds, 366 processed pages, 366 shipped pages, 11.964 pages/second (2) This is a 720 page novel (first run with this LMTX version, some fonts were still uncached): mkiv lua stats > runtime: 19.275 seconds, 720 processed pages, 720 shipped pages, 37.355 pages/second so what if you add to the top \enableexperiments[fonts.compact] 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] bottlenecks
Am 16.12.22 um 18:10 schrieb Hans Hagen via ntg-context: So the challenge is how to determine bottlenecks. Are there users on this list that have document runs of more than 10 seconds (as reference: the luametatex manual takes < 9 seconds for 350 pages and loads plenty fonts and has many tables) or have many (small) runs and are annoyed by the runtime? And if so, what does one guess are the bottlenecks? (1) This is my 366 page ConTeXt book: mkiv lua stats > used config file: home:texmf/web2c/texmfcnf.lua;selfautoparent:/texmf/web2c/texmfcnf.lua mkiv lua stats > used cache path: /Users/hraban/lmtx/tex/texmf-cache/luametatex-cache/context/c821363a6b068765c2a3bbfe3917fcf5 mkiv lua stats > resource resolver: loadtime 0.046 seconds, 1 scans with scantime 0.037 seconds, 0 shared scans, 165 found files, scanned paths: /Users/hraban/texmf mkiv lua stats > stored bytecode data: 507 modules (0.378 sec), 106 tables (0.017 sec), 613 chunks (0.395 sec) mkiv lua stats > traced context: maxstack: 3112, freed: 1448, unreachable: 1664 mkiv lua stats > cleaned up reserved nodes: 202 nodes, 22 lists of 517 mkiv lua stats > node memory usage: 1137 attribute, 46 dir, 559 glue, 82 gluespec, 177 glyph, 236 hlist, 3 kern, 647 mathspec, 48 penalty, 2 submlist, 2 temp mkiv lua stats > node list callback tasks: 13 unique task lists, 180 instances (re)created, 216502 calls mkiv lua stats > h-node processing time: 2.544 seconds including kernel mkiv lua stats > synctex tracing: 46 referenced files, 22 files ignored, 41808 objects flushed, logfile: prd_de.synctex mkiv lua stats > attribute processing time: 0.201 seconds front- and backend mkiv lua stats > driver time: 5.265 seconds mkiv lua stats > used backend: pdf mkiv lua stats > jobdata time: 0.271 seconds saving, 0.056 seconds loading mkiv lua stats > callbacks: file: 26780, saved: 405242, direct: 524, function: 281755, value: 2288, message: 0, bytecode: 613, late 0, total: 717202 (1960 per page) mkiv lua stats > randomizer: resumed with value 0.57895496379132 mkiv lua stats > v-node processing time: 1.464 seconds mkiv lua stats > loaded tex modules: 10 requested, all found (*-filter *-libs-imp-zint *-module-catcodes *-s-fonts-show *-s-symbols-show *-scite *-syntax-groups *-syntax-highlight *-vim *-visual) mkiv lua stats > loaded patterns: de::3 en::1, load time: 0.000 mkiv lua stats > xml load time: 0.002 seconds, 1 files, 1 converted mkiv lua stats > lxml preparation time: 0.000 seconds, 0 nodes, 31 lpath calls, 4 cached calls mkiv lua stats > interactive elements: 2536 references, 2870 destinations mkiv lua stats > margin data: 295 entries, 1 pending mkiv lua stats > loaded fonts: 31 files: latinmodern-math.otf, lmmono10-italic.otf, lmmono10-regular.otf, lmmonocaps10-regular.otf, lmmonolt10-bold.otf, lmmonolt10-boldoblique.otf, lmmonoltcond10-regular.otf, lmmonoslant10-regular.otf, lmroman10-bold.otf, lmroman10-italic.otf, lmroman10-regular.otf, lmromancaps10-regular.otf, lmsans10-oblique.otf, lmsans10-regular.otf, cc-icons.ttf, dejavusansmono.ttf, marvosym.ttf, font awesome 5 brands-regular-400.otf, font awesome 5 free-regular-400.otf, font awesome 5 free-solid-900.otf, cambria.ttc, cambriab.ttf, cambriai.ttf, cambriaz.ttf, segoe ui bold italic.ttf, segoe ui bold.ttf, segoe ui italic.ttf, segoe ui.ttf, segoepr.ttf, symbola.otf, unifrakturmaguntia.ttf (suspicious x height) mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 193 instances, 157 shared in backend, 11 common vectors, 146 common hashes, load time 15.349 seconds mkiv lua stats > body font sizes: defined: 10pt 11pt 12pt 14.4pt 17.3pt 20.7pt 4pt 5pt 6pt 7pt 8pt 9pt, undefined: 11.2pt 14pt 16.8pt mkiv lua stats > visualization time: 0.154 seconds mkiv lua stats > metapost: 0.678 seconds, loading: 0.092, execution: 0.651, n: 528, average: 0.003, instances: 2, luacalls: 37745 (file: 31092, text: 0, script: 3507, log: 3146), memory: 8.825 M mkiv lua stats > math tweaking time: 8.659 seconds, 116 math goodie tables mkiv lua stats > math processing time: 0.012 seconds mkiv lua stats > graphics processing time: 2.885 seconds including tex, 247 processed images, 69 unique asked, 42 bad names mkiv lua stats > pdf annotations: 2536 links (2535 unique), 0 special mkiv lua stats > font embedding time: 0.084 seconds, 31 fonts mkiv lua stats > result saved in file: prd_de.pdf, compresslevel 1, objectcompresslevel 0 mkiv lua stats > positions: 6786 collected, 3635 deltas, 6678 shared partials, 46 partial entries mkiv lua stats > used platform: osx-64, type: unix, binary subtree: texmf-osx-64 mkiv lua stats > used engine: luametatex version: 2.1004, functionality level: 20221208, format id: 678, compiler: clang mkiv lua stats > tex properties: 740852 hash slots used of 2097152, 59643 control sequences, approximate m
[NTG-context] bottlenecks
Hi, I'm (occasionally) trying to 'minimize' bottlenecks in the context / luametatex code. This is kind of hard because both are rather efficient already. On regular runs performance is probably okay but there are cases when one has a large complex document (e.g. with many tables) or has many runs (e.g. thousands of documents in one go). In that case even minor speedups can accumulate and become measurable (esp on vms and runs over a network). It can safe time and also energy (which can matter todays KWh pricing). So the challenge is how to determine bottlenecks. Are there users on this list that have document runs of more than 10 seconds (as reference: the luametatex manual takes < 9 seconds for 350 pages and loads plenty fonts and has many tables) or have many (small) runs and are annoyed by the runtime? And if so, what does one guess are the bottlenecks? Hans ps. Much runtime is spent in Lua and there is not that much we can do about making that faster. - 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://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] two issues with variable fonts
On 12/2/2022 7:06 PM, Pablo Rodriguez via ntg-context wrote: Hi Hans, I have two issues with variable fonts (using current latest from yesterday): 1. Using the following sample: \usemodule[fonts-variable] \starttext \showfontvariations[font=file:grenze.ttf] \stoptext With the fonts from https://github.com/Omnibus-Type/Grenze/tree/master/fonts-/gx, I get the following error message: lua error: run callback [6]: ...ext/tex/texmf-context/tex/context/base/mkxl/lpdf-emb.lmt:84: number (local 'n') has no integer representation stack traceback: ...base/mkxl/lpdf-emb.lmt:84: in upvalue 'tocardinal2' ...base/mkxl/lpdf-emb.lmt:771: in local 'writer' ...base/mkxl/lpdf-emb.lmt:2358: in field 'integer index' ...base/mkxl/lpdf-ini.lmt:828: in upvalue 'run' ...base/mkxl/lpdf-ini.lmt:859: in field 'finalizedocument' ...base/mkxl/lpdf-lmt.lmt:3413: in field '?' ...base/mkxl/luat-run.lmt:58: in function <...ext/tex/texmf-context/tex/context/base/mkxl/luat-run.lmt:56> mtx-context | fatal error: return code: 1 This crashes LuaMetaTeX but not LuaTeX. i'll catch it 2. The other font is Recursive (https://github.com/arrowtype/recursive/tree/main/fonts/recursive_for_googlefonts). \usemodule[fonts-variable] \starttext \showfontvariations[font=file:recursive.ttf] \stoptext There are some some instances (in pages 4 to 14) that don’t have the font (only Latin Modern Roman). i'll catch it Also in the last instances (at least, pages 19 to 25), kerning or interletter spacing clearly needs to be improved. no clue (ok, a little) 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] two issues with variable fonts
Hi Hans, I have two issues with variable fonts (using current latest from yesterday): 1. Using the following sample: \usemodule[fonts-variable] \starttext \showfontvariations[font=file:grenze.ttf] \stoptext With the fonts from https://github.com/Omnibus-Type/Grenze/tree/master/fonts-/gx, I get the following error message: lua error: run callback [6]: ...ext/tex/texmf-context/tex/context/base/mkxl/lpdf-emb.lmt:84: number (local 'n') has no integer representation stack traceback: ...base/mkxl/lpdf-emb.lmt:84: in upvalue 'tocardinal2' ...base/mkxl/lpdf-emb.lmt:771: in local 'writer' ...base/mkxl/lpdf-emb.lmt:2358: in field 'integer index' ...base/mkxl/lpdf-ini.lmt:828: in upvalue 'run' ...base/mkxl/lpdf-ini.lmt:859: in field 'finalizedocument' ...base/mkxl/lpdf-lmt.lmt:3413: in field '?' ...base/mkxl/luat-run.lmt:58: in function <...ext/tex/texmf-context/tex/context/base/mkxl/luat-run.lmt:56> mtx-context | fatal error: return code: 1 This crashes LuaMetaTeX but not LuaTeX. 2. The other font is Recursive (https://github.com/arrowtype/recursive/tree/main/fonts/recursive_for_googlefonts). \usemodule[fonts-variable] \starttext \showfontvariations[font=file:recursive.ttf] \stoptext There are some some instances (in pages 4 to 14) that don’t have the font (only Latin Modern Roman). Also in the last instances (at least, pages 19 to 25), kerning or interletter spacing clearly needs to be improved. Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Heisenbug in current?
On 11/23/2022 11:01 PM, Thomas A. Schmitz via ntg-context wrote: Hi all, I'm very hesitant to report this because I can't reproduce it consistently: some of my files don't compile with bizarre font errors, sometimes. At first I thought it may be a hardware problem on my laptop, but I've seen more or less the same error on 3 different computers now, intermittently. The offending call is always similar: fonts > otf loading > loading '/mnt/shared/lmtx/tex/texmf/fonts/data/public/dejavu/DejaVuSansMono.ttf', hash 'dejavusansmono' otf reader > fatal error in file '/mnt/shared/lmtx/tex/texmf/fonts/data/public/dejavu/DejaVuSansMono.ttf': ...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:1040: attempt to call a nil value (field 'to16dot16') It concerns several fonts, both my own and (as here) from the installation, and the first error is always this "field 'to16dot16.'" Has anybody else seen this? Do the developers have any idea what this could be? Has there been a change in the code concerning this field? Sorry for being so vague, but I'm pulling my hair because this error crops up totally at random, AFAICS. probably not that random ... can you put this on top of font-otr.lua local number = number and see if that helps .. if so you can then spend the rest of the evening figuring out where 'number' gets defined global 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Heisenbug in current?
Hi all, I'm very hesitant to report this because I can't reproduce it consistently: some of my files don't compile with bizarre font errors, sometimes. At first I thought it may be a hardware problem on my laptop, but I've seen more or less the same error on 3 different computers now, intermittently. The offending call is always similar: fonts > otf loading > loading '/mnt/shared/lmtx/tex/texmf/fonts/data/public/dejavu/DejaVuSansMono.ttf', hash 'dejavusansmono' otf reader > fatal error in file '/mnt/shared/lmtx/tex/texmf/fonts/data/public/dejavu/DejaVuSansMono.ttf': ...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:1040: attempt to call a nil value (field 'to16dot16') It concerns several fonts, both my own and (as here) from the installation, and the first error is always this "field 'to16dot16.'" Has anybody else seen this? Do the developers have any idea what this could be? Has there been a change in the code concerning this field? Sorry for being so vague, but I'm pulling my hair because this error crops up totally at random, AFAICS. All best Thomas ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] how to simulate \hss in luametatex?
Hans,
thank you.
By your and Max's answers, I understand that
there must be box.glueset for the glues in the box.list to actually work.
Best regards
Huang Fusyong(黄复雄)
Hans Hagen via ntg-context 于2022年11月11日周五 18:52写道：
>
> On 11/11/2022 10:53 AM, Max Chernoff via ntg-context wrote:
> > Hi,
> >
> >> I want to simulate \hss in lua end in ConTeXt/luametatex environment.
> >> For example,
> >>
> >> ```ConTeXt
> >> a{\raise 1.5ex\hbox to 0pt{\hss b}}c
> >> ```
> >
> >> And in lua, I do as follows(part of my app seen in attachment):
> >
> > Your code doesn't compile as is. I think that this is the same thing
> > though:
> >
> > \starttext
> > \startluacode
> > local a = node.new"glyph"
> > a.char = string.byte("a")
> > a.font = font.current()
> >
> > local b = node.new"glyph"
> > b.char = string.byte("b")
> > b.font = font.current()
> >
> > local c = node.new"glyph"
> > c.char = string.byte("c")
> > c.font = font.current()
> >
> > local hss = node.new("glue")
> > hss.stretch = 65536
> > hss.stretchorder = 2
> > hss.shrink = 65536
> > hss.shrinkorder = 2
> > hss.width = 0
> > b = node.insertbefore(b, b, hss)
> >
> > local box = node.new("hlist", "box")
> > box.head = b
> > box.width = 0
> > box.shift = -tex.sp("1ex")
> >
> > tex.forcehmode()
> > node.write(a + box + c)
> > \stopluacode
> > \stoptext
> >
> >> And got 'b' on top of 'c' in pdf as follows:
> >>
> >> ```pdf
> >>b
> >> ac
> >> ```
> >
> > The \hss isn't the problem here. The problem is actually with the box.
> > When you manually make the \hbox like that, I think (although I could be
> > wrong) that you're bypassing all of TeX's glue calculations. You should
> > probably use "node.hpack" instead:
> >
> > \starttext
> > \startluacode
> > local a = node.new"glyph"
> > a.char = string.byte("a")
> > a.font = font.current()
> >
> > local b = node.new"glyph"
> > b.char = string.byte("b")
> > b.font = font.current()
> >
> > local c = node.new"glyph"
> > c.char = string.byte("c")
> > c.font = font.current()
> >
> > local hss = node.new("glue")
> > hss.stretch = 65536
> > hss.stretchorder = 2
> > hss.shrink = 65536
> > hss.shrinkorder = 2
> > hss.width = 0
> >
> > local box = node.hpack(hss + b, "exactly", 0)
> > box.shift = -tex.sp("1ex")
> >
> > tex.forcehmode()
> > a.next = box
> > box.next = c
> > node.write(a)
> > \stopluacode
> > \stoptext
> indeed, an dafter that you can check it
>
> box.glueorder : 2
> box.glueset: 6.6683349609375
> box.gluesign : 2
>
> which will be applied (in the backend) to glues
>
> 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 /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] how to simulate \hss in luametatex?
Dear Max,
I am very grateful that you took the time to tweak and test my
non-running code snippet
and found the problem.
> local box = node.hpack(hss + b, "exactly", 0)
You are absolutely right, the cause of the problem was that I wasn't
using node.hpack().
Actually, I tried to use it, but used it wrong, as follows:
local box, _ = node_hpack(list)
box.width = 0
box.shift = -tex_sp("1ex")
My app works fine now. Also, I learned a lot from your code, like
font.current(), hss + b
and tex.forcehmode() - I immediately used the last one to set
box.shift, making it relative.
Best regards
Huang Fusyong(黄复雄)
Max Chernoff via ntg-context 于2022年11月11日周五 17:55写道：
>
> Hi,
>
> > I want to simulate \hss in lua end in ConTeXt/luametatex environment.
> > For example,
> >
> > ```ConTeXt
> > a{\raise 1.5ex\hbox to 0pt{\hss b}}c
> > ```
>
> > And in lua, I do as follows(part of my app seen in attachment):
>
> Your code doesn't compile as is. I think that this is the same thing
> though:
>
>\starttext
>\startluacode
>local a = node.new"glyph"
>a.char = string.byte("a")
>a.font = font.current()
>
>local b = node.new"glyph"
>b.char = string.byte("b")
>b.font = font.current()
>
>local c = node.new"glyph"
>c.char = string.byte("c")
>c.font = font.current()
>
>local hss = node.new("glue")
>hss.stretch = 65536
>hss.stretchorder = 2
>hss.shrink = 65536
>hss.shrinkorder = 2
>hss.width = 0
>b = node.insertbefore(b, b, hss)
>
>local box = node.new("hlist", "box")
>box.head = b
>box.width = 0
>box.shift = -tex.sp("1ex")
>
>tex.forcehmode()
>node.write(a + box + c)
>\stopluacode
>\stoptext
>
> > And got 'b' on top of 'c' in pdf as follows:
> >
> > ```pdf
> > b
> > ac
> > ```
>
> The \hss isn't the problem here. The problem is actually with the box.
> When you manually make the \hbox like that, I think (although I could be
> wrong) that you're bypassing all of TeX's glue calculations. You should
> probably use "node.hpack" instead:
>
>\starttext
>\startluacode
>local a = node.new"glyph"
>a.char = string.byte("a")
>a.font = font.current()
>
>local b = node.new"glyph"
>b.char = string.byte("b")
>b.font = font.current()
>
>local c = node.new"glyph"
>c.char = string.byte("c")
>c.font = font.current()
>
>local hss = node.new("glue")
>hss.stretch = 65536
>hss.stretchorder = 2
>hss.shrink = 65536
>hss.shrinkorder = 2
>hss.width = 0
>
>local box = node.hpack(hss + b, "exactly", 0)
>box.shift = -tex.sp("1ex")
>
>tex.forcehmode()
>a.next = box
>box.next = c
>node.write(a)
>\stopluacode
>\stoptext
>
> -- Max
>
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] how to simulate \hss in luametatex?
On 11/11/2022 10:53 AM, Max Chernoff via ntg-context wrote:
Hi,
I want to simulate \hss in lua end in ConTeXt/luametatex environment.
For example,
```ConTeXt
a{\raise 1.5ex\hbox to 0pt{\hss b}}c
```
And in lua, I do as follows(part of my app seen in attachment):
Your code doesn't compile as is. I think that this is the same thing
though:
\starttext
\startluacode
local a = node.new"glyph"
a.char = string.byte("a")
a.font = font.current()
local b = node.new"glyph"
b.char = string.byte("b")
b.font = font.current()
local c = node.new"glyph"
c.char = string.byte("c")
c.font = font.current()
local hss = node.new("glue")
hss.stretch = 65536
hss.stretchorder = 2
hss.shrink = 65536
hss.shrinkorder = 2
hss.width = 0
b = node.insertbefore(b, b, hss)
local box = node.new("hlist", "box")
box.head = b
box.width = 0
box.shift = -tex.sp("1ex")
tex.forcehmode()
node.write(a + box + c)
\stopluacode
\stoptext
And got 'b' on top of 'c' in pdf as follows:
```pdf
b
ac
```
The \hss isn't the problem here. The problem is actually with the box.
When you manually make the \hbox like that, I think (although I could be
wrong) that you're bypassing all of TeX's glue calculations. You should
probably use "node.hpack" instead:
\starttext
\startluacode
local a = node.new"glyph"
a.char = string.byte("a")
a.font = font.current()
local b = node.new"glyph"
b.char = string.byte("b")
b.font = font.current()
local c = node.new"glyph"
c.char = string.byte("c")
c.font = font.current()
local hss = node.new("glue")
hss.stretch = 65536
hss.stretchorder = 2
hss.shrink = 65536
hss.shrinkorder = 2
hss.width = 0
local box = node.hpack(hss + b, "exactly", 0)
box.shift = -tex.sp("1ex")
tex.forcehmode()
a.next = box
box.next = c
node.write(a)
\stopluacode
\stoptext
indeed, an dafter that you can check it
box.glueorder : 2
box.glueset: 6.6683349609375
box.gluesign : 2
which will be applied (in the backend) to glues
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] how to simulate \hss in luametatex?
Hi,
> I want to simulate \hss in lua end in ConTeXt/luametatex environment.
> For example,
>
> ```ConTeXt
> a{\raise 1.5ex\hbox to 0pt{\hss b}}c
> ```
> And in lua, I do as follows(part of my app seen in attachment):
Your code doesn't compile as is. I think that this is the same thing
though:
\starttext
\startluacode
local a = node.new"glyph"
a.char = string.byte("a")
a.font = font.current()
local b = node.new"glyph"
b.char = string.byte("b")
b.font = font.current()
local c = node.new"glyph"
c.char = string.byte("c")
c.font = font.current()
local hss = node.new("glue")
hss.stretch = 65536
hss.stretchorder = 2
hss.shrink = 65536
hss.shrinkorder = 2
hss.width = 0
b = node.insertbefore(b, b, hss)
local box = node.new("hlist", "box")
box.head = b
box.width = 0
box.shift = -tex.sp("1ex")
tex.forcehmode()
node.write(a + box + c)
\stopluacode
\stoptext
> And got 'b' on top of 'c' in pdf as follows:
>
> ```pdf
> b
> ac
> ```
The \hss isn't the problem here. The problem is actually with the box.
When you manually make the \hbox like that, I think (although I could be
wrong) that you're bypassing all of TeX's glue calculations. You should
probably use "node.hpack" instead:
\starttext
\startluacode
local a = node.new"glyph"
a.char = string.byte("a")
a.font = font.current()
local b = node.new"glyph"
b.char = string.byte("b")
b.font = font.current()
local c = node.new"glyph"
c.char = string.byte("c")
c.font = font.current()
local hss = node.new("glue")
hss.stretch = 65536
hss.stretchorder = 2
hss.shrink = 65536
hss.shrinkorder = 2
hss.width = 0
local box = node.hpack(hss + b, "exactly", 0)
box.shift = -tex.sp("1ex")
tex.forcehmode()
a.next = box
box.next = c
node.write(a)
\stopluacode
\stoptext
-- Max
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] how to simulate \hss in luametatex?
Hi list,
I want to simulate \hss in lua end in ConTeXt/luametatex environment.
For example,
```ConTeXt
a{\raise 1.5ex\hbox to 0pt{\hss b}}c
```
should get 'b' on top of 'a', as follows:
```pdf
b
ac
```
and in lua, I see a before "b" node, width
width:0, stretch:65536, shrink:65536, stretchorder:2, shrinkorder:2
And in lua, I do as follows(part of my app seen in attachment):
```lua
local hss = node_new(glue_id)
hss.stretch = 65536
hss.stretchorder = 2
hss.shrink = 65536
hss.shrinkorder = 2
hss.width = 0
list,_ = node_insertbefore(list, list, hss) -- b is in the list
-- I got a with
width:0, stretch:65536, shrink:65536, stretchorder:2, shrinkorder:2
local box = node_new(hlist_id, "box")
box.head = list
box.width = 0
box.shift = -tex_sp("1ex")
-- I got width:0 height:0 deep:0
shift: -503424
head, current = node_insertbefore(head,current, box) -- current is 'c' node
```
And got 'b' on top of 'c' in pdf as follows:
```pdf
b
ac
```
How can I get 'b' on top of 'a' as \hss do?
___
If your question is of interest to others as well, please add an entry
to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
t-zhpunc.lua
Description: Binary data
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] node.setglue broken in LuaMetaTeX
On 11/7/2022 11:40 AM, Max Chernoff via ntg-context wrote: Hi Hans, Using node.setglue in LuaMetaTeX sets all of the glue components to zero. This example: \startluacode local stretch_order = "stretch_order" local shrink_order = "shrink_order" if status.luatex_engine == "luametatex" then stretch_order = "stretchorder" shrink_order ="shrinkorder" end local glue = node.new "glue" print(node.getglue(glue)) node.setglue(glue, 1, 2, 3, 4, 5) print(node.getglue(glue)) glue.width = 1 glue.stretch = 2 glue.shrink = 3 glue[stretch_order] = 4 glue[shrink_order] = 5 print(node.getglue(glue)) node.setglue(glue, 1, 2, 3, 4, 5) print(node.getglue(glue)) \stopluacode produces this output in MkIV: 0 0 0 0 0 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 but this output in MkXL: 0 0 0 0 0 0 0 0 0 0 1 2 3 4 5 0 0 0 0 0 it is unrelated to luametatex in the sense that it doesn't have that setter, so we emulate it in node-cmp.lmt: function node.setglue (n,...) return setglue (todirect(n),...) end but even then you won't get the '5' as bad values are intercepted ... i'll also add some extra checks to those field setters 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] node.setglue broken in LuaMetaTeX
Hi Hans, Using node.setglue in LuaMetaTeX sets all of the glue components to zero. This example: \startluacode local stretch_order = "stretch_order" local shrink_order = "shrink_order" if status.luatex_engine == "luametatex" then stretch_order = "stretchorder" shrink_order ="shrinkorder" end local glue = node.new "glue" print(node.getglue(glue)) node.setglue(glue, 1, 2, 3, 4, 5) print(node.getglue(glue)) glue.width = 1 glue.stretch = 2 glue.shrink = 3 glue[stretch_order] = 4 glue[shrink_order] = 5 print(node.getglue(glue)) node.setglue(glue, 1, 2, 3, 4, 5) print(node.getglue(glue)) \stopluacode produces this output in MkIV: 0 0 0 0 0 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 but this output in MkXL: 0 0 0 0 0 0 0 0 0 0 1 2 3 4 5 0 0 0 0 0 Thanks, -- Max ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] "true" units in LuaMetaTeX
On 10/27/2022 10:22 AM, Max Chernoff via ntg-context wrote: Hi Hans, Anyway, I'll check it. Is anyone still using this "true" actually? I've been playing around with LuaMetaLaTeX/LuaMetaPlain recently https://github.com/zauguin/luametalatex and plain.tex uses truein for typesetting the footnote rule. It's trivial to fix that specific case, but I'm finding 140 other files in TeX Live that use the "true" dimensions, 69 of which that have been updated in the past 3 years. I doubt that anyone in ConTeXt uses the "true" dimensions though. well, we can keep it as depricated feature (as there is no measurable overhead when it's not used) .. although i might come up with some plain mode in lmtx (when i'm really bored as it makes little sense) i'm not going to worry much about / cq. follow old-school usage and compatibility wrt dvi driver related features (i'm not even sure if luametatex makes sense for other macro packages but we'll see, these things happens outside my scope anyway) 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] "true" units in LuaMetaTeX
Hi Hans, > Anyway, I'll check it. Is anyone still using this "true" actually? I've been playing around with LuaMetaLaTeX/LuaMetaPlain recently https://github.com/zauguin/luametalatex and plain.tex uses truein for typesetting the footnote rule. It's trivial to fix that specific case, but I'm finding 140 other files in TeX Live that use the "true" dimensions, 69 of which that have been updated in the past 3 years. I doubt that anyone in ConTeXt uses the "true" dimensions though. > I don't check github, it's mostly there for the compile farm and > intermediate testing (e.g. math stuff) so sending me a mail is ok. When > there is some serious issue a mwe to the list is good enough. K, will do. Thanks, -- Max ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] "true" units in LuaMetaTeX
On 10/27/2022 8:11 AM, Max Chernoff via ntg-context wrote: Hi Hans, The unit scanner in LuaMetaTeX fails for any of the "true" dimensions. With this test file: \starttext \vrule width 1truein height 1pt depth 0pt\relax \vrule width 1in height 1pt depth 0pt\relax \stoptext I get this output: tex error > tex error on line 2 in file ./lmtx-true.tex: Valid keyword expected, likely 'true' \vrule width 1truei n height 1pt depth 0pt\relax 1 \starttext 2 >> \vrule width 1truein height 1pt depth 0pt\relax 3 4 \vrule width 1in height 1pt depth 0pt\relax 5 \stoptext 6 I was able to fix this with the patch at the end of the email. (Also, how do you want patches sent? Via email to the mailing list, emailed directly to you, as a pull request on GitHub, or something else?) In a way 'true' has been dropped becauswe it doesn't do anything and I will likely remove that check completely (as \mag is also gone, although the performance hit for scanning true is neglectable in luametatex). Anyway, I'll check it. Is anyone still using this "true" actually? I don't check github, it's mostly there for the compile farm and intermediate testing (e.g. math stuff) so sending me a mail is ok. When there is some serious issue a mwe to the list is good enough. 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] "true" units in LuaMetaTeX
Hi Hans,
The unit scanner in LuaMetaTeX fails for any of the "true" dimensions.
With this test file:
\starttext
\vrule width 1truein height 1pt depth 0pt\relax
\vrule width 1in height 1pt depth 0pt\relax
\stoptext
I get this output:
tex error > tex error on line 2 in file ./lmtx-true.tex: Valid keyword
expected, likely 'true'
\vrule width 1truei
n height 1pt depth 0pt\relax
1 \starttext
2 >> \vrule width 1truein height 1pt depth 0pt\relax
3
4 \vrule width 1in height 1pt depth 0pt\relax
5 \stoptext
6
I was able to fix this with the patch at the end of the email.
(Also, how do you want patches sent? Via email to the mailing list,
emailed directly to you, as a pull request on GitHub, or something
else?)
Thanks,
-- Max
-- >8 --
From 69f186daa9b3bf53697e6edf1bd9b066d64b35fe Mon Sep 17 00:00:00 2001
From: Max Chernoff <49086429+gucci-on-fl...@users.noreply.github.com>
Date: Wed, 26 Oct 2022 23:45:19 -0600
Subject: [PATCH] Fix scanning of "true" units
---
source/tex/texscanning.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/tex/texscanning.c b/source/tex/texscanning.c
index 7f78d80..98a9c41 100644
--- a/source/tex/texscanning.c
+++ b/source/tex/texscanning.c
@@ -2304,6 +2304,7 @@ typedef enum scanned_unit {
static int tex_aux_scan_unit(halfword *num, halfword *denom, halfword *value,
halfword *order)
{
+ AGAIN:
do {
tex_get_x_token();
} while (cur_cmd == spacer_cmd);
@@ -2327,7 +2328,6 @@ static int tex_aux_scan_unit(halfword *num, halfword
*denom, halfword *value, ha
goto BACK_TWO;
}
cur_cs = save_cur_cs;
- AGAIN:
switch (chrone) {
case 'p': case 'P':
switch (chrtwo) {
--
2.37.3
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] debugging lmtx and firefox (was: TeXGyre Heros on Firefox)
Dear Pablo, Am Sun, Oct 16, 2022 at 08:43:25PM +0200 schrieb Pablo Rodriguez via ntg-context: > On 7/25/22 14:00, juh+ntg-context--- via ntg-context wrote: > > [...] > > They hint to LuaMetaTex as the cause of the problem. You can follow the > > discussion here. > > > > https://bugzilla.mozilla.org/show_bug.cgi?id=1781022 > > Hi juh, > > this should have been fixed in current latest. So I think it may be safe > to close the issue. > > Sorry, but I cannot access to my Mozilla account temporarily (and I > think you may close your issue without having to ask administrators). Thanks for the hint. I will test the new upload and close the bug. A first look into pdfjs/firefox on my notebook is looking good. Many thanks to our developers to fix this so quickly. juh -- Autoren-Homepage: . http://literatur.hasecke.com Satiren & Essays: . http://www.sudelbuch.de Privater Blog: http://www.hasecke.eu Netzliteratur-Projekt: http://www.generationenprojekt.de signature.asc Description: PGP signature ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] new upload
On 10/17/2022 8:43 AM, Otared Kavian via ntg-context wrote:
I use Lucida in my documents and did not notice any problem with the integrals
and other large operators.
Do you mean in the future I have to update to a new version of Lucida (and pay
again…) or will future versions of LuaMetaTeX handle correctly large operators
typeset in Lucida ?
I think there is some free upgrade policy. In general the old font
should work ok given that one can live with the (current) inaccuracies
(ance it's done there will be an article about the improvemnets that
clarifies things).
We already concluded long ago that the suite of math fonts is somewhat
inconsistent (between and within fonts). We try to deal with that as
good as possible and believe that we have found the right mixed
approach. If needed we can catch averythign in the goodie files but we
try to minimize it so once this is all settled down, we can improve
specific font related issues based on {\em realistic} user mwe's as we go.
Concerning large operators .. it worked before so ... the main reason
why in e.g. euler it failed was a configuration option (euler fonts will
be fixed too) which is a side effect of more advanced script anchoring
in lmtx.
The issue I observed with the new upload of 2022.10.15 is that the
presentations I typeset with the simpleslides module are broken after three
pages, but could not set up a minimal working example to send to the list.
Those presentations are typeset correctly with previous versions.
Has Metapost changed some crucial settings ?
some mp->tex interfacing macros were upgraded but that should not really
matter much so i need an example of what goes wrong (quite some month
ago we fixed some left/right page related interfacing but that should
not affect single sided documents)
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] new upload
On Mon, Oct 17, 2022 at 8:43 AM Otared Kavian via ntg-context wrote: > > Hi Mikael, Hi Otared, > > I use Lucida in my documents and did not notice any problem with the > integrals and other large operators. > Do you mean in the future I have to update to a new version of Lucida (and > pay again…) or will future versions of LuaMetaTeX handle correctly large > operators typeset in Lucida ? In Lucida the integrals have almost been at the right place. See the attached screenshot. To the left, the unfixed Lucida (first aligned at the base line, and then centered around the math axis). To the right, the same with fixed Lucida. In the eulernova example that Aditya shows, the difference is much bigger. The fixoldschool tweak fixes it, but it is of course better if it gets fixed in the font. Regarding the Lucida fonts: When you bought them you should have got some login information. That should still work, and you should be able to upgrade your fonts when released. I don't know how they (TUG) do releases, though, if they send out information to all people who bought the font. Hans and I are only involved in the fixing. /Mikael PS There are some other glyphs in Lucida that will be fixed. The <, >, \oiint and \oiiint (displayed versions of the integrals). If you add them (and, say also a = close to the < and >) to a document, and use \showglyphs you will see why. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] new upload
Hi Mikael,
I use Lucida in my documents and did not notice any problem with the integrals
and other large operators.
Do you mean in the future I have to update to a new version of Lucida (and pay
again…) or will future versions of LuaMetaTeX handle correctly large operators
typeset in Lucida ?
The issue I observed with the new upload of 2022.10.15 is that the
presentations I typeset with the simpleslides module are broken after three
pages, but could not set up a minimal working example to send to the list.
Those presentations are typeset correctly with previous versions.
Has Metapost changed some crucial settings ?
Best regards: Otared
> On 16 Oct 2022, at 19:03, Mikael Sundqvist via ntg-context
> wrote:
>
> Hi,
>
> On Sun, Oct 16, 2022 at 6:07 PM Aditya Mahajan via ntg-context
> wrote:
>>
>> On Fri, 14 Oct 2022, Hans Hagen via ntg-context wrote:
>>
>>> Hi,
>>>
>>> I uploaded a new version. Apart from a few fixes / extensions already
>>> mentioned here (or known to those who wanted it) the main changes are in
>>> the math goodie files (work in progress, we will clean them up later) as
>>> part of improving the rendering of math.
>>
>> Something is wrong with the placement of limits around an integral with
>> NeoEuler:
>>
>> \usetypescriptfile[euler]
>>
>> \definetypeface[mainfont][rm][specserif][CharisSil][default]
>> \definetypeface[mainfont][mm][math] [eulernova][default]
>> \definetypeface[mainfont][tt][mono] [dejavu][default] [rscale=0.8,
>> features=none]
>> \setupbodyfont[mainfont,10pt]
>>
>> \starttext
>> \startTEXpage[offset=1mm]
>> $\displaystyle \int_{0}^{1} f(x) dx$
>> \stopTEXpage
>> \stoptext
>>
>> gives the attached result.
>
> This is because the integral "sits wrong" in its boundingbox. Almost
> all fonts have the glyph centered around the math axis, but there are
> a few that doesn't. In euler-math.lfg, add the tweak
>
> {
> tweak = "fixoldschool",
> },
>
> In fact, we have not updated the euler goodie file for a while it
> seems. I think there are more things that can be improved. Hopefully
> before next release.
>
> It can also be mentioned that some fonts (Daniel Flipo was quick to
> fix concrete, erewhon and kpfonts) was fixed recently regarding this,
> and it is reported on and fixed in development of Lucida.
>
> /Mikael
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___
Otared Kavian
e-mail: ota...@gmail.com
Phone: +33 6 88 26 70 95
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] debugging lmtx and firefox (was: TeXGyre Heros on Firefox)
On 7/25/22 14:00, juh+ntg-context--- via ntg-context wrote: > [...] > They hint to LuaMetaTex as the cause of the problem. You can follow the > discussion here. > > https://bugzilla.mozilla.org/show_bug.cgi?id=1781022 Hi juh, this should have been fixed in current latest. So I think it may be safe to close the issue. Sorry, but I cannot access to my Mozilla account temporarily (and I think you may close your issue without having to ask administrators). Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] synctex problem
Hi Alan, I have an almost identical set-up (M1, MacOS12.6, TexShop, useAlternatePath, useConTeXtSyncParser). One important difference, I use sync method: SyncTeX (TeX ≥ 2010) I’d recommend trying that. There are some other differences in my setup that probably are not important. At the beginning of my files (products and components)I only use the two lines % !TEX useAlternatePath % !TEX useConTeXtSyncParser not the root and TS-program lines, but I don’t think that matters for your SynchTeX issue. Here is the engine I use for LMTX, just in case it has something helpful for you. #!/bin/zsh # # This engine uses TeXShop's "Alternate Path", which is the variable "$3" below. # Set the TeXShop's alternate path to your ConTeXt installation in # TeXShop's Preferences -> Engine -> Alternate Path # Start ConTeXt source files with the lines: # % !TEX useAlternatePath # % !TEX useConTeXtSyncParser export OSFONTDIR=/Library/Fonts/:/System/Library/Fonts:$HOME/Library/Fonts export PATH="$3":$PATH mtxrun --autogenerate --script context --synctex "$1” I put that long comment in the engine because I share it with collaborators. Hope that helps! Gavin > On Oct 15, 2022, at 12:00 PM, Alan Bowen via ntg-context > wrote: > > At the top of a single source file, I have the lines: > % !TEX root = prd_Aestimatio-0301.tex % the root file > % !TEX TS-program = ConTeXt2021 > % !TEX useAlternatePath > % !TEX useConTeXtSyncParser >\setupsynctex[state=start, method=max] > > Syncing works well enough—though I can see no difference between method =min > and method=max, both highlight only a few words and not the entire text to be > synced, but perhaps my expectations are out of line. > > When I have these lines at the top of a component file and typeset the > product file, I get a rootfile.synctex file, but syncing itself goes awry. > Nothing happens when I sync from the PDf file to the component file, and when > I sync from the component file to the product PDF, I get the correct page but > no highlighting. > > I am using TeXShop ver. 5.03— > sync method: Both Pdf Sync and Search > Alternative Path: > /Users/bowen1/Applications/LuaMetaTeX/tex/texmf-osx-arm64/bin > > and also the latest ConteXt (ver. 2022.10.15 10:37 LMTX) under macOS 12.6 > (Apple M1 Pro chip) > > Note: the product file has only one component file for now. > > I suspect that I am missing something but am not sure where to look or what > to do now. Any guidance will be much appreciated. > > Alan > > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > ___ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] synctex problem
At the top of a single source file, I have the lines: % !TEX root = prd_Aestimatio-0301.tex % the root file % !TEX TS-program = ConTeXt2021 % !TEX useAlternatePath % !TEX useConTeXtSyncParser \setupsynctex[state=start, method=max] Syncing works well enough—though I can see no difference between method =min and method=max, both highlight only a few words and not the entire text to be synced, but perhaps my expectations are out of line. When I have these lines at the top of a component file and typeset the product file, I get a rootfile.synctex file, but syncing itself goes awry. Nothing happens when I sync from the PDf file to the component file, and when I sync from the component file to the product PDF, I get the correct page but no highlighting. I am using TeXShop ver. 5.03— sync method: Both Pdf Sync and Search Alternative Path: /Users/bowen1/Applications/LuaMetaTeX/tex/texmf-osx-arm64/bin and also the latest ConteXt (ver. 2022.10.15 10:37 LMTX) under macOS 12.6 (Apple M1 Pro chip) Note: the product file has only one component file for now. I suspect that I am missing something but am not sure where to look or what to do now. Any guidance will be much appreciated. Alan ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] new upload
On 10/15/2022 10:48 AM, Pablo Rodriguez via ntg-context wrote: On 10/15/22 09:41, Hans Hagen via ntg-context wrote: On 10/14/2022 4:14 PM, Pablo Rodriguez via ntg-context wrote: [...] Many thanks for the new version, Hans. I have discovered that it includes in tex/texmf-context/source/luametatex what should be the LMTX source (about 11MB). It zips to 2 MB and totals to less of a picture on a fancy phone ... Many thanks for your reply, Hans. At least on my system, I think every file is downloaded uncompressed. With a low speed connection (here, the service isn’t great all the time), having to download over 400 files is a killer. as has been pointed out, you only download the changed files and those are not many when sources are not included some complain, when they are others com-plain ... The storage space on disk is irrelevant, I totally agree with you. I wish I could say that large updates such as these weren’t a problem in some cases. But sometimes this isn’t true here. With incremental updates, the downloading process takes way shorter in subsequent updates (as Alan pointed out). But the first time it might take too much (so the script quits). just run twice as the script will pick up the idea is to provide the user with all he needs as archive so no dependencies (apart from a compiler). Also by including the source we can sort of guaranteed that you get what you expect to work with the tex files (no interference with distribution patches our of our control). It has always been part of the plan with luametatex. So ... it will not be optional. I asked to make this optional not to avoid having the source, but to be able to complete the update process. i guess a few extra fonts are more demanding, actually the number of fonts in the installation dropped (for now) so that compensates the larger source tree I’m not extremely confident, but I hope I will manage to update ConTeXt at the office (next working day). 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] new upload
On 10/15/22 09:41, Hans Hagen via ntg-context wrote: > On 10/14/2022 4:14 PM, Pablo Rodriguez via ntg-context wrote: >> [...] >> Many thanks for the new version, Hans. >> >> I have discovered that it includes in >> tex/texmf-context/source/luametatex what should be the LMTX source >> (about 11MB). > > It zips to 2 MB and totals to less of a picture on a fancy phone ... Many thanks for your reply, Hans. At least on my system, I think every file is downloaded uncompressed. With a low speed connection (here, the service isn’t great all the time), having to download over 400 files is a killer. The storage space on disk is irrelevant, I totally agree with you. I wish I could say that large updates such as these weren’t a problem in some cases. But sometimes this isn’t true here. With incremental updates, the downloading process takes way shorter in subsequent updates (as Alan pointed out). But the first time it might take too much (so the script quits). > the idea is to provide the user with all he needs as archive so no > dependencies (apart from a compiler). Also by including the source we > can sort of guaranteed that you get what you expect to work with the tex > files (no interference with distribution patches our of our control). It > has always been part of the plan with luametatex. So ... it will not be > optional. I asked to make this optional not to avoid having the source, but to be able to complete the update process. I’m not extremely confident, but I hope I will manage to update ConTeXt at the office (next working day). Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] ToC filler dots not aligned
On 10/14/2022 9:50 PM, Pablo Rodriguez via ntg-context wrote: On 10/14/22 17:29, Schister, Roman via ntg-context wrote: Hi, If I typeset a table of contents with the latest version of ConTeXt on my computer (2022.09.11 20:44 LMTX), the filler dots used in list alternative C aren’t aligned [...] Hi Roman, I compiled your code with version from 2022.09.11 20:44. I attach an overlay of the results from both LuaMeTaTeX (in red) and LuaTeX (in darkgreen). It seems that MkIV is doing fine, but LMTX isn’t aligning the dots (for some reason unknown to me). Latest from 2022.10.14 10:16 gives exactly the same result for LMTX, and MkIV doesn’t work for me. fixed in next upload - 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://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] new upload
On 10/14/2022 4:14 PM, Pablo Rodriguez via ntg-context wrote: On 10/14/22 10:21, Hans Hagen via ntg-context wrote: Hi, I uploaded a new version. Apart from a few fixes / extensions already mentioned here (or known to those who wanted it) the main changes are in the math goodie files (work in progress, we will clean them up later) as part of improving the rendering of math. Many thanks for the new version, Hans. I have discovered that it includes in tex/texmf-context/source/luametatex what should be the LMTX source (about 11MB). It zips to 2 MB and totals to less of a picture on a fancy phone .. tre idea is to provide the user with all he needs as archive so no dependenccies (apart from a compiler). Also by including the source we can sort of guaranteed that you get what you expect to work with the tex files (no interference with distribution patches our of our control). It has always been part of the plan with luametatex. So .. it wil not be optional. 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] issues with current latest
On 10/15/2022 12:33 AM, Max Chernoff via ntg-context wrote: Hi Alan, On Fri, 2022-10-14 at 16:20 -0600, Alan Braslau wrote: On Fri, 14 Oct 2022 15:38:52 -0600 Max Chernoff via ntg-context wrote: $ context --luatex test.tex mtx-context | redirect luametatex -> luatex: luatex --luaonly "/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context --luatex test.tex --redirected mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' This happens when the luatex cache is cleared and the context format is not rebuilt properly. Do you know how to rebuild the format? I've tried the following to no avail: normally context will remake automatically (you can try to touch the context.mk* file) 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] issues with current latest
On 10/15/2022 12:46 AM, Max Chernoff via ntg-context wrote:
On Fri, 2022-10-14 at 16:38 -0600, Alan Braslau wrote:
On Fri, 14 Oct 2022 16:33:12 -0600
Max Chernoff wrote:
Do you know how to rebuild the format? I've tried the following to no
avail:
--script mtx-context
I believe that you have to give the full script path here to mtxrun
Thanks! Running:
luatex --luaonly "/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script
/opt/context/tex/texmf-context/scripts/context/lua/mtx-context.lua --luatex --make
--redirected
has fixed the format issue.
I now unfortunately have a new issue (probably for Hans or Mikael).
Running:
context --luatex empty.tex
where "empty.tex" is:
\starttext
\null
\stoptext
gives me this output:
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context --luatex
empty.tex --redirected
resolvers | formats | executing runner 'run luatex format': /opt/context/tex/texmf-linux-64/bin/luatex --jobname="empty" --fmt=/home/max/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.fmt --lua=/home/max/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui cont-yes.mkiv --c:currentrun=1 --c:engine="luatex" --c:fulljobname="./empty.tex" --c:input="./empty.tex" --c:kindofrun=1 --c:luatex --c:maxnofruns=9 --c:redirected --c:texmfbinpath="/opt/context/tex/texmf-linux-64/bin"
This is LuaTeX, Version 1.15.1 (TeX Live 2023/dev)
system commands enabled.
open source > level 1, order 1, name
'/opt/context/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv'
job > passes > version mismatch: 1.33 <> 1.32
system >
system > ConTeXt ver: 2022.10.14 10:16 MKIV fmt: 2022.10.14
int: english/english
system >
system > 'cont-new.mkiv' loaded
open source > level 2, order 2, name
'/opt/context/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
system > beware: some patches loaded from cont-new.mkiv
close source> level 2, order 2, name
'/opt/context/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
system > files > jobname 'empty', input './empty', result 'empty'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 2, order 3, name
'/home/max/Projects/lua-widow-control/nogit-testing/empty.tex'
fonts > preloading latin modern fonts (second stage)
lua error > lua error on line 1 in file /home/max/Projects/lua-widow-control/nogit-testing/empty.tex:
...tex/texmf-context/tex/context/fonts/mkiv/common-math.lfg:100: attempt to index a nil value (field 'subsets')
stack traceback:
...tex/texmf-context/tex/context/fonts/mkiv/common-math.lfg:100: in
field 'moveitalics'
.../context/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg:103: in
main chunk
[C]: in function 'dofile'
...ext/tex/texmf-context/tex/context/base/mkiv/good-ini.lua:78: in function
<...ext/tex/texmf-context/tex/context/base/mkiv/good-ini.lua:68>
(...tail calls...)
1 >> \starttext
2 \null
3 \stoptext
4
mtx-context | fatal error: return code: 256
The same file compiles just fine with LMTX.
i'll add a dummy subtable in math-act.lua:
local tweaks = { subsets = { } }
mathematics.tweaks = tweaks
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] issues with current latest
On Fri, 2022-10-14 at 16:38 -0600, Alan Braslau wrote: > On Fri, 14 Oct 2022 16:33:12 -0600 > Max Chernoff wrote: > > > Do you know how to rebuild the format? I've tried the following to no > > avail: > > > > --script mtx-context > > I believe that you have to give the full script path here to mtxrun Thanks! Running: luatex --luaonly "/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script /opt/context/tex/texmf-context/scripts/context/lua/mtx-context.lua --luatex --make --redirected has fixed the format issue. I now unfortunately have a new issue (probably for Hans or Mikael). Running: context --luatex empty.tex where "empty.tex" is: \starttext \null \stoptext gives me this output: mtx-context | redirect luametatex -> luatex: luatex --luaonly "/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context --luatex empty.tex --redirected resolvers | formats | executing runner 'run luatex format': /opt/context/tex/texmf-linux-64/bin/luatex --jobname="empty" --fmt=/home/max/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.fmt --lua=/home/max/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui cont-yes.mkiv --c:currentrun=1 --c:engine="luatex" --c:fulljobname="./empty.tex" --c:input="./empty.tex" --c:kindofrun=1 --c:luatex --c:maxnofruns=9 --c:redirected --c:texmfbinpath="/opt/context/tex/texmf-linux-64/bin" This is LuaTeX, Version 1.15.1 (TeX Live 2023/dev) system commands enabled. open source > level 1, order 1, name '/opt/context/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv' job > passes > version mismatch: 1.33 <> 1.32 system > system > ConTeXt ver: 2022.10.14 10:16 MKIV fmt: 2022.10.14 int: english/english system > system > 'cont-new.mkiv' loaded open source > level 2, order 2, name '/opt/context/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' system > beware: some patches loaded from cont-new.mkiv close source> level 2, order 2, name '/opt/context/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' system > files > jobname 'empty', input './empty', result 'empty' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 2, order 3, name '/home/max/Projects/lua-widow-control/nogit-testing/empty.tex' fonts > preloading latin modern fonts (second stage) lua error > lua error on line 1 in file /home/max/Projects/lua-widow-control/nogit-testing/empty.tex: ...tex/texmf-context/tex/context/fonts/mkiv/common-math.lfg:100: attempt to index a nil value (field 'subsets') stack traceback: ...tex/texmf-context/tex/context/fonts/mkiv/common-math.lfg:100: in field 'moveitalics' .../context/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg:103: in main chunk [C]: in function 'dofile' ...ext/tex/texmf-context/tex/context/base/mkiv/good-ini.lua:78: in function <...ext/tex/texmf-context/tex/context/base/mkiv/good-ini.lua:68> (...tail calls...) 1 >> \starttext 2 \null 3 \stoptext 4 mtx-context | fatal error: return code: 256 The same file compiles just fine with LMTX. Thanks, -- Max ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] issues with current latest
Hi Alan,
On Fri, 2022-10-14 at 16:20 -0600, Alan Braslau wrote:
> On Fri, 14 Oct 2022 15:38:52 -0600
> Max Chernoff via ntg-context wrote:
>
>
>$ context --luatex test.tex
>mtx-context | redirect luametatex -> luatex: luatex --luaonly
> "/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context
> --luatex test.tex --redirected
>mtxrun | unknown script 'mtx-context.lua' or
> 'mtx-mtx-context.lua'
>
> This happens when the luatex cache is cleared and the context format is not
> rebuilt properly.
Do you know how to rebuild the format? I've tried the following to no
avail:
$ mtxrun --generate
[snip]
$ context --make
[snip]
$ context --luatex --make
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context --luatex
--make --redirected
mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'
$ TEXINPUTS="$(dirname $(mtxrun --findfile 'cont-en.mkiv' | head -1))"
luatex -ini cont-en.mkiv
warning: /opt/context/tex/texmf/web2c/texmf.cnf:49: (kpathsea) No cnf value
on line: OSFONTDIR =.
This is LuaTeX, Version 1.15.1 (TeX Live 2023/dev) (INITEX)
system commands enabled.
(/opt/context/tex/texmf-context/tex/context/base/mkiv/cont-en.mkiv
(/opt/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
(/opt/context/tex/texmf-context/tex/context/base/mkiv/syst-ini.mkiv)
(/opt/context/tex/texmf-context/tex/context/base/mkiv/norm-ctx.mkiv)
(/opt/context/tex/texmf-context/tex/context/base/mkiv/syst-pln.mkiv)
(/opt/context/tex/texmf-context/tex/context/base/mkiv/syst-mes.mkiv)
(/opt/context/tex/texmf-context/tex/context/base/mkiv/luat-cod.mkiv[\directlua]
:1: attempt to call a nil value (field 'registercode')
stack traceback:
[\directlua]:1: in main chunk.
\registerctxluafile ...ua.registercode("#1","#2")}
l.73 \registerctxluafile{luat-cod}{}
? x
181 words of node memory still in use:
1 dir, 22 glue_spec nodes
avail lists: 2:3
No pages of output.
Transcript written on cont-en.log.
$ fmtutil --all
bash: fmtutil: command not found...
$ context --make cont-en.mkiv
[snip]
Not sure what else to try.
Thanks,
-- Max
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] issues with current latest
On Fri, 14 Oct 2022 15:38:52 -0600 Max Chernoff via ntg-context wrote: $ context --luatex test.tex mtx-context | redirect luametatex -> luatex: luatex --luaonly "/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context --luatex test.tex --redirected mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' This happens when the luatex cache is cleared and the context format is not rebuilt properly. Alan ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] issues with current latest
Hi Pablo, > I’m afraid that I cannot make latest from 2022.10.14 10:16 with LuaTeX. > > I’m on Linux64. I've got the same configuration and I'm getting the same results: $ context --luatex test.tex mtx-context | redirect luametatex -> luatex: luatex --luaonly "/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context --luatex test.tex --redirected mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' $ luatex '\relax' warning: /opt/context/tex/texmf/web2c/texmf.cnf:49: (kpathsea) No cnf value on line: OSFONTDIR =. This is LuaTeX, Version 1.15.1 (TeX Live 2023/dev) system commands enabled. kpathsea: Running mktexfmt luatex.fmt mktexfmt: No such file or directory I can't find the format file `luatex.fmt'! $ luatex -ini '\end' warning: /opt/context/tex/texmf/web2c/texmf.cnf:49: (kpathsea) No cnf value on line: OSFONTDIR =. This is LuaTeX, Version 1.15.1 (TeX Live 2023/dev) (INITEX) system commands enabled. No pages of output. Transcript written on texput.log. LuaMetaTeX works fine though. Thanks, -- Max ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] ToC filler dots not aligned
On 10/14/22 17:29, Schister, Roman via ntg-context wrote: > Hi, > > If I typeset a table of contents with the latest version of ConTeXt > on my computer (2022.09.11 20:44 LMTX), the filler dots used in list > alternative C aren’t aligned [...] Hi Roman, I compiled your code with version from 2022.09.11 20:44. I attach an overlay of the results from both LuaMeTaTeX (in red) and LuaTeX (in darkgreen). It seems that MkIV is doing fine, but LMTX isn’t aligning the dots (for some reason unknown to me). Latest from 2022.10.14 10:16 gives exactly the same result for LMTX, and MkIV doesn’t work for me. Just in case it might help, Pablo a.pdf Description: Adobe PDF document ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
