ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	"General discussion of LuaTeX." <luatex@tug.org>,
	 luatex development list <dev-luatex@ntg.nl>,
	Dev Context <dev-context@ntg.nl>
Subject: Luatex 1.08.0 announcement
Date: Fri, 31 Aug 2018 21:00:33 +0200	[thread overview]
Message-ID: <CAG5iGsAeFxJ3Sq_7F9btTL_-XV5_u7NwzB7MTJkQUB6tivyeBw@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1424 bytes --]

==============================================================
LuaTeX 1.08 2018-08-28
==============================================================


(1) This release is a prelude to 1.10, the next stable iteration of LuaTeX
after version 1.00.

(2) Lua 5.3 is now considered to be default and we might use 5.4 in version
1.10. There are no real functional changed expected. You still need to
rename
the binary for 5.3!

(3) Binary mode is no longer available in MPlib but it is still available in
stand alone MetaPost. This simplifies compilation and reduces dependencies.

(4) The dependency on Poppler for pdf image inclusion has been removed. We
now use a small dedicated library written by Pawel Jakowski. We no longer
need c++ compilers. We're in the process of making it behave well on all
platforms. It has been tested on intel platforms.

(5) We know that there can be some (alignment) issues with the arm platform
but these are looked into. Therefore, later this year we will release 1.09.
Version 1.10 is planned for TeXlive. We hope that ffi works ok on intel and
arm platforms at that point.

(6) There have been some extensions to the Lua libraries and some callbacks
have been added. Also, a few new primitives have been introduced. The
documentation mentions the stable extensions.

(7) There are the usual bug fixes and cleanups but there have been no real
fundamental changes in the API.

The LuaTeX team

[-- Attachment #1.2: Type: text/html, Size: 1840 bytes --]

[-- Attachment #2: Type: text/plain, Size: 144 bytes --]

_______________________________________________
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context

             reply	other threads:[~2018-08-31 19:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 19:00 luigi scarso [this message]
2018-10-23 18:12 ` Luatex 1.09.0 announcement luigi scarso
2018-10-24 21:15   ` [dev-context] " Mojca Miklavec
2018-10-24 21:19     ` luigi scarso
2018-10-24 21:23       ` Mojca Miklavec
2018-10-24 21:32         ` luigi scarso
     [not found]   ` <CAG5iGsDY1ckcnqb7DGSbWj2kD1P-+p_KWRvhhRTh=6J0gtiP7A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-25 18:02     ` Luatex 1.09.0 announcement (following) luigi scarso
     [not found]       ` <CAG5iGsBYBfd6_u6Kq+tk6-SFbY5T_4ObSFqUOnu-rbEz=_oqdQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-25 18:57         ` [luatex] " Werner LEMBERG
2018-10-25 19:04           ` luigi scarso
2019-01-30 10:11     ` Luatex 1.09.2 announcement luigi scarso
2019-10-28 21:35       ` Luatex 1.11.1 announcement luigi scarso

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=CAG5iGsAeFxJ3Sq_7F9btTL_-XV5_u7NwzB7MTJkQUB6tivyeBw@mail.gmail.com \
    --to=luigi.scarso@gmail.com \
    --cc=dev-context@ntg.nl \
    --cc=dev-luatex@ntg.nl \
    --cc=luatex@tug.org \
    --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).