December 2019 - dev-luatex

wrong no-file-line-error option
by Hironobu Yamashita 17 Jan '20

17 Jan '20

Hi, The command-line option -no-file-line-error behaves exactly the same as -file-line-error. hironobu$ cat test.tex \x hironobu$ echo x | luatex test This is LuaTeX, Version 1.10.0 (TeX Live 2020/dev) restricted system commands enabled. (./test.tex ! Undefined control sequence. l.1 \x ? warning (pdf backend): no pages of output. Transcript written on test.log. hironobu$ echo x | luatex -file-line-error test This is LuaTeX, Version 1.10.0 (TeX Live 2020/dev) restricted system commands enabled. (./test.tex ./test.tex:1: Undefined control sequence. l.1 \x ? warning (pdf backend): no pages of output. Transcript written on test.log. hironobu$ echo x | luatex -no-file-line-error test This is LuaTeX, Version 1.10.0 (TeX Live 2020/dev) restricted system commands enabled. (./test.tex ./test.tex:1: Undefined control sequence. l.1 \x ? warning (pdf backend): no pages of output. Transcript written on test.log. hironobu$ Best, Hironobu

1 1

LuaTeX 1.10.0 cannot embed properly PDFs with 4-bit images
by L. E. Segovia 17 Jan '20

17 Jan '20

Hello, I would like to report that since TeX Live 2019, LuaTeX is unable to embed properly a certain type of image I have. These sort of images are embedded in the PDFs generated by the tool "Comprobantes en línea" of Argentina's IRS (Administración Federal de Ingresos Públicos, https://www.afip.gob.ar) This is an example: https://comunadealvear.gob.ar/wp-content/uploads/2017/03/30710518803_01_000… (or just search online for the string "Esta Administración Federal no se responsabiliza por los datos ingresados en el detalle de la operación"). Embed this file using the following snippet: \documentclass{article} \usepackage{luatex85} \usepackage{incgraph} \begin{document} \incgraph{30710518803_01_0002_00000009.pdf} \end{document} Where the white-and-grey AFIP logo appears in the original, LuaTeX instead embeds a grey-on-grey image, probably by messing with the alpha channel. I have consistently reproduced this on every update since the 2019 release. XeLaTeX and pdfTeX do not have this issue. Please let me know if I can be of more assistance. I hope I've posted to the right mailing list. Best regards, Leonardo -- Leonardo E. Segovia https://www.amyspark.me

3 6

Allow skippig the font cache in font.getfont
by Marcel Fabian Krüger 12 Dec '19

12 Dec '19

Hello, could font.getfont get an option to always return a new font table instead of returning the current one? While for many fonts a cached table makes sense, sometimes it would be useful to also have access to the ooriginal table, e.g. to see which characters are `used`, inspect the result of `font.addcharacters` or inspect other changes which might be applied to the underlying font from TeX. I attached a patch implementing this by adding a `nocache` parameter to `font.getfont`, such that `font.getfont(true, font_id)` always generates a new table. IMO `font.getfont(font_id, true)` would look nicer, but that wouldn't be compatible to older LuaTeX versions which always expect the font is as last parameter. Best regards, Marcel

2 1

commands with a non-letter in token.set_macro
by Ulrike Fischer 11 Dec '19

11 Dec '19

Commands that should be use in token.set_macro must already exist. But while it is easy to predefine a command like \blub it seems not to be possible to do it with commands consisting of a \ with a non-letter. E.g. I put this in a luatest.lua token.set_macro("foo","\\bar\\blub\\!") and then compile \def\!{hallo} \def\blub{hallo} \directlua{require"luatest"} \show\foo \bye I get: > \foo=macro: ->\bar \blub BAD!. l.254 \show\foo so the \blub works, but not the \!. How can one repair this? -- Ulrike Fischer https://www.troubleshooting-tex.de/

2 1

Re: [Dev-luatex] Request for bugfix - user defined whatsit node
by luigi scarso 05 Dec '19

05 Dec '19

On Tue, Dec 3, 2019 at 6:16 PM Hans Hagen <j.hagen(a)xs4all.nl> wrote: > On 11/15/2019 12:35 PM, Sigitas Tolusis wrote: > > Noticed two bugs. > > > > 1. Mised case for user defined whatsit node type 108 (‘l’ Lua value) > > in function check_node_wrapup_core (texnodes.c:2482). > > Possible fix: just add the same as cases for types ’s’ and ‘d’. > > Insert line at texnodes.c:2500 > > case ‘l': > > > > 2. In function flush_node_wrapup_core (texnodes.c:2201) for user defined > > whatsit node type ‘l’ we have: free_user_lua(user_node_value(p)). > > But in luanode.c:409 free_user_lua is defined as: > > > > void free_user_lua(pointer p) > > { > > if (user_node_value(p) != 0) { > > luaL_unref(Luas, LUA_REGISTRYINDEX, user_node_value(p)); > > } > > } > > > > So we have two times user_node_value and it generates segmentation fault. > > Possible fix: free_user_lua(p); // (texnodes.c:2223) > fixed in next luatex beta buit best test then > > Hans > Done in rev. 7233 . -- luigi

1 0