From: luigi scarso <luigi.scarso@gmail.com>
To: "General discussion of LuaTeX." <luatex@tug.org>,
luatex development list <dev-luatex@ntg.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>,
Dev Context <dev-context@ntg.nl>
Subject: LuaTeX 1.0.3 announcement
Date: Fri, 17 Feb 2017 20:57:09 +0100 [thread overview]
Message-ID: <CAG5iGsAE3Yc+b6rHf7vV9_63Jw6pkPyMgfhpz841wwXUzgM2+A@mail.gmail.com> (raw)
==============================================================
LuaTeX Release 1.0.3 was released 2017021514
==============================================================
This is a minor upgrade and probably this version will go on texlive.
There are a couple
of fixes and additions.
- We added a few a few more helpers in the pdf namespace (like
set|get]gentounicode,
[set|get]omitcidset and set|get]decimaldigits. Some helpers were
moved from the tex
to the pdf namespace.
- We added a build_page_insert callback for inserts so that one can
for instance adapt
spacing on demand.
- On the agenda has been some more control over word start and end in
hyphenation and
this is now possible via hyphenationbounds. We also updated the
manual with some more
details.
- An old tracker item with respect to control over spacing around math
was revived and
has resulted in mathsurroundmode (one can wonder how useful this is).
- We improved the resolution detection in included jpeg images.
- An ffi library has been added to luatex so that it is more in sync
with luajittex. This
permits easy and flexible loading of libraries. Our policy is to
make luatex as lean
as possible with no dependencies and this is a step towards that.
Eventually we hope
to support all relevant platforms.
- The glue and skip register accessors have been improved as a step in
freeing the user
from glue spec management.
- We added a few more getters and setters for nodes in order to get a
more consistent
set.
- Irrelevant fields have been removed from the status table and an
engine identifier
has been added.
- Of course there are numerous fixes and improvements but none of
these have consequences
for the interfaces.
- The manual has been updated but will be improved over time.
Have fun,
Hans, Luigi, Taco
_______________________________________________
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context
next reply other threads:[~2017-02-17 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 19:57 luigi scarso [this message]
2017-02-18 8:11 ` Henri Menke
2017-02-18 8:42 ` luigi scarso
2017-02-18 13:27 ` Henri Menke
2017-02-18 13:52 ` Hans Hagen
2017-02-18 13:59 ` luigi scarso
2017-02-18 16:03 ` Alan Braslau
2017-02-18 14:08 ` Hans Hagen
2017-02-18 23:34 Akira Kakuto
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=CAG5iGsAE3Yc+b6rHf7vV9_63Jw6pkPyMgfhpz841wwXUzgM2+A@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).