From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Henri Menke <henrimenke@gmail.com>
Subject: Re: metafun 2
Date: Wed, 14 Aug 2019 13:16:00 +0200 [thread overview]
Message-ID: <a6cdfb81-4f32-7a70-a2e3-586fcc880582@xs4all.nl> (raw)
In-Reply-To: <ec867b38-615e-ead3-4102-a03fcc998e66@gmail.com>
On 8/14/2019 12:18 PM, Henri Menke wrote:
> Dear Hans,
>
> I just wanted to ask, will LMTX and MetaFun remain valid implementations
> of TeX and MetaPost or do we have to expect incompatibilities?
It depends on how you define 'valid' ... we're downward compatible ...
but LMTX will use features available in luametatex, so when that is the
case some code will only be available in LMTX (unless i decide to
backport some). Wrr the TeX part: LMTX is mostly MKIV but it might
provide extra things (or different implementations). Wrr metapost: lmtx
can do more advanced things. There is a split context code base.
I expect most users to move on to lmtx anyway at some point. Maybe at
some point the existing mkiv will be like mkii: frozen.
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:[~2019-08-14 11:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 9:54 Hans Hagen
2019-08-14 10:18 ` Henri Menke
2019-08-14 11:16 ` Hans Hagen [this message]
2019-08-14 11:31 ` Floris van Manen
2019-08-14 11:53 ` Hans Hagen
2019-08-15 6:05 ` Arthur Reutenauer
2019-08-14 14:22 ` Otared Kavian
2019-08-14 14:49 ` Hans Hagen
2019-08-14 14:53 ` Aditya Mahajan
2019-08-14 14:58 ` Otared Kavian
2019-08-14 15:11 ` Wolfgang Schuster
2019-08-14 15:34 ` Hans Hagen
2019-08-14 14:58 ` Mikael P. Sundqvist
2019-08-14 15:37 ` Hans Hagen
[not found] ` <CAHy-LL9D5NB6qZYj+QynCWR-rqk6suD3reepLUgO8KOwrjwnXA@mail.gmail.com>
2019-08-19 19:20 ` Fwd: " Mikael P. Sundqvist
2019-08-16 23:31 ` Adam Reviczky
2019-08-17 1:27 ` Alan Braslau
2019-08-17 8:52 ` Hans Hagen
2019-08-17 18:12 ` Adam Reviczky
2019-08-19 19:15 ` Jorge Manuel
2019-09-08 8:42 ` Aditya Mahajan
2019-09-08 10:09 ` Otared Kavian
2019-09-08 14:54 ` Aditya Mahajan
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=a6cdfb81-4f32-7a70-a2e3-586fcc880582@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=henrimenke@gmail.com \
--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).