- dev-luatex - NTG Mailing Lists

LuaTeX 1.18.0
by luigi scarso 21 Feb '24

21 Feb '24

The upcoming version 1.18.0 has some changes that are not compatible with previous versions but should only apply in kpse mode: 1) the debug library is disabled; can be enabled with --luadebug 2) os.rename os.remove and lfs library functions are checked from kpse to see if the path is legal I'm sure some packages that use debug won't work without --luadebug at least. LuaLaTeX should be ok, and also ConTeXt mkiv should be ok. -- luigi

1 0

short vs long path on Windows with lua
by Norbert Preining 16 Nov '23

16 Nov '23

Hi all, (for reference: original discussion: https://github.com/rstudio/tinytex/issues/427) in TeX Live we are using runscript.lua https://tug.org/svn/texlive/trunk/Master/bin/windows/runscript.tlu?revision… to resolve scripts, typical examples are fmtutil -> fmtutil.pl updmap -> updmap.pl etc (not only for perl scripts!). It seems that in some cases, the scripts fails to resolve scripts, for example fmtutil-sys will use Windows "short name" passed in, like "FMTUTI~1.EXE" My question: Is there a way in luatex to convert these short names to "proper" (= long) names? Thanks Norbert -- PREINING Norbert https://www.preining.info Mercari Inc. + IFMGA Guide + TU Wien + TeX Live GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

3 3

\leqno in right to left paragraph
by Udicoudco 21 Aug '23

21 Aug '23

Hello, It looks like \leqno is broken in r2l paragraphs (see leqno-rtl-par.tex). I tried to use \eqno and restore \pardirection before and after the equation, but then \parfillskip is on the wrong side. Best Regards, Udi

1 1

Font patches
by Max Chernoff 01 Aug '23

01 Aug '23

Hi Luigi, I've attached a series of font-related patches. Patch 1: Even if you set "tounicode = 1" at the top level of a font, "tounicode = <something>" for each character, and run "pdf.setgentounicode(1)", LuaTeX will only write out a /ToUnicode entry if the document uses "\pdfextension glyphtounicode" somewhere. A minimal(-ish) example: % \pdfextension glyphtounicode{fake!}{0000} \newcount\fontid \directlua{ local height = tex.sp("8bp") local width = tex.sp("36bp") pdf.setgentounicode(1) local inner = font.define { name = "fake-font-inner", parameters = {}, properties = {}, encodingbytes = 0, psname = "none", tounicode = 1, characters = { [1] = { width = width, height = height, depth = 0, tounicode = { 0x1f986 }, } } } tex.count.fontid = font.define { name = "fake-font-virtual", parameters = {}, properties = {}, characters = { [string.byte"x"] = { width = width, height = height, depth = 0, commands = { { "slot", 1, 1 } } } }, type = "virtual", fonts = {{ id = inner }}, } callback.register( "provide_charproc_data", function (mode, font_id, slot) if mode == 2 then return pdf.immediateobj("stream", "36 0 d0 0 0 36 8 re f"), 36 elseif mode == 3 then return 1 / 10 end end ) } x{\setfontid\fontid x}x \bye You would expect that copying the black box would give you a duck, but this only happens if the first line is uncommented. The first patch should fix this. Patch 2: Defining a Type 3 font with a character index greater than 256 can cause a segfault. Using an index >256 is impossible with a T3 font, but you shouldn't be able to cause a segfault from Lua code. Minimal example: \directlua{ local height = tex.sp("8bp") local width = tex.sp("36bp") local id = font.define { name = "fake-font-inner", parameters = {}, properties = {}, encodingbytes = 0, psname = "none", tounicode = 1, characters = { [0x1f986] = { width = width, height = height, depth = 0, } } } callback.register( "provide_charproc_data", function (mode, font_id, slot) if mode == 2 then return pdf.immediateobj("stream", "36 0 d0 0 0 36 8 re f"), 36 elseif mode == 3 then return 1 / 10 end end ) local glyph = node.new("glyph") glyph.font = id glyph.char = 0x1f986 tex.forcehmode() node.write(glyph) } \bye The second patch catches this when the font is initialized, skips the too-large character, and issues a warning. Patch 3: The third patch adds the "provide_charproc_data" callback to the manual. Thanks, -- Max

3 3

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

FFI documentation is missing in luatex reference manual
by Christophe Jorssen 10 May '23

10 May '23

Hi all, If I'm not mistaken, there is no mention of FFI in the luatex reference manual (at least in 1.16). It would be really nice to have some kind of minimal documentation about it. I know it would be better if I could write a patch myself but I'm not fluent enough in English nor technically competent, sorry. Many thanks for the hard work done with luatex. All the best -- Christophe

2 3

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

Extended the documentation of some functions in the os.* namespace (J. Friedrich)
by Josef Friedrich 24 Apr '23

24 Apr '23

The following patch adds a short description of the os.sleep() function which is undocumented to the manual. The C source code of the os.sleep() function can be found here: https://gitlab.lisn.upsaclay.fr/texlive/luatex/-/blob/master/source/texk/we… In addition, the patch documents the optional argument template of the os.tmpdir([template]) function: https://gitlab.lisn.upsaclay.fr/texlive/luatex/-/blob/master/source/texk/we… The patch also fixes a few whitespace issues. See attached patch file. diff --git a/manual/luatex-lua.tex b/manual/luatex-lua.tex index 94dead9e1..01b39d832 100644 --- a/manual/luatex-lua.tex +++ b/manual/luatex-lua.tex @@ -434,8 +434,9 @@ used as building blocks for other helpers. The \type {os} library has a few extra functions and variables: \libidx {os} {selfdir}, \libidx {os} {exec}, \libidx {os} {spawn}, \libidx {os} {setenv}, -\libidx {os} {env}, \libidx {os} {gettimeofday}, \libidx {os} {times}, \libidx -{os} {tmpdir}, \libidx {os} {type}, \libidx {os} {name} and \libidx {os} {uname}, +\libidx {os} {env}, \libidx {os} {gettimeofday}, \libidx {os} {times}, +\libidx {os} {sleep}, \libidx {os} {tmpdir}, \libidx {os} {type}, +\libidx {os} {name} and \libidx {os} {uname}, that we will discuss here. \startitemize @@ -522,19 +523,29 @@ that we will discuss here. \stopitem \startitem - \type {os.times()}returns the current process times according to \ the + \type {os.times()} returns the current process times according to the \UNIX\ C library function \quote {times}. This function is not available on the \MSWINDOWS\ and \SUNOS\ platforms, so do not use this function for portable documents. \stopitem \startitem - \type {os.tmpdir()} creates a directory in the \quote {current directory} + \type {os.sleep(interval[, unit])} suspends the execution of the current run for + a given number of seconds. If the optional argument \type {unit} is present, the + function waits \type {interval / units} seconds. \type {os.sleep(1, 1000)} + for example pauses the program for one millisecond. +\stopitem + +\startitem + \type {os.tmpdir([template])} creates a directory in the \quote {current directory} with the name \type {luatex.XXXXXX} where the \type {X}-es are replaced by a unique string. The function also returns this string, so you can \type {lfs.chdir()} into it, or \type {nil} if it failed to create the directory. The user is responsible for cleaning up at the end of the run, it does not - happen automatically. + happen automatically. You can also use your own \type {template} for the name + of the temporary folder. However, the passed string must end with six capital + \type {X}-es. For example, the template \type {tmp.XXXXXX} could result in the + folder name \type {tmp.vX3gPo}. \stopitem \startitem

2 2

Update the functions overview table of the two namespaces node.* and node.direct.*
by Josef Friedrich 19 Apr '23

19 Apr '23

Add this missing functions: - fix_node_lists - flush_properties_table - get_properties_table - getexpansion - hyphenating - make_extensible - set_properties_mode - setdata - traverse_list - values Put this functions into the right alphabetical sorting order: - setexpansion - getdata according to https://gitlab.lisn.upsaclay.fr/texlive/luatex/-/blob/master/source/texk/we… See patch file diff --git a/manual/luatex-nodes.tex b/manual/luatex-nodes.tex index 347987d41..a57ed98b2 100644 --- a/manual/luatex-nodes.tex +++ b/manual/luatex-nodes.tex @@ -2334,21 +2334,26 @@ consistency. You can of course always define additional accessors using \type \supported {fields} \yes \nop \supported {find_attribute} \yes \yes \supported {first_glyph} \yes \yes +\supported {fix_node_lists} \yes \nop \supported {flatten_discretionaries} \yes \yes \supported {flush_list} \yes \yes \supported {flush_node} \yes \yes +\supported {flush_properties_table} \yes \yes \supported {free} \yes \yes \supported {get_attribute} \yes \yes +\supported {get_properties_table} \yes \yes \supported {get_synctex_fields} \nop \yes \supported {getattributelist} \nop \yes \supported {getboth} \yes \yes \supported {getbox} \nop \yes \supported {getchar} \yes \yes \supported {getcomponents} \nop \yes +\supported {getdata} \nop \yes \supported {getdepth} \nop \yes \supported {getdirection} \nop \yes \supported {getdir} \nop \yes \supported {getdisc} \yes \yes +\supported {getexpansion} \nop \yes \supported {getfam} \nop \yes \supported {getfield} \yes \yes \supported {getfont} \yes \yes @@ -2369,13 +2374,13 @@ consistency. You can of course always define additional accessors using \type \supported {getsubtype} \yes \yes \supported {getsub} \nop \yes \supported {getsup} \nop \yes -\supported {getdata} \nop \yes \supported {getwhd} \yes \yes \supported {getwidth} \nop \yes \supported {has_attribute} \yes \yes \supported {has_field} \yes \yes \supported {has_glyph} \yes \yes \supported {hpack} \yes \yes +\supported {hyphenating} \nop \yes \supported {id} \yes \nop \supported {insert_after} \yes \yes \supported {insert_before} \yes \yes @@ -2388,6 +2393,7 @@ consistency. You can of course always define additional accessors using \type \supported {last_node} \yes \yes \supported {length} \yes \yes \supported {ligaturing} \yes \yes +\supported {make_extensible} \yes \nop \supported {mlist_to_hlist} \yes \nop \supported {new} \yes \yes \supported {next} \yes \nop @@ -2399,20 +2405,22 @@ consistency. You can of course always define additional accessors using \type \supported {rangedimensions} \yes \yes \supported {remove} \yes \yes \supported {set_attribute} \yes \yes +\supported {set_properties_mode} \yes \yes \supported {set_synctex_fields} \nop \yes \supported {setattributelist} \nop \yes \supported {setboth} \nop \yes \supported {setbox} \nop \yes \supported {setchar} \nop \yes \supported {setcomponents} \nop \yes +\supported {setdata} \nop \yes \supported {setdepth} \nop \yes \supported {setdirection} \nop \yes \supported {setdir} \nop \yes \supported {setdisc} \nop \yes +\supported {setexpansion} \nop \yes \supported {setfam} \nop \yes \supported {setfield} \yes \yes \supported {setfont} \nop \yes -\supported {setexpansion} \nop \yes \supported {setglue} \yes \yes \supported {setheight} \nop \yes \supported {setkern} \nop \yes @@ -2443,6 +2451,7 @@ consistency. You can of course always define additional accessors using \type \supported {traverse_char} \yes \yes \supported {traverse_glyph} \yes \yes \supported {traverse_id} \yes \yes +\supported {traverse_list} \nop \yes \supported {traverse} \yes \yes \supported {types} \yes \nop \supported {type} \yes \nop @@ -2451,6 +2460,7 @@ consistency. You can of course always define additional accessors using \type \supported {unset_attribute} \yes \yes \supported {usedlist} \yes \yes \supported {uses_font} \yes \yes +\supported {values} \yes \nop \supported {vpack} \yes \yes \supported {whatsits} \yes \nop \supported {write} \yes \yes

2 1

lua.setluaname(n, s) and lua.getluaname(n): Mismatch between documentation and implementation
by Josef Friedrich 18 Apr '23

18 Apr '23

The documentation and the implementation of the two functions lua.setluaname and lua.getluaname do not match. Minimal working example (MWE): % lua.setluaname(42, '@filename') not working \directlua{ lua.setluaname(nil, 42, '@filename') } \directlua 42 {xxx} \bye This is how the parameters should be arranged in the set function: lua.setluaname(<number> n, <string> s) <string> s = lua.getluaname(<number> n) # Patch: diff --git a/manual/luatex-tex.tex b/manual/luatex-tex.tex index f8c3d5ac6..e953a1802 100644 --- a/manual/luatex-tex.tex +++ b/manual/luatex-tex.tex @@ -96,7 +96,7 @@ If you want to unset a \LUA\ name, you can assign \type {nil} to it. The functio accessors are: \startfunctioncall -lua.setluaname(<string> s,<number> n]) +lua.setluaname(<number> n, <string> s) <string> s = lua.getluaname(<number> n) \stopfunctioncall @@ -2747,7 +2747,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}}] diff --git a/source/texk/web2c/luatexdir/lua/llualib.c b/source/texk/web2c/luatexdir/lua/llualib.c index 0586aba02..d91a9a729 100644 --- a/source/texk/web2c/luatexdir/lua/llualib.c +++ b/source/texk/web2c/luatexdir/lua/llualib.c @@ -319,8 +319,8 @@ static int set_luaname(lua_State * L) { int k; const char *s; - if (lua_gettop(L) == 3) { - k = (int) luaL_checkinteger(L, 2); + if (lua_gettop(L) == 2) { + k = (int) luaL_checkinteger(L, 1); if (k > 65535 || k < 0) { /* error */ } else { @@ -328,8 +328,8 @@ static int set_luaname(lua_State * L) free(luanames[k]); luanames[k] = NULL; } - if (lua_type(L,3) == LUA_TSTRING) { - s = lua_tostring(L, 3); + if (lua_type(L, 2) == LUA_TSTRING) { + s = lua_tostring(L, 2); if (s != NULL) luanames[k] = xstrdup(s); } @@ -340,7 +340,7 @@ static int set_luaname(lua_State * L) static int get_luaname(lua_State * L) { - int k = (int) luaL_checkinteger(L, 2); + int k = (int) luaL_checkinteger(L, 1); if (k > 65535 || k < 0) { /* error */ lua_pushnil(L);

2 2