ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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>,
	David Carlisle <d.p.carlisle@gmail.com>,
	 Joseph Wright <joseph.wright@morningstar2.co.uk>,
	Dev Context <dev-context@ntg.nl>
Subject: Luatex 0.87.0 announcement
Date: Sun, 20 Dec 2015 22:54:30 +0100	[thread overview]
Message-ID: <CAG5iGsD7-cqbVpT+CJXCwhpMuj4aq4w5Q4eooBZO5NS2e704Tg@mail.gmail.com> (raw)


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

New luatex release, 0.87.0
From NEWS:

==================================================
This is a next step upto 0.90 and it has the following changes:

- image data is no longer stored in the format (it was fragile anyway)

- pdf backend data generated when in ini mode is no longer stored in  the
format

- (incomplete) \mag support removed from pdf backend (this functionality is
  kept in dvi mode)

- there are a couple of improvements that should make luatex run a little
bit faster
  (but of course that depends on the job at hand)

- some further pending issues / cleanup has been done (but this is not
reflected in the
  interface)

- there is a new primitive \nospace:

  \nospace=1   do now not inject glue for spaces (not even zero glue)
  \nospace=2   inject zero glue for spaces

- there are new primitives \hpack, \vpack and \tpack that are like \hbox,
\vbox and
  \vtop but they don't trigger callbacks

- we no longer keep track of older math character and delimiter definition
states,
  but this should normally go unnoticed

- from now on only ^^XX, ^^C, ^^^^XXXX and ^^^^^^XXXXXX are supported so no
funny odd
  values (three and five)

- texio.setescape(0) disables escaping to terminal (a matter of taste)

- the (current) lc codes are now saved with the (current) language when
patterns are
  loaded unless one hs used \hjcode instead of \lccode; overloading of
\hjcodes is
  possible (but of course goes ahead of hyphenation which is delayed till
parbuilding or
  packaging

- active characters can now be set with: \letcharcode123=\foo (experimental)

- there are some experimental new primitives but these will be described
when they are
  stable (currently being tested)

- there is more backend error reporting and all error messages adn warnings
(the non-tex
  ones) have been normalized

- of course there are the usual small fixes and additional setters and
getters in libraries
  (see manual)
==================================================

Last minute note:
 --synctex
doesn't work. It will be fixed in the next release.

As usual,
the archives can be downloaded from supelec:

        https://foundry.supelec.fr/projects/luatex/

You could also check out the sources via anonymous svn:

  svn co --username anonsvn --password anonsvn              \
      https://foundry.supelec.fr/svn/luatex/tags/beta-0.87.0

Bugs and feature requests can be added to the issue tracker at

       http://tracker.luatex.org

When you use context or latex you need an updated format. The latest
version of
context can be fetched from the context garden, latex from ctan. For latex
you can contact David and Joseph as they are dealing with the update.






Have fun,
Hans, Luigi, Taco (in alphabetical order this time)

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

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

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

                 reply	other threads:[~2015-12-20 21:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAG5iGsD7-cqbVpT+CJXCwhpMuj4aq4w5Q4eooBZO5NS2e704Tg@mail.gmail.com \
    --to=luigi.scarso@gmail.com \
    --cc=d.p.carlisle@gmail.com \
    --cc=dev-context@ntg.nl \
    --cc=dev-luatex@ntg.nl \
    --cc=joseph.wright@morningstar2.co.uk \
    --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).