On 13/07/2015 17:23, Joseph Wright wrote:
> On 13/07/2015 17:05, Stephan Hennig wrote:
>> 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
> 
> We are not unmindful of the problem of code that works with multiple
> formats! Most obviously, luaoftload is required for using the
> higher-level fontspec interface in LaTeX but also works with plain
> LuaTeX to extend the font loader. Whilst we want to work to improve the
> LaTeX support in this area we certainly don't want to break working with
> plain.

David's written a quick demo showing one way of using our code with
plain: much of the fixing up is more to do with the differences between
luatexbase and the current experiments rather than being really to do
with plain. I've added it to ltluatex for comment/testing/...
--
Joseph Wright