dev-luatex November 2021

dev-luatex@ntg.nl

4 participants
7 discussions

Luatex 1.12.0 announcement.
by luigi scarso 27 May '23

27 May '23

============================================================== LuaTeX 1.12.0 2020-03-15 ============================================================== This is the release for TeX live 2020. --shell-restricted now forbids loading of dso (dll/so object) Scaled virtual font Aadditional primitives \eTeXglue[stretch|shrink]order for querying order the etex way. Extra features runtoks tex.getmodenames() (as these can differ per engine/version) Permit nested runtoks in more complex situations of nesting (HH) More accurate and correct test for tex.[set|get]math Minor clean-up and bugs fixed -- luigi

4 8

Fix for pdf_literal Lua string / token list conversions
by Michal Vlasák 07 May '23

07 May '23

Hello, take this plain LuaTeX example: \setbox0=\hbox{\pdfextension literal{0 g}} % 1) \directlua{ local literal = tex.getbox(0).head texio.write_nl("log", "literal.data="..literal.data) } \showbox0 % 2) \directlua{ local literal = tex.getbox(0).head literal.data = "test" literal.token = "toks" texio.write_nl("log", "literal.token="..(literal.token or "nil")) } \showbox0 % 3) patch test \directlua{ tex.set("everyjob", "asd") texio.write_nl("log", tex.get("everyjob")) } \bye Expected log output (abridged): 1) literal.data=0 g .\pdfliteral origin{0 g} 2) literal.token=toks .\pdfliteral origin{toks} Actual output: 1) literal.data=data .\pdfliteral origin{0 g} 2) literal.token=characters .\pdfliteral origin <lua data reference 153> In the first case the Lua accessor returns a value which happens to be on top of the stack (the key "data" itself). In the second case an index into TeX memory is misinterpreted as a Lua registry index, so the returned data is essentially garbage. Patch for both issues is attached. I also extended `tokenlist_from_lua` (which is what `nodelib_gettoks` is defined as) to allow an index argument. The previous version used the value on top of the stack, which probably worked for every use currently in LuaTeX, but seemed rather dangerous and subtle. The patch is from git, though it can be applied normally with patch -Np1 < pdf_literal.patch Kind regards, Michal Vlasák

2 3

Re: [Dev-luatex] bug#48064: texlive-* packages fail to build non-deterministically
by Ludovic Courtès 31 Dec '21

31 Dec '21

