[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1034501: ITP: luametatex -- New generation processing Engine for ConTeXt



Package: wnpp
Severity: wishlist
Owner: Hilmar Preusse <hille42@web.de>
X-Debbugs-Cc: debian-devel@lists.debian.org

I'm not fully sure about the final name of the source package. The OpenSuSE
people name it texlive-context-bin, maybe I'll use a similar naming.

* Package name    : luametatex
  Version         : 2.10.07
  Upstream Contact: Hans Hagen <pragma@wxs.nl>
* URL             : https://github.com/contextgarden/luametatex
* License         : GPL, MIT/X
  Programming Lang: C, CWeb, C++
  Description     : New generation processing Engine for ConTeXt

This is a follow up on the LuaTeX project. The source is considered part
of the ConTeXt distribution and managed by the ConTeXt development team
and the ConTeXt user group. That way we can guarantee that the engine and
this TeX macro package work together as expected. The idea is that users
can easily compile the source themselves and that way have a guaranteed
long term (minimal) TeX based installation. Because the management scripts
are in Lua, only one binary is needed to serve the ConTeXt distribution.

In the source code we try to stay close to the ancestors, LuaTeX, pdfTeX,
eTeX and TeX, but in the meantime due to additions there is quite some
diverge. There are new primitives and submechanisms, there is more control
over the inner workings, font handling is mostly delegated to Lua and there
is no built-in backend. The code base is all-inclusive and has no (nor will
have) dependencies on external libraries.

 - The TeX engine in this package will be (probably) the default processing
   engine of ConTeXt. The upcoming 2023 release of Context will hence depend
   on it.
 - I'm a member of the Debian TeX Task force, I'll maintain the package as
   a member of the team. As I'm not a DD, I'd a sponsor for the initial
   upload.

-- 
sigmentation fault

Attachment: signature.asc
Description: PGP signature


Reply to: