- dev-luatex - NTG Mailing Lists

Multiple problems with tprint
by Marcel Krüger 28 Mar '19

28 Mar '19

Hi, there are multiple issues memory issues in tprint: If the buffer passed to tprint only contains of to be escaped characters, the `xmalloc(strlen(sss)*3)` is too small: The final `\0` can not be written, so this causes a write into unallocated memory. If t_flush_buffer is called for such a buffer at the last position, there is an additional `\n` written, so `xmalloc(strlen(sss)*3+2)` is needed. Additionally, the test `if (*buffer)` is used to test if there is something to print left. If the parameter is empty, `*buffer` is never written, so valgrind complains about `if (*buffer)` depending on uninitialized memory. Instead, `if (i)` can be used: `i` is the length of the written part of the buffer, so `i==0` iff there is nothing to write. A related problem is with `max_print_line`: If the point where the line should be broken falls inside the escape sequence of an escaped character, the line limit is ignored. This can be fixed by adding if (term_offset+2>=max_print_line) { wterm_cr(); term_offset=0; } as in `wterm_char` also in tprint above `buffer[i++] = '^';`. A full patch fixing all three issues is attached. Best regards Marcel Krüger

1 0

pdfe error / question
by Ulrike Fischer 23 Mar '19

23 Mar '19

