ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: luatex on the garden
Date: Fri, 31 Aug 2018 10:27:57 +0200	[thread overview]
Message-ID: <38506050-6923-1cd4-b825-e3a7044a1e58@xs4all.nl> (raw)

Hi,

We now have a new version of luatex on the garden. This is the anual 
context meeting release which is a prelude to next years 1.10 version 
for texlive. The version number is 1.08 (as 1.09 will be out in a few 
months and mostly concerns some fixes needed for arm).

For the average user there are no real differences (luatex 1.10 will 
basically be functionality complete). Of course we use lua 5.3 (1.10 
might actually use 5.4). You can expect (depending on usage) a bit 
better performance as i wrapped some (yet) unsupported stuff into 
fallback functions.

Things to watch out for: context now uses a one-pass mp approach which 
so far worked ok (alan an i tested it in regular usage). This might 
boost performance in case where extensive mp embedding takes place.

Poppler is gone and replaced by pplib by Pawel Jakowski written for us. 
Currently he and luigi are finetuning the c code for portability. Users 
should not notice this (but it removes a dependency). More on some of 
the consequences later. It also makes the binary smaller.

The binary mode in mplib is not available in luatex. It has no real 
benefits (and is probably not used, not even by alan) apart from 
research. This removes a large dependency on foreign code (we try to 
minimlize that) and again makes the binary smaller. We might introduce 
64 bit scaled at some point (luigi will look into that next year).

There are some changes in terms of efficiency that kick in now. I only 
tested on my setup but it's probably ok. Don't expect drastic 
improvements wrr to average performsance from now on. For those on 
windows: i noticed a performance difference between the native and mingw 
binaries (with native being slower, mostly due to format saving and 
loading).

A lot of work went into this release and we hope that it's worth it. I 
will rmove some older code paths in a few weeks (less code that way) so 
then beta's will assume the new binary is used.

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:[~2018-08-31  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31  8:27 Hans Hagen [this message]
2018-08-31 18:56 ` Pablo Rodriguez
2018-08-31 19:33   ` Hans Hagen

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=38506050-6923-1cd4-b825-e3a7044a1e58@xs4all.nl \
    --to=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).