- dev-luatex - NTG Mailing Lists

`os.execute` special output is still undocumented
by Jérôme LAURENS 10 Jun '24

10 Jun '24

The thread https://tug.org/pipermail/luatex/2015-November/005536.html points out that `os.execute` is still version `5.1`. It is said there that "one can always wrap os.execute into something that does what one wants" How to do that to get the "5.3" output of `os.execute`, in any situation of course? This design policy is so special that it should definitely be documented.

2 1

user_defined node clears \lastskip
by Linas Stonys 30 May '24

30 May '24

Hi, I'm sure that for lua gurus it is known behavior that user_defined whatsit clears the \lastskip but for me it was a big surprise. little example: aa \vskip11.1pt \showthe\lastskip \directlua{% local x = node.new('whatsit', 'user_defined') x.type=115 x.value="TEXT" node.write(x) }% \showthe\lastskip \bye log: > 11.1pt. l.4 \showthe\lastskip ? > 0.0pt. l.13 \showthe\lastskip I just accidentally noticed that I messed up output trying to markup document. I was sure that luatex will step over these whatsits. Is there another way to write user_defined whatsits directly without effecting \lastskip? My goal is to mark text in DVI mode with user_defined whatsits and on the shipout turn them to postscript \special's for accessible pdf Thanks, Linas

4 9

continuation links looses the linkmargin
by Ulrike Fischer 06 Mar '24

06 Mar '24

If I compile the following example in texlive 2023 with LuaTeX, Version 1.16.0, Development id: 7567 then only the first part of the link on the first line has a link margin, in the following line the link is tight around the text: \hsize=1.5cm \pdfvariable linkmargin3pt \noindent\pdfextension startlink attr {/Border [0 0 1]} user {/Subtype /Link /A << /Type /Action /S /URI /URI (http://luatex.org/) >>}% Link Link Link Link Link Link Link Link Link \pdfextension endlink \bye In texlive 2022 there is no problem. -- Ulrike Fischer http://www.troubleshooting-tex.de/

2 4

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

07 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