Hi, The code has been checked in for the next luatex beta. The current MKIV beta is already prepared for that (primitive initializations and changed directlua support). Also, there are a few bug fixes (esp the vf positioning) that might result in better output. There are some pending issues with math but they might as well relate to issues with the lm fonts. Anyway, we tested the beta a few days and it should work ok. One new feature in MKIV is names lua runs. In the current version we no longer have multiple lua instances (we decided that it made no sense as no data can be shared). However, in MKIV we do have a few mildly isolated instances that are defined as follows: \definenamedlua[user] [private user instance] \definenamedlua[third] [third party module instance] \definenamedlua[module] [module instance] \definenamedlua[isolated][isolated instance] the names kind of reflect what their intended usage is. By default one has no access to global data unless prefixed by global, so for instance one can access the global character data as in (untested): \startusercode tex.sprint(global.characters.data[123].description) \startusercode (there is also \usercode{...}) This prevents that users mess up with the data unintended. However, there is still read and write access so be careful. I see no advantage in a more strict model than this. Since each call to lua is reentrant, errors in your scripts will normally not result in a crash of \MKIV. The error message mentiones the second argument to the previous definitions. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------