LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stephan Hennig <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Mon, 13 Jul 2015 18:05:49 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (20 lines)
Am 06.07.2015 um 22:10 schrieb Joseph Wright:

> We are looking for feedback in two areas. Firstly, does the
> functionality provided cover the needs of package authors using LuaTeX?
> Secondly, we would like input on how a transition to new support code
> can be managed. We are reluctant to suggest a complex compatibility
> layer for either our code or the existing packages, and suspect at this
> stage that a clean 'step change' may be needed for packages working with
> LuaTeX. However, this is a complex area and needs careful consideration.

Let me question the idea of implementing resource allocation stuff in
the LaTeX kernel.  What is the appropriate way to claim resources, e.g.,
attributes, in a format agnostic pure Lua low-level module foo.lua
(which is then used in format specific wrappers/packages)?  That foo.lua
module can't certainly make use of function latex.new_attribute, since
that is only available to LaTeX users.  Or do I miss something?

Best regards,
Stephan Hennig

ATOM RSS1 RSS2