- dev-luatex - NTG Mailing Lists

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

Not searching the font cache
by Jouke Witteveen 08 Jan '19

08 Jan '19

Hi, I ran into an inconvenience with lualatex and would like some help debugging it. Consider the following .tex file: ---- documentclass{article} \usepackage{bbm} \begin{document} $\mathbbm{1}$ \end{document} ---- When compiling with pdflatex, the font file for the bbm font is created in the local cache (~/.texlive/texmf-var/fonts) only if it does not exist. When the font exists in the cache, it is used without warning. When compiling with lualatex, the font file is created every time. When the font exists, this results in a simple warning ("mktexpk: [...] already exists."). Trying to create the fonts slows down compilation noticeably. How do I go about debugging this? The fact that pdflatex has no problems suggests that this is not an issue with my texmf.cnf, right? Regards, - Jouke

2 3

require "lfs" doesn't work on LuajitTeX
by ARATA Mizuki 27 Dec '18

27 Dec '18

Hi, Even though LuajitTeX has lfs as a built-in library, trying to load it via `require` doesn't work. (LuaTeX with Lua 5.2/5.3 doesn't have this problem) This is because the field package.loaded["lfs"] is not set during initialization. To fix this, change Luas_open to set the module (returned by the module loader) to the package.loaded table, which is available as _LOADED on the registry table. Also, zlib suffers from a similar problem, both on LuaTeX and LuajitTeX. Here is a proposed patch to fix these problems: diff --git a/source/texk/web2c/luatexdir/lua/luastuff.c b/source/texk/web2c/luatexdir/lua/luastuff.c index 0d9342223..a0590c400 100644 --- a/source/texk/web2c/luatexdir/lua/luastuff.c +++ b/source/texk/web2c/luatexdir/lua/luastuff.c @@ -36,9 +36,14 @@ int lua_active = 0; #define Luas_load(Luas,getS,ls,lua_id) \ lua_load(Luas,getS,ls,lua_id); #define Luas_open(name,luaopen_lib) \ + luaL_findtable(L, LUA_REGISTRYINDEX, "_LOADED", 1); \ lua_pushcfunction(L, luaopen_lib); \ lua_pushstring(L, name); \ - lua_call(L, 1, 0); + lua_call(L, 1, 1); \ + lua_pushvalue(L, -1); /* copy of module */ \ + lua_setfield(L, -3, name); /* _LOADED[name] = module */ \ + lua_setglobal(L, name); /* _G[name] = module */ \ + lua_pop(L, 1); /* pop _LOADED table */ #else #define Luas_load(Luas,getS,ls,lua_id) \ lua_load(Luas,getS,ls,lua_id,NULL); @@ -347,8 +352,7 @@ void luainterpreter(void) luatex_socketlua_open(L); } /*tex |zlib|'s slightly odd calling convention */ - luaopen_zlib(L); - lua_setglobal(L, "zlib"); + Luas_open("zlib", luaopen_zlib); luaopen_gzip(L); /*tex our own libraries register themselves */ luaopen_fio(L); -- Mizuki

2 3

epdf libray <EmbFile>:save()
by Reinhard Kotucha 26 Dec '18

26 Dec '18

Hello everybody, I'm working on a script ATM which is using the epdf library. The manual says <boolean> = <EmbFile>:save() -- will go The manual also says <string> = <EmbFile>:name() -- not (yet) implemented Will the latter allow me to save the file to the disk as usual e.g., using the IO library? Don't know what <EmbFile>:name() is supposed to do. Would't it be better if <FileSpec>:getEmbeddedFile() returns the file as a string instead of userdata? Everything would be easier then. At least at user level. The removal of <EmbFile>:save() will break existing scripts anyway, so I think that changing the behavior of <FileSpec>:getEmbeddedFile() is even less invasive. Merry Christmas, Reinhard -- ------------------------------------------------------------------ Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ------------------------------------------------------------------

2 1

Unicode-Math in LuaLaTeX and XeLaTeX
by Mathias Schickel 12 Dec '18

12 Dec '18

Dear LuaTeX and XeTeX teams, it seems that recent versions of LuaLaTeX and XeLaTeX contain some issues regarding the rendering of opentype fonts using the unicode-math package. I have already contacted Will Robertson about these bugs because I supposed the unicode-math package could cause them. According to Will the math rendering is done by the engines and not by unicode-math. This is why I am contacting you now. The first issue is the usage of the staircase kerning boxes of opentype math fonts. They are obviously not applied in expressions like $f_j$ using LuaLaTeX. The index is rendered too far away from the glyph. If we use XeLaTeX we get the correct output. The second issue is present in both LuaLaTeX and XeLaTeX. If we have an index together with an exponent like j the index is rendered too high – in fact it is risen compared to the expression that uses an index only. A typical example is $f_n^j$. I have prepared a minimal example that shows the problems and have attached it and the outputs using the current versions of LuaLaTeX and XeLaTeX contained in TeXLive. For the sake of completeness it should be mentioned that ConTeXt using the LuaTeX engine as well does not show any of these issues. This leads me to the conclusion that either LuaLaTeX does not use the most recent version of LuaTeX or that the issues are not caused by the engine itself. Maybe you have a clue what leads to the bugs I mentioned. I hope they can be solved soon. Kind regards, Mathias Schickel

2 2