Hello, While investigating luatex crashes in the TeX Live 2020 package of GNU Guix¹, we identified the following heap corruption reported by Valgrind (this is on GNU/Linux, with glibc 2.33): --8<---------------cut here---------------start------------->8--- sh-5.0$ ~ludo/.guix-profile/bin/valgrind --extra-debuginfo-path=/gnu/store/f933bvd6ab6l2lg6xl6k1a6jwvcls0z6-glibc-2.33-debug/lib/debug "luatex" "-interaction=nonstopmode" "-output-directory=build" "&luatex" "amsbsy.dtx" ==28531== Memcheck, a memory error detector ==28531== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==28531== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==28531== Command: luatex -interaction=nonstopmode -output-directory=build &luatex amsbsy.dtx ==28531== This is LuaTeX, Version 1.12.0 (TeX Live 2020) restricted system commands enabled. ==28531== Invalid write of size 8 ==28531== at 0x485C691: lua_pushlstring (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x568E03: load_hyphenation (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x56B41C: undump_language_data (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x4DFB9F: load_fmt_file (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x4EF0ED: main_body (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x45118D: main (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== Address 0xae14170 is 0 bytes after a block of size 1,168 alloc'd ==28531== at 0x483EBE1: realloc (in /gnu/store/jlmh0jbgr6zn4iyvhfbvxps8pykzj5ry-valgrind-3.16.1/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==28531== by 0x46695D: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x486D932: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x48660F2: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x4868BE7: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x4868FCF: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x486988B: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x485C6BB: lua_pushlstring (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x568E03: load_hyphenation (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x56B41C: undump_language_data (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x4DFB9F: load_fmt_file (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x4EF0ED: main_body (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== ==28531== Invalid write of size 4 ==28531== at 0x485C6A2: lua_pushlstring (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x568E03: load_hyphenation (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x56B41C: undump_language_data (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x4DFB9F: load_fmt_file (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x4EF0ED: main_body (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x45118D: main (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== Address 0xae14178 is 8 bytes after a block of size 1,168 alloc'd ==28531== at 0x483EBE1: realloc (in /gnu/store/jlmh0jbgr6zn4iyvhfbvxps8pykzj5ry-valgrind-3.16.1/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==28531== by 0x46695D: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x486D932: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x48660F2: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x4868BE7: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x4868FCF: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x486988B: ??? (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x485C6BB: lua_pushlstring (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/lib/libtexlua53.so.5.3.5) ==28531== by 0x568E03: load_hyphenation (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x56B41C: undump_language_data (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x4DFB9F: load_fmt_file (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== by 0x4EF0ED: main_body (in /gnu/store/w20xxg8p0wksbrxxvj3y46fngvr3954w-texlive-bin-20200406/bin/luatex) ==28531== [...] valgrind: m_mallocfree.c:305 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed. valgrind: Heap block lo/hi size mismatch: lo = 1232, hi = 68. This is probably caused by your program erroneously writing past the end of a heap block and corrupting heap metadata. If you fix any invalid writes reported by Memcheck, this assertion failure will probably go away. Please try that before reporting this as a bug. --8<---------------cut here---------------end--------------->8--- Does that ring a bell? Is there a chance this problem was fixed in the meantime? Thanks in advance, Ludovic. ¹ https://issues.guix.gnu.org/48064

3 4

os.uname on 64 bit Windows
by Reinhard Kotucha 23 Dec '21

23 Dec '21

Hi, on a 64 bit Windows machine os.uname() erroneously returns machine i686 On the same machine I get under Linux machine x86_64 with both, x86_64-linux and i386-linux binaries. Thus I assume that the keyword 'machine' refers to the hardware, not to how the binaries were compiled (32 vs. 64 bit). The complete output of for k,v in pairs(os.uname()) do print(k,v) end is release build 9200 nodename R804 version 6.02 machine i686 sysname Windows 8 Regards, Reinhard -- ------------------------------------------------------------------ Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ------------------------------------------------------------------

3 8

Trouble with generating warning messages in Unicode
by निरंजन 30 Nov '21

30 Nov '21

Hello, I am having trouble with generating a warning message with unicode characters and LuaLaTeX. My code is as follows: \documentclass{article} \begin{filecontents}[overwrite]{quack.sty} \ProvidesPackage{quack}[2021/11/30 v0.1 quack quack] \newcommand{\quack}{% \PackageWarningNoLine{quack}{% ककाकिकी खखाखिखी गगागिगी घघाघिघी ङङाङिङी\MessageBreak चचाचिची छछाछिछी जजाजिजी झझाझिझी ञञाञिञी\MessageBreak टटाटिटी ठठाठिठी डडाडिडी ढढाढिढी णणाणिणी% }% } \end{filecontents} \usepackage{quack} \begin{document} \quack \end{document} If I run this with xelatex, the warning message is printed as expected. With pdflatex and lualatex it isn't. In a GitHub issue[1] I was told that pdftex and luatex count in bytes and I need to reset it with max_print_line in order to print this warning correctly. As it has to be set in the .cnf or .ini files in the local installations or per compile, I asked if it can be set in the TeX code. They told me to report this to luatex developers and therefore I am mailing this issue here. There are two questions: 1. If I set the max_print_line to, say 300, it prints the log in an unusual way. Everything in the log is affected. So can luatex be requested to count the strings the way XeLaTeX counts them? What implication will it have? 2. If the above is not possible/worth/advisable; can there be a feature to set the max_print_line in the TeX code? David Carlisle says[2] in LuaTeX it can be checked, but not changed. [1]: https://github.com/lualatex/luatexbase/issues/22 [2]: https://github.com/lualatex/luatexbase/issues/22#issuecomment-982553035

1 0

\partokenname, \partokencontext in LuaTeX?
by Petr Olsak 19 Nov '21

19 Nov '21

Hello, may I ask if the primitives \partokenname, \partokencontext will be implemented into LuaTeX? They were implemented in pdftex and XeTeX into TeXlive sources. I would very much welcome their implementation in LuaTeX, I need then on OpTeX macros. Regards Petr Olsak ----------- texk/web2c/NEWS: - new primitives \partokenname and \partokencontext allow overriding the name of the internally-emitted \par token at blank lines, the end of vboxes, etc. ----------- \pdftexprimitive{\Syntax{\Tex{\partokenname} \Whatever{control-sequence}}} \bookmark{\tex{partokenname}} \TeX{} inserts the {\it par-token} at empty lines and at various more places into the input stream. Its meaning is {\it end-paragraph} by default and it can be changed (by \type{\def}, for example). Its name is \type{\par} by default and you can change its name by \type{\partokenname}\Something{control-sequence}. The name of the {\it par-token} is given \Something{control-sequence}. The setting performed by \type{\partokenname} is global. The no-\type{\long} macros throw the error ``runaway argument'' if {\it par-token} is scanned to its parameter regardless its name. The following example releases the name \type{\par} to the ``user name space'', i.e.\ users can define and use \type{\par} as they need without any influence to behavior of internal \TeX{} algorithms. \starttyping \catcode`\_=11 \let\_par=\par \partokenname\_par Hello world.\end \stoptyping The token with name \type{\_par} is auto-emitted at the empty line and before \type{\end} primitive in this example. The no-\type{\long} macros can read parameters with \type{\par} but \type{\_par} is prohibited. \pdftexprimitive{\Syntax{\Tex{\partokencontext} \Whatever{number}}} \bookmark{\tex{partokencontext}} The {\it par-token} (i.e.\ the token with the name \type{\par} or with the name given by \type{\partokenname}) is inserted into the input stream depending on the \type{\partokencontext} value. Its value can be: 0: {\it par-token} is inserted at empty lines (more exactly, when a token category 5 is found in the state~$N$ of reading a line) and before \type{\end}, \type{\vskip}, \type{\hrule}, \type{\unvbox}, and \type{\halign} when \TeX{} is in horizontal mode and at various error recovery cases. 1: {\it par-token} is inserted as above and moreover at the end of \type{\vbox}, \type{\vtop}, and \type{\vcenter} if \TeX{} is in horizontal mode. 2: {\it par-token} is inserted as above and moreover at the end of \type{\insert}, \type{\vadjust}, \type{\output}, \type{\noalign}, and items of \type{\valign} if \TeX{} is in horizontal mode. Default is \type{\partokencontext=0}, i.e.\ the cases 1 and 2 are processed by direct call of {\it end-paragraph} routine without emitted {\it par-token}. This is classical \TeX{} behavior. If \type{\partokencontext=1} then \TeX\ inserts {\it par-token} in additional cases: when vertical boxes are completed but horizotal mode is not finished. The settings \type{\partokencontext=2} deactivates all cases where classical \TeX\ uses direct {\it end-paragraph} routine and {\it par-token} is inserted in such cases. The setting value to the register \type{\partokencontext} is local.

2 1

math.tointeger in l-math
by Robert 18 Nov '21

18 Nov '21

Hi, [sorry, I know it's the wrong list, but I'm not subscribed to ntg-context] I think line 144 in l-math.lua should read function math.ult(m,n) otherwise, the function math.tointeger would be overwritten with older luatex versions. (reference: https://source.contextgarden.net/tex/context/base/mkiv/l-math.lua ) Best, -- Robert

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

dev-luatex November 2021