- dev-luatex - Mailing Lists

Correction of a typo in the manual
by Josef Friedrich 10 Apr '23

10 Apr '23

diff --git a/manual/luatex-languages.tex b/manual/luatex-languages.tex index 573727a66..9ca27a095 100644 --- a/manual/luatex-languages.tex +++ b/manual/luatex-languages.tex @@ -140,7 +140,7 @@ hyphenation happens is (normally) when the paragraph or a horizontal box is constructed. When \prm {savinghyphcodes} was zero when the language got initialized you start out with nothing, otherwise you already have a set. -When a \lpr {hjcode} is greater than 0 but less than 32 is indicates the +When a \lpr {hjcode} is greater than 0 but less than 32 it indicates the to be used length. In the following example we map a character (\type {x}) onto another one in the patterns and tell the engine that \type {œ} counts as one character. Because traditionally zero itself is reserved for inhibiting @@ -1110,4 +1110,3 @@ initialized due to \prm {savinghyphcodes} being larger than zero. % 12-34-\vrule width 1em height 1.5ex \par % 12-\hbox{34}-56 \par % 12-\vrule width 1em height 1.5ex-56 \par -

2 1

Documentation of the *_syntex_fields functions
by Josef Friedrich 08 Apr '23

08 Apr '23

The *_syntex_fields functions are located in the node.direct.* namespace, not in the node.* namespace. See source code: set_* https://gitlab.lisn.upsaclay.fr/texlive/luatex/-/blob/master/source/texk/we… get_* https://gitlab.lisn.upsaclay.fr/texlive/luatex/-/blob/master/source/texk/we… diff --git a/manual/luatex-nodes.tex b/manual/luatex-nodes.tex index 42a4aedc7..9b72fdf2c 100644 --- a/manual/luatex-nodes.tex +++ b/manual/luatex-nodes.tex @@ -2490,9 +2490,9 @@ number, for a glue, kern, hlist, vlist, rule and math nodes as well as glyph nodes (although this last one is not used in native \SYNCTEX). \startfunctioncall -node.set_synctex_fields(<integer> f, <integer> l) +node.direct.set_synctex_fields(<integer> n, <integer> f, <integer> l) <integer> f, <integer> l = - node.get_synctex_fields(<node> n) + node.direct.get_synctex_fields(<integer> n) \stopfunctioncall Of course you need to know what you're doing as no checking on sane values takes

2 1

[set|get]omitinfodict -> [set|get]omitinfo
by Josef Friedrich 06 Apr '23

06 Apr '23

diff --git a/manual/luatex-backend.tex b/manual/luatex-backend.tex index e53a81367..672288d45 100644 --- a/manual/luatex-backend.tex +++ b/manual/luatex-backend.tex @@ -125,7 +125,7 @@ after the \PDFTEX\ equivalents. \stopsubsection \startsubsection[title={\type {[set|get]suppressoptionalinfo}, \type {[set|get]trailerid}, -\type {[set|get]omitcidset}, \type {[set|get]omitinfodict} and \type {[set|get]omitmediabox}}] +\type {[set|get]omitcidset}, \type {[set|get]omitinfo} and \type {[set|get]omitmediabox}}] \topicindex{\PDF+options} \topicindex{\PDF+trailer} @@ -134,7 +134,7 @@ after the \PDFTEX\ equivalents. \libindex{gettrailerid} \libindex{settrailerid} \libindex{getomitcidset} \libindex{setomitcidset} \libindex{getomitcharset} \libindex{setomitcharset} -\libindex{getomitinfodict} \libindex{setomitinfodict} +\libindex{getomitinfo} \libindex{setomitinfo} \libindex{getomitmediabox} \libindex{setomitmediabox} The optional info bitset (a number) determines what kind of info gets flushed.

2 1

Possible double use of inserts
by Martin Münch 05 Apr '23

05 Apr '23

