From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: lmtx vs mkiv
Date: Sat, 18 Apr 2020 18:07:24 +0200 [thread overview]
Message-ID: <f6d90490-645c-a2da-279e-d1cff4b65a07@gmail.com> (raw)
In-Reply-To: <8d81637e-f3a1-f668-3cff-8faecea96ac7@xs4all.nl>
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
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-04-18 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 9:07 Hans Hagen
2020-04-05 9:10 ` Axel Kielhorn
2020-04-18 16:07 ` Wolfgang Schuster [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f6d90490-645c-a2da-279e-d1cff4b65a07@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).