From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Hugh Fisher <hugo.fisher@gmail.com>
Cc: Hans Hagen <j.hagen@xs4all.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LuaMetaTEX as LaTeX to XHTML/ePub transpiler?
Date: Sat, 11 Sep 2021 14:00:12 +0200 [thread overview]
Message-ID: <38070aec-f9ee-cc36-9163-cef8769a2faa@xs4all.nl> (raw)
In-Reply-To: <CAAahdHNwBDtVzfKJfYsmRJVHMm9Z7Bj=Bie49ft=+jKPJi1b5w@mail.gmail.com>
On 9/11/2021 1:19 PM, Hugh Fisher wrote:
> On Fri, 10 Sept 2021 at 21:47, Hans Hagen <j.hagen@xs4all.nl> wrote:
>>
> [ munch ]
>
>>
>> in this area there is nothing in luametatex that luatex can't do
>
> As in my earlier reply, I'm thinking about replacing Adobe Illustrator with
> Metapost, and LuaMetaTEX seems to have better integration?
indeed the interfaces in lmtx/luametatex are better than in mkiv/luatex
and new things will only be done in lmtx
anyway, context users most likely will move to lmtx (mkiv is not really
frozen as it is also the test case for luatex, but there will be no
fundamental new things added)
>> so, if your source uses a limited set of commands you can write a parser
>> (in any language)
>
> This parser would need to understand TeX source files and conventions
> such as % for comments, recognise commands starting with \ and with
> arguments/parameters bracketed by [] and {}, and look up command names
> that might be written in Lua, then call them.
>
> Isn't that what LuaMetaTEX does? No, I haven't looked at the actual source
> code yet, but starting with something that already does most of what you
> want is always quicker than writing from scratch.
sure, any tex engine is better at parsing tex input
the main differences between luatex and luametatex (much is disucussed
in articles and manuals) is that luametatex has no backend built in and
has some better interfaces in the front end; there are extension to the
subsystems of the tex engine (fonts, language, math, inserts, marks,
alignments, conditionals, macro definition, par handling) that are not
in luatex (which is basically frozen in order to permit other macro
packages to support it); lua helpers have been cleaned up and there are
some more; luametatex has a smaller binary, is more efficient wrt memory
and has better performance (if used well) than luatex
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-09-11 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 11:13 Hugh Fisher via ntg-context
2021-09-10 11:26 ` Henning Hraban Ramm via ntg-context
2021-09-11 11:14 ` Hugh Fisher via ntg-context
2021-09-10 11:47 ` Hans Hagen via ntg-context
2021-09-11 11:19 ` Hugh Fisher via ntg-context
2021-09-11 12:00 ` Hans Hagen via ntg-context [this message]
2021-09-10 15:34 ` Denis Maier via ntg-context
2021-09-10 15:50 ` Denis Maier via ntg-context
2021-09-11 11:49 ` Hugh Fisher via ntg-context
2021-09-11 12:03 ` Hans Hagen via ntg-context
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=38070aec-f9ee-cc36-9163-cef8769a2faa@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=hugo.fisher@gmail.com \
--cc=j.hagen@xs4all.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).