ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henri Menke <henrimenke@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lmtx
Date: Wed, 3 Apr 2019 09:30:19 +1300	[thread overview]
Message-ID: <c2947d70-91ef-b9d7-8eca-77c2785a3097@gmail.com> (raw)
In-Reply-To: <2a23939c-f534-f387-f0c3-16a4d532dcd6@xs4all.nl>



On 3/04/19 9:19 AM, Hans Hagen wrote:
> On 4/2/2019 10:11 PM, Henri Menke wrote:
>>
>>
>> On 2/04/19 10:05 PM, Hans Hagen wrote:
>>> Hi,
>>>
>>> So, for those who hesitate to check out lmtx, here is some information.
>>>
>>> - In order to achieve long term stability context will use a lean and
>>> mean variant of luatex (although for now context will keep running on
>>> luatex too; i might drop support for luajittex). Eventually the source
>>> code will be part of the context distribution so that one can always
>>> compile a binary that matches an archived context version.
>>>
>>> - This version also permits us to experiment (even very extreme) without
>>> interupting the parent program luatex, which is now used by other macro
>>> packages too and therefore needs to be frozen in functionality. Some
>>> features might trickle back into luatex eventually (unless it breaks
>>> compatibility).
>>>
>>> - As a direct effect it means that context does a bit more: creating the
>>> pdf file (already most is done anyway in mkiv), dealing with font
>>> embedding, handling image inclusion, etc. For sure there can be issues
>>> with that but it has run on my machine already for quite a while.
>>>
>>> - It is hard to be conclusive about performance but for instance the
>>> luatex manual processes a bit faster with lmtx as does the test suite. A
>>> gain in performance on very demanding documents is also observed by Alan
>>> and Thomas. Normally one can expect a similar performance. However, the
>>> memory footprint could be a bit smaller.
>>>
>>> - The current somewhat hybrid codebase of context will stepwise be
>>> adapted so that at some point we can start experimenting with some
>>> pending ideas. (Which is why i sometimes answer "later this year".)
>>
>> Where can I find the C sources for the luametatex engine?
> nowhere ... as i mentioned these will become part of the context 
> distribution around the ctx meeting (when we also have the compile 
> infrastructure ready)

Hm.  But luatex is released under GPLv2 and I reckon luametatex is based on
luatex, i.e. it is a derived work which means that you legally *have* to
publish the source.

> 
> what we offer now is an experimental test release
> 
> 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
___________________________________________________________________________________

  reply	other threads:[~2019-04-02 20:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  9:05 lmtx Hans Hagen
2019-04-02 19:03 ` lmtx Taco Hoekwater
2019-04-02 20:11 ` lmtx Henri Menke
2019-04-02 20:19   ` lmtx Hans Hagen
2019-04-02 20:30     ` Henri Menke [this message]
2019-04-02 20:47       ` lmtx Hans Hagen
2019-08-05 12:38 lmtx Hans Hagen
2019-12-12  0:37 lmtx Hans Hagen
2019-12-12  5:28 ` lmtx Otared Kavian
2019-12-12  6:04   ` lmtx Otared Kavian
2019-12-12 10:08   ` lmtx Hans Hagen
2019-12-12  6:36 ` lmtx Richard Mahoney | Indica et Buddhica
2019-12-12 16:59 ` lmtx Pablo Rodriguez
2019-12-12 20:13   ` lmtx Pablo Rodriguez
     [not found] <mailman.310.1576128525.1207.ntg-context@ntg.nl>
2019-12-12 23:48 ` lmtx Jeong Dal
2019-12-13  8:39   ` lmtx Otared Kavian
     [not found] <mailman.1.1576234801.28358.ntg-context@ntg.nl>
2019-12-13 19:29 ` lmtx Jeong Dal
2020-06-19 10:11 lmtx Hans Hagen
2020-10-30 22:29 lmtx Hans Hagen
2020-10-31  2:50 ` lmtx Jairo A. del Rio
2020-11-02 19:43   ` lmtx Hans Hagen
2021-01-18 18:20 lmtx Hans Hagen
2021-01-19 10:57 ` lmtx Floris van Manen
2021-01-19 11:10   ` lmtx Hans Hagen
2021-01-19 11:31     ` lmtx Jano Kula
2021-01-19 19:12 ` lmtx Jan U. Hasecke
2021-01-19 23:03   ` lmtx Hans Hagen
2021-02-19 12:32 lmtx Hans Hagen
2022-02-03 21:00 lmtx 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=c2947d70-91ef-b9d7-8eca-77c2785a3097@gmail.com \
    --to=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).