Hi, One problem of mixed usage of mkiv (with luatex) and lmtx (with luametatex) is that in the later we use a different (initial) context runner. Basically all platforms are now handled the same (in mkiv there was a stub and no texlua, in unix something shebang with texlua because of argument passing limitations). However, the main context script can be told to use a specific engine: context --luatex foo.tex so in principle one can use both lmtx and mkiv with the same binary tree, given that luametatex and luatex are both present and that luametatex is in charge. For that reason the latest lmtx installer now (for the time being) also includes the luatex binary (plus mkiv files needed) so that one can install lmtx and run both engines. Instead of the --luatex switch one can also force the engine in the usual way with "% engine=luatex" at the top line of the source file (but no pdftex and xetex in this installer). FWIW, the lmtx installation ships with the latest experimental luatex binary but normally that should not have consequences, but it does permits testing occasional updates. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
Am 03.04.2020 um 11:07 schrieb Hans Hagen
: For that reason the latest lmtx installer now (for the time being) also includes the luatex binary (plus mkiv files needed) so that one can install lmtx and run both engines. Instead of the --luatex switch one can also force the engine in the usual way with "% engine=luatex" at the top line of the source file (but no pdftex and xetex in this installer).
I updated LMTX on MacOSX 10.13 today. The luatex binary in not executable, thus when I run axel$ context --luatex --version mtx-context | redirect luametatex -> luatex: luatex --luaonly "/usr/local/texlive/LMTX/tex/texmf-osx-64/bin/mtxrun.lua" --script mtx-context --luatex --version --redirected mtx-context | ConTeXt Process Management 1.02 mtx-context | mtx-context | main context file: /Volumes/Macintosh HD/usr/local/texlive/2019/texmf-dist/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2019.03.21 21:39 it picks up the TeX-Live version. after I axel$ chmod 744 luatex I get the correct version: axel$ context --luatex --version mtx-context | redirect luametatex -> luatex: luatex --luaonly "/usr/local/texlive/LMTX/tex/texmf-osx-64/bin/mtxrun.lua" --script mtx-context --luatex --version --redirected mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: /Volumes/Macintosh HD/usr/local/texlive/LMTX/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2020.04.03 10:31 mtx-context | main context file: /Volumes/Macintosh HD/usr/local/texlive/LMTX/tex/texmf-context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2020.04.03 10:31 Greetings Axel
Hans Hagen schrieb am 03.04.2020 um 11:07:
Hi,
One problem of mixed usage of mkiv (with luatex) and lmtx (with luametatex) is that in the later we use a different (initial) context runner. Basically all platforms are now handled the same (in mkiv there was a stub and no texlua, in unix something shebang with texlua because of argument passing limitations).
However, the main context script can be told to use a specific engine:
context --luatex foo.tex
so in principle one can use both lmtx and mkiv with the same binary tree, given that luametatex and luatex are both present and that luametatex is in charge.
For that reason the latest lmtx installer now (for the time being) also includes the luatex binary (plus mkiv files needed) so that one can install lmtx and run both engines. Instead of the --luatex switch one can also force the engine in the usual way with "% engine=luatex" at the top line of the source file (but no pdftex and xetex in this installer).
FWIW, the lmtx installation ships with the latest experimental luatex binary but normally that should not have consequences, but it does permits testing occasional updates.
Hans
The binary for Windows 64bit is missing (or in a different folder) on the server because I get the following message as content for luatex.exe <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /build/luatex/x86_64-w64-mingw32/luatex.exe was not found on this server.</p> </body></html> Wolfgang
participants (3)
-
Axel Kielhorn
-
Hans Hagen
-
Wolfgang Schuster