Michal Vlasák

@kberry Out of curiosity, do you have one of those 32 bit format files handy? I think this is more of a Lua issue, but I don't know yet how...

Actually, nevermind I got "cross compilation" to 32 bits working. Quick patch to LuaTeX revealed the real error message and also that by mistake I was looking at Lua 5.4...

In Lua 5.4 (unlike Lua 5.3) "ints" and "sizes" are not dumped as are, but instead in a variable length encoding (with a bounds check when loading). This is even...

Also a thought: Lua is very configurable, and the types for "lua_Integer" and "Instruction" could be customly `#defined` in headers, to the appropriate `stdint.h` types if all TeX Live architectures...

@kberry > I'll point Luigi to your patch here and we'll see what he thinks. Already posted an updated patch to the list. https://tug.org/pipermail/luatex/2022-February/007623.html It includes also code that (if...

Linking the mentioned issue: #819 I think that there are two main things here: 1) TeX's and Tectonic's handling of warnings / diagnostics. 2) Use of `\XeTeXtracingfonts=1`. ### Tectonic's handling...

Either we provide the ConTeXt code with allocator for attributes (current solution) or reserve the first 256 attributes for it. I also found the defintion of XeTeX `\font` syntax, it...

I was wrong even in the ConTeXt case, `\font=name` does font name with file name fallback. I currently let the font name lookup automatically fail, so that file names are...

Hm, maybe we could even `\fontfam[lmfonts]` by default? With hot caches, the following (simulating `\fontfam[lmfonts]` in `\everyjob`): ``` \fontfam[lm] \fontfam[heros] test \bye ``` Is: ``` Time (mean ± σ): 127.0...

> We've talked about it before. It would be fine to leave the dependency on luaotfload, but: > > * the luaotfload developers extract fontloader from Context in its actual...