January 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

linkarea wrong in TRT context
by Ulrike Fischer 24 Jan '23

24 Jan '23

If there is a \textdir change in a paragraph *and* if a link breaks over two lines then then link area is wrong: \hsize=5cm \parskip=1em OK: {abc \textdir TRT \pdfextension startlink attr {/Border[0 0 1]} user{ /Subtype/Link/A<</S/URI/URI(blub)>> } x y y y z \pdfextension endlink abc } end Wrong: {abc \textdir TRT \pdfextension startlink attr {/Border[0 0 1]} user{ /Subtype/Link/A<</S/URI/URI(blub)>> } x y y y y y y y y y y y y y y y z \pdfextension endlink abc } end \pardir TRT \textdir TRT OK: \pdfextension startlink attr {/Border[0 0 1]} user{ /Subtype/Link/A<</S/URI/URI(blub)>> } x y y y y y y y y y y y y y y y z \pdfextension endlink end \bye (extracted from https://tex.stackexchange.com/q/672299/2388) -- Ulrike Fischer http://www.troubleshooting-tex.de/

2 1

duplicated /MediaBox entry if pageattr is used
by Ulrike Fischer 20 Jan '23

20 Jan '23

In pdftex "if the \pdfpageattr value contains the string /MediaBox, then pdfTEX omits outputting its own /MediaBox value". That means that the following produce a PDF with only one /MediaBox in the page dictionary: \pdfcompresslevel0 \pdfobjcompresslevel0 \pdfpageattr{/MediaBox [0 0 200 300]} abc \bye The same is not true for luatex: \pdfvariable compresslevel = 0 \pdfvariable objcompresslevel = 0 \pdfvariable pageattr{/MediaBox [0 0 200 300]} abc \bye leads to two entries (using pdf.setpageattributes gives the same): /MediaBox [ 0 0 595.276 841.89 ] /MediaBox [0 0 200 300] Would it be possible to copy the pdftex behaviour also in luatex? -- Ulrike Fischer http://www.troubleshooting-tex.de/

2 3

Function name mismatch between manual and C code: font.copyfont <-> font.getcopy ?
by Josef Friedrich 17 Jan '23

17 Jan '23

I think that there is a wrong function name documented in the manual. The lfontlib.c C file exports a getcopy function: https://gitlab.lisn.upsaclay.fr/texlive/luatex/-/blob/master/source/texk/we… diff --git a/manual/luatex-fonts.tex b/manual/luatex-fonts.tex index 136d20dd3..037d252ff 100644 --- a/manual/luatex-fonts.tex +++ b/manual/luatex-fonts.tex @@ -728,10 +728,10 @@ font.setfont(<number> n, <table> f) Note that at the moment, each access to the \type {font.fonts} or call to \type {font.getfont} creates a \LUA\ table for the whole font unless you cached it. -If you want a copy of the internal data you can use \type {font.copyfont}: +If you want a copy of the internal data you can use \type {font.getcopy}: \startfunctioncall -<table> f = font.copyfont(<number> n) +<table> f = font.getcopy(<number> n) \stopfunctioncall This one will return a table of the parameters as known to \TEX. These can be

2 1

Typo in the manual
by Josef Friedrich 16 Jan '23

16 Jan '23

diff --git a/manual/luatex-fonts.tex b/manual/luatex-fonts.tex index 136d20dd3..917147c55 100644 --- a/manual/luatex-fonts.tex +++ b/manual/luatex-fonts.tex @@ -788,7 +788,7 @@ Within reasonable bounds you can extend a font after it has been defined. Becaus some properties are best left unchanged this is limited to adding characters. \startfunctioncall -font.addcharacters(<number n>, <table> f) +font.addcharacters(<number> n, <table> f) \stopfunctioncall The table passed can have the fields \type {characters} which is a (sub)table

2 2

Using Harfbuzz with dvilualatex produces invalid font references
by Zameer Manji 15 Jan '23

15 Jan '23

Hello, I have run into a bug when using HarfBuzz and dvilualatex. When the following document is compiled with dvilualatex ``` \documentclass{minimal} \usepackage{fontspec} \setmainfont[Renderer = OpenType]{OpenSans-Regular.ttf } \begin{document} Hello \end{document} ``` The produced DVI file cannot be handled by dvipdfmx. Running dvipdfmx produces the following error: ``` dvipdfmx:fatal: Unable to find TFM file "[OpenSans-Regular.ttf]:mode=harf;shaper=ot;script=latn;language=dflt;+tlig;". ``` Removing '[Render = OpenType]' and running dvipdfmx on the resulting dvi file works fine. -- Zameer Manji

1 0

Typo in the LuaTeX manual: node.type(n)
by Josef Friedrich 15 Jan '23

15 Jan '23

I found a typo in the LuaTeX manual. It would be nice if this error could be corrected. I've attached a patch. I made this patch from the mirrored repository on Github (https://github.com/TeX-Live/luatex) Despite an intensive search I could not find the current development repository of LuaTeX. I read about an upcoming Git migration in the mail archive. Is there any progress? diff --git a/manual/luatex-nodes.tex b/manual/luatex-nodes.tex index d18006df0..a4ba7cfd7 100644 --- a/manual/luatex-nodes.tex +++ b/manual/luatex-nodes.tex @@ -1248,7 +1248,7 @@ This converts a single type name to its internal numeric representation. \libindex {type} \libindex {subtype} -In the argument is a number, then the next function converts an internal numeric +If the argument is a number, then the type function converts an internal numeric representation to an external string representation. Otherwise, it will return the string \type {node} if the object represents a node, and \type {nil} otherwise.

2 1