dev-luatex May 2021

dev-luatex@ntg.nl

5 participants
5 discussions

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

\tracingtokens=1, ( ) are logged curiously
by Petr Olsak 21 May '21

21 May '21

Suppose: ----------------------------------------- \tracingscantokens=1 \scantextokens{first} \scantextokens{second} \bye ----------------------------------------- and run luatex test. Then the ( and ) are logged curiously: ( ( ... )) Why all closing )) are logged after end command? If we change \scantextokens to \scantokens, then ( and ) behaves more logical in log file and in the terminal: ( ) ( ). Petr Olsak

3 3

BUG: Luatex gets high unicode codepoints with an offset
by Sergio Callegari 12 May '21

12 May '21

Hi, please consider this sample code|:| ||||\documentclass{article} \usepackage{fontspec} \newfontface\MDI{Material Design Icons}[] \begin{document} Look at this character {\MDI \char"F1372}! \end{document} It is meant to work with the materialdesignicons-webfont.ttf font downloadable from https://materialdesignicons.com/ <https://materialdesignicons.com/> . The code works just fine with xelatex, but with lualatex it picks a wrong char (there seems to be an offset by 14). See also https://tex.stackexchange.com/questions/596610/how-to-use-luatex-with-large… . Seems a bug to me, certainly an inconsistency with xelatex. Any idea? Best, Sergio ||

2 1

Potential race condition in makefiles
by Dmitry Kalinkin 08 May '21

08 May '21

Hi, We are observing a following build failure: ../../../texk/web2c/luatexdir/luamd5/md5lib.c:197:10: fatal error: 'utilsha.h' file not found #include "utilsha.h" ^~~~~~~~~~~ 1 error generated. For the full log, see https://hydra.nixos.org/build/142527628/nixlog/2 Best regards, Dmitry

2 3

\protrusionboundary
by Robert 06 May '21

06 May '21

Hi, the command \protrusionboundary could potentially be very useful, but I'm not sure I understand how it's supposed to work. The manual gives the example (p.43): | \protrusionboundary1\llap{!\quad}«Who needs protrusion?» However, with the following: \input luaotfload.sty \parindent=0pt \protrudechars=2 \directlua{ fonts.protrusions.setups['test'] = { [0x00AB] = { 1, 0 } % left guillemet } } \font\x=[lmroman10-regular.otf]:protrusion=test; \x Who\par «Who\par \protrusionboundary1\llap{!\quad}«Who \bye the guillemet on the last line is not protruded as I would have expected. Or am I missing something? Secondly, the documentation says that \protrusionboundary will ignore the next/previous node (singular). What would be much more practical in real life, I think, is to have a command that would simply say, "consider the current point as left/right/both margin(s)", because more often than not, you'd find a succession of hboxes, penalties etc. (plural) that you'd want to skip. Would that be feasible? Best, -- Robert

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

dev-luatex May 2021