February 2023 - dev-luatex - NTG Mailing Lists

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 06 May '23

06 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

new luatex binary in TL pretest crashes when \directmeatpost is used
by Petr Olsak 01 Mar '23

01 Mar '23

Hello luatex developers, I installed TL pretest with new luatex binary and I found a bug in it, when \directmetapost defined in minim-mp package is used. Try the following file: \input minim-mp \directmetapost{ % define the pattern picture letter; letter = maketext("a"); beginpattern(a) draw letter rotated 45; matrix = identity rotated 45; endpattern(12pt,12pt); % use the pattern beginfig(1) fill fullcircle scaled 3cm withpattern(a) withcolor 3/4red; draw fullcircle scaled 3cm withpen pencircle scaled 1; endfig; } \bye and run luatex. The luatex from TL 2022 runs without problems but luatex from TL 2023 says: This is LuaTeX, Version 1.16.0 (TeX Live 2023) restricted system commands enabled. (./test.tex (/usr/local/texlive/2023/texmf-dist/tex/luatex/minim-mp/minim-mp.tex (/usr/local/texlive/2023/texmf-dist/tex/luatex/minim/minim-alloc.tex) (/usr/local/texlive/2023/texmf-dist/tex/luatex/minim/minim-pdfresources.tex)){/ usr/local/texlive/2023/texmf-var/fonts/map/pdftex/updmap/pdftex.map} ! error: (pdf backend): 2 unmatched 'save' after form shipout ! ==> Fatal error occurred, no output PDF file produced! Michal Vlasak noticed that the problem is probably related to the commit: https://gitlab.lisn.upsaclay.fr/texlive/luatex/-/commit/c1909e4a4c5311197a2… Best regards Petr Olsak

5 5

node properties lost after mlist_to_hlist conversion
by Linas Stonys 09 Feb '23

09 Feb '23

Hi, If I add properties to math nodes they do not appear in HLIST converted nodes. But if I add attributes they stay to this node for all time. And if I create custom node (for example `user_defined` WHATSIT) then properties doesn't disappear when MLIST is converted to HLIST. EXAMPLE: ``` \documentclass{article} \usepackage[color=no,verbosity=0,channel=log]{nodetree} \nodetreeregister{preout} \nodetreeregister{mhlist} \directlua{ %% node.set_properties_mode(true,true) function set_mathchar_property(n) if node.type(n.id) == "math_char" then % set any attribute node.set_attribute(n, 999, 999) % set any property node.setproperty(n, {math_char = true}) elseif node.type(n.id) == "noad" then if n.nucleus then set_mathchar_property(n.nucleus) end elseif node.type(n.id) == 'sub_mlist' then set_mathchar_property(n.head) local USER_MARK = node.new(node.id("whatsit"), 8) USER_MARK.type = 115 USER_MARK.value = "math added whatsit" node.set_attribute(USER_MARK, 888, 888) node.setproperty(USER_MARK, {math_whatsit = true}) n.head = node.insert_before(n.head, n.head, USER_MARK) end end function parse_math_char(h) set_mathchar_property(h) return h end luatexbase.add_to_callback('pre_mlist_to_hlist_filter', parse_math_char, 'set_mathchar_property') } \begin{document} ${aa}$ \end{document} ``` Here is the output. You can see that after line break only WHATSIT has properties and attributes 888=888, 999=999 stays sticky: ``` Callback: mlist_to_hlist - need_penalties: true - display_type: text ------------------------------------------ └─NOAD ╚═nucleus: └─SUB_MLIST ╚═head: ├─WHATSIT subtype: user_defined, type: 115, value: math added whatsit, attr: 888=888 │ properties: {['math_whatsit'] = true} ├─NOAD │ ╚═nucleus: │ └─MATH_CHAR fam: 1, char: a, attr: 999=999 │ properties: {['math_char'] = true} └─NOAD ╚═nucleus: └─MATH_CHAR fam: 1, char: a ----------------------- Callback: post_linebreak_filter ------------------------------------------ ├─GLUE subtype: baselineskip, width: 7.69pt └─HLIST subtype: line, width: 345pt, height: 4.31pt ╚═head: ├─LOCAL_PAR ├─HLIST subtype: indent, width: 15pt ├─MATH ├─HLIST width: 10.57pt, height: 4.31pt │ ╚═head: │ ├─WHATSIT subtype: user_defined, type: 115, value: math added whatsit, attr: 888=888 │ │ ╚═ properties: {['math_whatsit'] = true} │ ├─GLYPH subtype: 256, char: a, width: 5.29pt, height: 4.31pt, attr: 999=999 │ └─GLYPH subtype: 256, char: a, width: 5.29pt, height: 4.31pt ├─MATH subtype: endmath ├─PENALTY subtype: linepenalty, penalty: 10000 ├─GLUE subtype: parfillskip, stretch: +1fil └─GLUE subtype: rightskip ----------------------- ``` There is setup `node.set_properties_mode(true,true)` which should do something with properties copying but here it does nothing. Could math noad properties be copied to corresponding new noads: - MATH_CHAR properties moved to GLYPH; - SUB_MLIST properties moved to HLIST; - and others depending on conversion Thanks, Linas

1 0

Typos in the manual and in the source code
by Josef Friedrich 06 Feb '23

06 Feb '23

# Typo in the source code diff --git a/source/texk/web2c/luatexdir/luatex.c b/source/texk/web2c/luatexdir/luatex.c index 14426db6a..c11b0ca62 100644 --- a/source/texk/web2c/luatexdir/luatex.c +++ b/source/texk/web2c/luatexdir/luatex.c @@ -329,7 +329,7 @@ int shell_cmd_is_allowed(const char *cmd, char **safecmd, char **cmdname) free(buf); /* - Is *cmdname listed in a texmf.cnf vriable as shell_escape_commands = + Is *cmdname listed in a texmf.cnf variable as shell_escape_commands = foo,bar,... ? */ p = cmdlist; # Lua code example diff --git a/manual/luatex-tex.tex b/manual/luatex-tex.tex index a5e458088..9109a09db 100644 --- a/manual/luatex-tex.tex +++ b/manual/luatex-tex.tex @@ -1379,8 +1379,8 @@ tex.print(tex.romannumeral(123)) The first one returns the name only, the second one reports the size too. \startfunctioncall -tex.print(tex.fontname(tex.fontname)) -tex.print(tex.fontname(tex.fontidentidier)) +tex.print(tex.fontidentifier(1)) +tex.print(tex.fontname(1)) \stopfunctioncall \subsubsection{\type {sp}} # No longer there? 10.3.15.6 tex.getlinenumber and tex.setlinenumber diff --git a/manual/luatex-tex.tex b/manual/luatex-tex.tex index a5e458088..f88fe1bb9 100644 --- a/manual/luatex-tex.tex +++ b/manual/luatex-tex.tex @@ -1412,29 +1412,6 @@ following: \stopitem \stopitemize -\subsubsection{\type {tex.getlinenumber} and \type {tex.setlinenumber}} - -\libindex{getlinenumber} -\libindex{setlinenumber} - -You can mess with the current line number: - -\startfunctioncall -local n = tex.getlinenumber() -tex.setlinenumber(n+10) -\stopfunctioncall - -which can be shortcut to: - -\startfunctioncall -tex.setlinenumber(10,true) -\stopfunctioncall - -This might be handy when you have a callback that read numbers from a file and -combines them in one line (in which case an error message probably has to refer -to the original line). Interference with \TEX's internal handling of numbers is -of course possible. - \subsubsection{\type {error} and \type {show_context}} \topicindex{errors} @@ -2747,7 +2724,6 @@ The options match commandline arguments from \type {kpsewhich}: If \type {--output-directory} is specified and the value is a relative pathname, the file is searched first here and then in the standard tree. - \stopsubsection \startsubsection[title={\type {init_prog}}] # 14.2.7 get[from][dictionary|array|stream] -> 14.2.7 get[dictionary|array|stream] diff --git a/manual/luatex-backend.tex b/manual/luatex-backend.tex index 8d4c366c3..c4c646290 100644 --- a/manual/luatex-backend.tex +++ b/manual/luatex-backend.tex @@ -739,7 +739,7 @@ string is hex encoded. The second call returns the unencoded string. \stopsubsection -\startsubsection[title={\type {get[from][dictionary|array|stream]}}] +\startsubsection[title={\type {get[dictionary|array|stream]}}] \libindex {getdictionary} \libindex {getfromdictionary} \libindex {getarray} \libindex {getfromarray} # 14.2.8 [open|close|readfrom|whole|]stream -> 14.2.8 [open|close|readfrom|readwhole]stream diff --git a/manual/luatex-backend.tex b/manual/luatex-backend.tex index 8d4c366c3..062ec43ad 100644 --- a/manual/luatex-backend.tex +++ b/manual/luatex-backend.tex @@ -775,7 +775,7 @@ print(pdfe.open("foo.pdf").Pages[1]) \stopsubsection -\startsubsection[title={\type {[open|close|readfrom|whole|]stream}}] +\startsubsection[title={\type {[open|close|readfrom|readfromwhole]stream}}] \libindex {openstream} \libindex {closestream}

2 2