- dev-luatex - NTG Mailing Lists

unexpected delimiter construction with classic tfm cmex font
by David Carlisle 11 Jan '25

11 Jan '25

There are some images of the output and discussion of the \showlists trace in the stackexchange post at https://tex.stackexchange.com/a/734734/1090 but this plain luatex file \tracingonline1 \showboxdepth10 \immediate\write500{\meaning\Arrowvert} $\Arrowvert + \Big\Arrowvert\showlists $ \expandafter\show\the\textfont3 \bye produces the expected || character with pdftex but a { character with luatex even though both claim to be using the same extension font (cmex10) David

3 5

CMap unrecoverably broken
by Denis Bitouzé 27 Dec '24

27 Dec '24

Hi, I recently encountered an issue with LuaTeX (1.18.0) + Ghostscript (10.04.0) and it turns out that the culprit seems to be LuaTeX :) This may be summarized as follows: 1. Compile with `lualatex` the following `test.tex` file: --8<---------------cut here---------------start------------->8--- \documentclass{article} \begin{document} Foo. \end{document} --8<---------------cut here---------------end--------------->8--- 2. Run then the following command: --8<---------------cut here---------------start------------->8--- gs -V -P- -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sstdout=%stderr "-sOutputFile=test.pdf.pdf" test.pdf --8<---------------cut here---------------end--------------->8--- On GNU/Linux, this returns: ┌──── │ GPL Ghostscript 10.04.0 (2024-09-18) │ Copyright (C) 2024 Artifex Software, Inc. All rights reserved. │ This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: │ see the file COPYING for details. │ Processing pages 1 through 1. │ Page 1 │ │ The following errors were encountered at least once while processing this file: │ CMap unrecoverably broken │ │ **** This file had errors that were repaired or ignored. │ **** The file was produced by: │ **** >>>> LuaTeX-1.18.0 <<<< │ **** Please notify the author of the software that produced this │ **** file that it does not conform to Adobe's published PDF │ **** specification. └──── You can find more details on how I came to LuaTeX in the TeX Live mailing list archive and on the Ghostcript's Bugzilla: ┌──── │ https://tug.org/pipermail/tex-live/2024-December/050985.html │ https://bugs.ghostscript.com/show_bug.cgi?id=708201 └──── Best regards. -- Denis

5 6

CMap unrecoverably broken
by Denis Bitouzé 19 Dec '24

19 Dec '24

Hi, I recently encountered an issue with LuaTeX (1.18.0) + Ghostscript (10.04.0) and it turns out that the culprit seems to be LuaTeX :) This may be summarized as follows: 1. Compile with `lualatex` the following `test.tex` file: --8<---------------cut here---------------start------------->8--- \documentclass{article} \begin{document} Foo. \end{document} --8<---------------cut here---------------end--------------->8--- 2. Run then the following command: --8<---------------cut here---------------start------------->8--- gs -V -P- -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sstdout=%stderr "-sOutputFile=test.pdf.pdf" test.pdf --8<---------------cut here---------------end--------------->8--- On GNU/Linux, this returns: ┌──── │ GPL Ghostscript 10.04.0 (2024-09-18) │ Copyright (C) 2024 Artifex Software, Inc. All rights reserved. │ This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: │ see the file COPYING for details. │ Processing pages 1 through 1. │ Page 1 │ │ The following errors were encountered at least once while processing this file: │ CMap unrecoverably broken │ │ **** This file had errors that were repaired or ignored. │ **** The file was produced by: │ **** >>>> LuaTeX-1.18.0 <<<< │ **** Please notify the author of the software that produced this │ **** file that it does not conform to Adobe's published PDF │ **** specification. └──── You can find more details on how I came to LuaTeX in the TeX Live mailing list archive and on the Ghostcript's Bugzilla: ┌──── │ https://tug.org/pipermail/tex-live/2024-December/050985.html │ https://bugs.ghostscript.com/show_bug.cgi?id=708201 └──── Best regards. -- Denis

1 0

charwidth and fullembed fonts
by luca boncompagni 18 Nov '24

18 Nov '24

Hi to all. I think that if I do a fullembed of a font, it is not correct to include the only charwidth used in the pdf. Think about a font used in a /Form. I tested the attached patch and it seems ok in my case, but I'm not sure it is fully OK. Thanks, Luca

1 0

Allow usage of img module from texlua
by Max Chernoff 17 Nov '24

17 Nov '24

Hi Luigi, I'm currently reimplementing the "extractbb" program in Lua, but for this to work properly I need access to the "img" module from Lua-only mode. Right now I'm using a questionable hack to make this work https://github.com/gucci-on-fleek/extractbb/blob/v0.0.7/source/extractbb-sc… but I'd prefer it if I could do this without using the FFI module. I've attached a (rather trivial) patch to allow this. Thanks, -- Max

1 0

\toksapp cannot be set expandable
by Petr Olsak 12 Oct '24

12 Oct '24

Hello, my question: is there a reason why \toksapp assignment cannot be set expandable by \immediateassigned or \immediateassignment? We can compare: \immediateassigned{\toks0={abc} \toks0\ea{\the\toks0 xyz}} it works. On the other hand: \immediateassigned{\toks0={abc} \toksapp0{xyz}} fails with error: ! This can't happen (prefix). l.2 \immediateassigned{\toks0={abc} \toksapp 0{xyz}} Where is a difference? It should be great if \toksapp can be set expandable. I use it in my macro \replstring. If very large strings are modified by this macro at many points then there is significantly better calculation speed with \toksapp than \toks\ea{\the\toks} (approximately ten times better). So \toksapp is optimal but if it is used in a macro then the macro cannot be set expandable. Best regards Petr Olsak

3 2

Typo in source/texk/web2c/luatexdir/font/texfont.c
by Josef Friedrich 15 Sep '24

15 Sep '24

diff --git a/source/texk/web2c/luatexdir/font/texfont.c b/source/texk/web2c/luatexdir/font/texfont.c index 496cb0838..16e8a5131 100644 --- a/source/texk/web2c/luatexdir/font/texfont.c +++ b/source/texk/web2c/luatexdir/font/texfont.c @@ -1878,7 +1878,7 @@ void read_expand_font(void) /*tex - Here's an old (sort of obsolete) letterspace-a-font helper. It does so by by + Here's an old (sort of obsolete) letterspace-a-font helper. It does so by creating a virtual font. */

2 1

`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