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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
