- dev-luatex - NTG Mailing Lists

Typos in the manual
by Josef Friedrich 14 Mar '23

14 Mar '23

The functions todirect() and tonode() are only available in the node.direct.* namespace and not in node.* diff --git a/manual/luatex-nodes.tex b/manual/luatex-nodes.tex index 1367ea1fc..98ee29b57 100644 --- a/manual/luatex-nodes.tex +++ b/manual/luatex-nodes.tex @@ -2195,8 +2195,8 @@ number often is reported when you print node related information. You go from userdata nodes and there numeric references and back with: \startfunctioncall -<integer> d = node.todirect(<node> n)) -<node> n = node.tonode(<integer> d)) +<integer> d = node.direct.todirect(<node> n) +<node> n = node.direct.tonode(<integer> d) \stopfunctioncall The userdata model is rather robust as it is a virtual interface with some @@ -2437,8 +2437,8 @@ consistency. You can of course always define additional accessors using \type \supported {subtypes} \yes \nop \supported {subtype} \yes \nop \supported {tail} \yes \yes -\supported {todirect} \yes \yes -\supported {tonode} \yes \yes +\supported {todirect} \nop \yes +\supported {tonode} \nop \yes \supported {tostring} \yes \yes \supported {traverse_char} \yes \yes \supported {traverse_glyph} \yes \yes diff --git a/manual/luatex-graphics.tex b/manual/luatex-graphics.tex index 0e34a6528..54eed1757 100644 --- a/manual/luatex-graphics.tex +++ b/manual/luatex-graphics.tex @@ -822,7 +822,7 @@ anonymous capsules like loop variables are not accessible). <table> p = get_path (mp,<string> name) \stopfunctioncall -The path is returned a a table with subtables that have six numbers: the +The path is returned as a table with subtables that have six numbers: the coordinates of the point, pre- and postcontrol. A \type {cycle} fields indicates if a path is cyclic. diff --git a/manual/luatex-nodes.tex b/manual/luatex-nodes.tex index 1367ea1fc..2f9bdf299 100644 --- a/manual/luatex-nodes.tex +++ b/manual/luatex-nodes.tex @@ -1877,7 +1877,7 @@ word boundaries are possible). \startfunctioncall node.unprotect_glyph(<node> n) -node.unprotect_glyphs(<node> n,[<node> n]) +node.unprotect_glyphs(<node> n,[<node> m]) \stopfunctioncall Subtracts 256 from all glyph node subtypes. This and the next function are @@ -1891,7 +1891,7 @@ processing. The second argument is optional and indicates the end of a range. \startfunctioncall node.protect_glyph(<node> n) -node.protect_glyphs(<node> n,[<node> n]) +node.protect_glyphs(<node> n,[<node> m]) \stopfunctioncall Adds 256 to all glyph node subtypes in the node list starting at \type {n},

2 1

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

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 17 Jan '23

17 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 16 Jan '23

16 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