May the file LuaInsert.tex consist of \documentclass{minimal} \makeatletter \newcommand{\stressInsert}[1]{% \@tempcnta=0\relax% \@whilenum\the\@tempcnta<#1\do% {\advance\@tempcnta +1\relax% \expandafter\newinsert\csname TestInsert\the\@tempcnta\endcsname% \message{insert \the\@tempcnta: \the\allocationnumber^^J}% }% } \makeatother \stressInsert{70000} \begin{document} \end{document} then > lualatex LuaInsert.tex creates LuaInsert.log, which also contains: This is LuaHBTeX, Version 1.16.0 (TeX Live 2023) (format=lualatex 2023.4.4) ... \TestInsert1=\insert199 insert 1: 199 \TestInsert2=\insert198 insert 2: 198 ... \TestInsert17=\insert183 insert 17: 183 [ *** 1st JUMP HERE *** ] \TestInsert18=\insert252 insert 18: 252 \TestInsert19=\insert251 insert 19: 251 ... \TestInsert68=\insert202 insert 68: 202 \TestInsert69=\insert201 insert 69: 201 [ *** 2nd JUMP HERE *** ] \TestInsert70=\insert65534 insert 70: 65534 \TestInsert71=\insert65533 insert 71: 65533 ... \TestInsert65350=\insert254 insert 65350: 254 \TestInsert65351=\insert253 insert 65351: 253 \TestInsert65352=\insert252 [ *** AGAIN?! ***] insert 65352: 252 \TestInsert65353=\insert251 [ *** AGAIN?! ***] insert 65353: 251 ... \TestInsert65368=\insert236 [ *** AGAIN?! ***] insert 65368: 236 \TestInsert65369=\insert235 [ *** AGAIN?! ***] insert 65369: 235 ! No room for a new \count . \ch@ck ...\else \errmessage {No room for a new #3} \fi l.12 \stressInsert{70000} ? x So, are \insert252 to \insert235 used twice?! And Lua does not even stop there because of "No room for a new insert", but because there is no room for a new \count! Otherwise more inserts would see double use? Should after \insert253 (!, not 235) the next \newinsert produce some error "No room for a new \insert"?

2 2

Typos, whitespace issue in the manual and in the C source code
by Josef Friedrich 04 Apr '23

04 Apr '23

diff --git a/manual/luatex-backend.tex b/manual/luatex-backend.tex index afbaa84d0..e53a81367 100644 --- a/manual/luatex-backend.tex +++ b/manual/luatex-backend.tex @@ -619,12 +619,11 @@ pdfe.getstatus(<pdfe document>) The returned codes are: - \starttabulate[|c|l|] \DB value \BC explanation \NC \NR \TB \NC \type {-2} \NC the document is (still) protected \NC \NR -\NC \type {-1} \NC the document failed to open \NC \NR +\NC \type {-1} \NC the document failed to open \NC \NR \NC \type {0} \NC the document is not encrypted \NC \NR \NC \type {1} \NC the document has been unencrypted \NC \NR \LL @@ -943,7 +942,7 @@ pdfscanner.scan (<pdfe array>, <table> operatortable, <table> info) pdfscanner.scan (<string>, <table> operatortable, <table> info) \stopfunctioncall -The first argument should be a \LUA\ string or a stream or array onject coming +The first argument should be a \LUA\ string or a stream or array object coming from the \type {pdfe} library. The second argument, \type {operatortable}, should be a \LUA\ table where the keys are \PDF\ operator name strings and the values are \LUA\ functions (defined by you) that are used to process those operators. diff --git a/manual/luatex-fontloader.tex b/manual/luatex-fontloader.tex index 0a830ed00..1e12b61f1 100644 --- a/manual/luatex-fontloader.tex +++ b/manual/luatex-fontloader.tex @@ -225,7 +225,7 @@ by fontloader while applying the AFM file. On success, \type {nil} is returned. As mentioned earlier, the return value of \type {fontloader.open} is a userdata object. One way to have access to the actual metrics is to call \type {fontloader.to_table} on this object, returning the table structure that is -explained in the following sections. In teh following sections we will not +explained in the following sections. In the following sections we will not explain each field in detail. Most fields are self descriptive and for the more technical aspects you need to consult the relevant font references. @@ -911,7 +911,7 @@ space|-|separated string of glyph names in this class. \startsubsection[title={\type {math}}] -The math table has the variables that are also discussed in the chapter aboout +The math table has the variables that are also discussed in the chapter about math: \type {ScriptPercentScaleDown}, \type {ScriptScriptPercentScaleDown}, \type {DelimitedSubFormulaMinHeight}, \type {DisplayOperatorMinHeight}, \type {MathLeading}, \type {AxisHeight}, \type {AccentBaseHeight}, \type @@ -971,7 +971,6 @@ The \type {scripts} subtable: \LL \stoptabulate - The \type {lang} subtable: \starttabulate[|l|l|p|] diff --git a/source/texk/web2c/luatexdir/font/writettf.c b/source/texk/web2c/luatexdir/font/writettf.c index cf034e98d..6270cbf04 100644 --- a/source/texk/web2c/luatexdir/font/writettf.c +++ b/source/texk/web2c/luatexdir/font/writettf.c @@ -1518,7 +1518,7 @@ static void do_writeotf(PDF pdf, fd_entry * fd) if (tracefilenames) tex_printf("<<%s", cur_file_name); ttf_read_tabdir(); - /*tex Read teh font parameters. */ + /*tex Read the font parameters. */ if (ttf_name_lookup("head", false) != NULL) ttf_read_head(); if (ttf_name_lookup("hhea", false) != NULL) @@ -1570,4 +1570,3 @@ void writeotf(PDF pdf, fd_entry * fd) xfree(ttf_buffer); cur_file_name = NULL; } -

2 2

Typo in the manual
by Josef Friedrich 02 Apr '23

02 Apr '23

diff --git a/manual/luatex-nodes.tex b/manual/luatex-nodes.tex index 1b7325ac5..42a4aedc7 100644 --- a/manual/luatex-nodes.tex +++ b/manual/luatex-nodes.tex @@ -1321,7 +1321,7 @@ creates a node at the \TEX\ level. \libindex{flush_node} \libindex{flush_list} -The next one the node \type {n} from \TEX's memory. Be careful: no checks are +The next one removes the node \type {n} from \TEX's memory. Be careful: no checks are done on whether this node is still pointed to from a register or some \type {next} field: it is up to you to make sure that the internal data structures remain correct.

2 1

Duplicate line in luafflib.c
by Josef Friedrich 01 Apr '23

01 Apr '23

diff --git a/source/texk/web2c/luatexdir/luafontloader/src/luafflib.c b/source/texk/web2c/luatexdir/luafontloader/src/luafflib.c index 434413b00..41e5c3a32 100644 --- a/source/texk/web2c/luatexdir/luafontloader/src/luafflib.c +++ b/source/texk/web2c/luatexdir/luafontloader/src/luafflib.c @@ -1236,7 +1236,6 @@ static void handle_pfminfo(lua_State * L, struct pfminfo pfm) dump_intfield(L, "vlinegap", pfm.vlinegap); dump_intfield(L, "hhead_ascent", pfm.hhead_ascent); dump_intfield(L, "hhead_descent", pfm.hhead_descent); - dump_intfield(L, "hhead_descent", pfm.hhead_descent); dump_intfield(L, "os2_typoascent", pfm.os2_typoascent); dump_intfield(L, "os2_typodescent", pfm.os2_typodescent); dump_intfield(L, "os2_typolinegap", pfm.os2_typolinegap);

2 1

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