According to the documentation pdfe.status can be use to check if a pdf has been opened. But when I try \directlua{ dict=pdfe.open("testinput.pdf") pdfe.status(dict)} \bye I get an error (./test-utf8.tex[\directlua]:1: attempt to call a nil value (field 'status') And how I'm supposed to extract an object reference from a dictionary? There are commands getinteger, getstring but nothing that looks like a "getreference". -- Ulrike Fischer http://www.troubleshooting-tex.de/

2 3

\mathchar feature request
by Linas Stonys 21 Mar '19

21 Mar '19

Hi, I was tracing \mathchar created nodes in text mode and they are just a simple glyph nodes with subtype 256. The problem is that there is no how to control the output changing the text font. It's ok if engine throws messages about missing characters in font. But if current font has a different character in this slot that is a problem. Documentation says that this command is allowed in text mode: """""" The commands \mathchar, and \Umathchar and control sequences that are the result of \math- chardef or \Umathchardef are also acceptable in the horizontal and vertical modes. In those cases, the \textfont from the requested math family is used. """""" but maybe could be any other subtype assigned to the glyph node that these characters could be traced down and one could write some control functions (for example error "\mathchar is not allowed in text mode") What do you think? Thanks, Linas

5 7

change in pdfliteral logging
by Ulrike Fischer 14 Mar '19

14 Mar '19

In the following example (which doesn't give a valid pdf, it is only for demo) the logging has changed between texlive 2018 and 2019: In texlive 2018 the log said: ...\pdfliteral page"/Artifact /BMC" In texlive 2019 I now get ...\pdfliteral page <lua data reference 770> This sadly means that my testsuites are no longer really meaningful. Is there a way to get the old behaviour back? Or to somehow add the content of the "<lua data reference 770>" to the log? \tracingoutput 1 \showboxbreadth \maxdimen \showboxdepth \maxdimen \tracingonline 1 \setbox0\hbox{a} \directlua{ for n in node.traverse(tex.box[0].list) do local bdcnode = node.new("whatsit","pdf_literal") bdcnode.data = "/Artifact /BMC" bdcnode.mode=1 tex.box[0].list = node.insert_before(tex.box[0].list,n,bdcnode) end } \box0 \bye -- Ulrike Fischer http://www.troubleshooting-tex.de/

2 1

objcompresslevel doesn't work correctly with pdf 2.0
by Ulrike Fischer 02 Mar '19

02 Mar '19

When setting the pdf version so 2.0 (by using the not really documented variable majorversion) I get a warning that objcompresslevel needs a minorversion >4: \pdfvariable majorversion 2 \pdfvariable minorversion 0 \pdfvariable objcompresslevel=1 blb \bye This is LuaTeX, Version 1.10.0 (TeX Live 2019/W32TeX) (format=luatex 2019.3.1) 2 MAR 2019 13:13 restricted system commands enabled. **test-utf8.tex (./test-utf8.tex warning (pdf backend): objcompresslevel > 0 requires minorversion > 4 -- Ulrike Fischer https://www.troubleshooting-tex.de/

1 0

lualatex (incorrectly) replaces em dashes with hyphens
by Matt Kline 01 Mar '19

01 Mar '19

Hi folks, The current version of lualatex distributed with TeX Live (as installed today via TeX Live's install-tl, or via Arch Linux's packages) replaces em dashes with hyphens if they're not separated by any space. For example, if given \documentclass{article} % This makes no difference: %\usepackage{fontspec} %\setmainfont[Ligatures=TeX]{Latin Modern Roman} % \begin{document} \noindent% I have \emph{no} idea why em dashes---these things---are being replaced with hyphens in Lua\LaTeX. But --- this only seems to happen if there is no space around them. \end{document} lualatex replaces the first two dashes with hyphens, but not the third. The problem goes away when I downgrade to a version from December (Arch's previous release of their texlive-core package was built December 1), and neither pdflatex or xelatex exhibit this behavior.

6 15

a quick question?
by Steven 19 Feb '19

19 Feb '19

Hi, Not sure this is the correct email to write to but I've been on your website luatex.org and on Linkedin, and couldn't identify whom I should write to. The coworker I am trying to reach is in charge of writing product descriptions and content - Maybe that is the one in charge of Marketing / SEO? Thanks for helping! I am not trying to sell you anything - my company is developing an AI powered tool to create unique product descriptions automatically and I want to ask someone who deals with this every day a few question to better understand how this is done today. --- Steven J. Morell Head of Growth AX Semantics GmbH Stuttgart, Germany https://about.ax-semantics.com

1 0

luatex and broken locales
by Norbert Preining 19 Feb '19

19 Feb '19

Hi Luigi, here on Debian we got a bug report that luatex cannot build formats under a broken locale. I can reproduce this on standard TeX Live, too: $ LC_TIME=en_DE.UTF-8 luatex -ini -jobname=luatex -progname=luatex luatex.ini Unable to read environment locale: exit now. $ (same on dev version) It comes from the code of luainit env_locale = setlocale (LC_ALL, ""); if (!env_locale && !lua_only) { fprintf(stderr,"Unable to read environment locale: exit now.\n"); exit(1); } I agree that the locale is completely broken, and the system does not support this locale. BUT it would be nice if luatex would not crash on such a setup, at least during format build? WDYT? Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + JAIST + TeX Live + Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

2 2

Fwd: luatex engine new option request
by Taco Hoekwater 05 Feb '19

05 Feb '19

> Begin forwarded message: > > From: Linas Stonys <lstonys(a)vtex.lt> > Subject: luatex engine new option request > Date: 5 February 2019 at 12:26:35 CET > To: dev-luatex-owner(a)ntg.nl > > Hi, > tex engine provides several compilation modes: > --interaction=STRING set interaction mode (STRING=batchmode/nonstopmode/scrollmode/errorstopmode) > --halt-on-error stop processing at the first error > > But it lacks one very important where one could hide > all the output from terminal except errors (when tex waits for stdin). > And tex engine would interact with user by letting him decide what to do next instead of killing at first error or compiling with errors til the end. > > For typsetter or a simple tex user terminal messages ar just a "white noise". While there is no errors. It just slows down all the compilation. If there is a lot of messages you can gain several seconds by hiding all the output. > > What I want to offer is a new option: > --output-on-prompt=LINES_NO output to terminal only on input prompt (LINES_NO lines of buffered stdout, all of it if 0) > > It works like a "batchmode" but pics all the stdout. And when stdin > is required it will print latest nuber of stodout lines (LINES_NO). > After hitting enter (or what ever tex says to do) it will hide the output again till next stdin. > Lets say --output-on-prompt=20 then on error user will see all the error > and can decide what to do next. > > We have implemented such a feature to luatex 1.09.2 and it works perfectly. Could we send some how a patch to request implement this feature for future releases? We could provide the code for the latest release. > > Thanks, Linas > Taco Hoekwater Elvenkind BV

2 2

pre everydisplay hook feature request
by Linas Stonys 05 Feb '19

05 Feb '19

Hi luatex developers, I want to ask your opinion about new hook (token list) "\everypredisplay". This should work just before $$ (display start) while math group is not started. There is \everydisplay but it works immediately after math mode start. Why one would need it? Now there is now how to control spaces between to equations. Lets say journal requires spaces around displays (and in display inner lines) and text 6pt. I can do with tex macros by hooking into every latex display environment and putting some code right before $$. In that code I add \par; then I do manipulations of \abovedisplayskip by checking \lastskip; and controling \panalty by looking at \prevgraf. Finaly I add \noindent to remove empty boxes. Everything is perfect while I do not get plain display makros $$ a+b $$. Manualy to retype them is not an option. So the hook of \everypredisplay where \par could work would be very useful. What do you think? I'm using luatex 1.09.2.

2 3