dev-luatex July 2019

dev-luatex@ntg.nl

4 participants
7 discussions

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.08.0 announcement
by luigi scarso 28 Oct '19

28 Oct '19

============================================================== LuaTeX 1.08 2018-08-28 ============================================================== (1) This release is a prelude to 1.10, the next stable iteration of LuaTeX after version 1.00. (2) Lua 5.3 is now considered to be default and we might use 5.4 in version 1.10. There are no real functional changed expected. You still need to rename the binary for 5.3! (3) Binary mode is no longer available in MPlib but it is still available in stand alone MetaPost. This simplifies compilation and reduces dependencies. (4) The dependency on Poppler for pdf image inclusion has been removed. We now use a small dedicated library written by Pawel Jakowski. We no longer need c++ compilers. We're in the process of making it behave well on all platforms. It has been tested on intel platforms. (5) We know that there can be some (alignment) issues with the arm platform but these are looked into. Therefore, later this year we will release 1.09. Version 1.10 is planned for TeXlive. We hope that ffi works ok on intel and arm platforms at that point. (6) There have been some extensions to the Lua libraries and some callbacks have been added. Also, a few new primitives have been introduced. The documentation mentions the stable extensions. (7) There are the usual bug fixes and cleanups but there have been no real fundamental changes in the API. The LuaTeX team

2 5

Re: [Dev-luatex] Embedding minimally used TTF fonts
by Marcel Krüger 23 Jul '19

23 Jul '19

On 23 July 2019 16:21:18 CEST, luigi scarso <luigi.scarso(a)gmail.com> wrote: >On Tue, Jul 23, 2019 at 1:03 PM Marcel Fabian Krüger <tex(a)2krueger.de> >wrote: > >> Hi, >> >> whenever LuaTeX loads a TTF font but only uses a single glyph, >> which happens to be the notdef glyph (GID=0), LuaTeX complains about >> >> (type 2): there are no glyphs in the subset >> >> Of course this isn't true, because the notdef *is* in the subset. >> >> This happens because LuaTeX always includes the notdef glyph, so it >is >> never counted. The problem can be fixed by explicitly testing for >this >> case. >> >> >Do you have an example ? Of course: \starttext \font\test=logix.ttf\test \char"F0000 \stoptext See https://github.com/u-fischer/luaotfload/issues/73 for some context.

2 2

Embedding minimally used TTF fonts
by Marcel Fabian Krüger 23 Jul '19

23 Jul '19

Hi, whenever LuaTeX loads a TTF font but only uses a single glyph, which happens to be the notdef glyph (GID=0), LuaTeX complains about (type 2): there are no glyphs in the subset Of course this isn't true, because the notdef *is* in the subset. This happens because LuaTeX always includes the notdef glyph, so it is never counted. The problem can be fixed by explicitly testing for this case. Best regards, Marcel Krueger diff --git a/source/texk/web2c/luatexdir/font/writetype2.c b/source/texk/web2c/luatexdir/font/writetype2.c index 49193579b..0f889f707 100644 --- a/source/texk/web2c/luatexdir/font/writetype2.c +++ b/source/texk/web2c/luatexdir/font/writetype2.c @@ -289,7 +289,7 @@ boolean make_tt_subset(PDF pdf, fd_entry * fd, unsigned char *buff, int buflen) num_glyphs++; } - if (num_glyphs == 1) { + if (num_glyphs == 1 && used_chars[0] == 0) { normal_error("type 2","there are no glyphs in the subset"); } if (tt_build_tables(sfont, glyphs, fd) < 0) {

1 0

linebreak_filter
by Marcel Fabian Krüger 20 Jul '19

20 Jul '19

Hi everyone, in current LuaTeX versions, the result of `linebreak` filter is ignored and instead it is always treated as if no node has been returned (so the internal linebreak algorithm is applied). A minimal example: \directlua{ callback.register("linebreak_filter", function(nodes) return node.hpack(nodes) end) } Some very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very long paragraph. \bye You would expect the whole paragraph to be set in a single line, but normal paragraph breaking is applies instead. This is caused by a change in revision 6686 from Mar 29 2018 "experimental) possible fix for for lua stack issue + consistent error handling (HH)". There in the function lua_linebreak_callback, the change return ret; } + lua_settop(Luas, s_top); p = lua_touserdata(Luas, -1); if (p != NULL) { a = nodelist_from_lua(Luas); try_couple_nodes(*new_head,a); ret = 1; } - lua_settop(Luas, s_top); return ret; has been applied. I am not sure what kind of stack issue this was supposed to fix, but as a side effect this moves the check for the node return value after `lua_settop`, so the return value is already removed from the stack when the test is done. So it is ignored. Best regards, Marcel Krüger

2 3

luatex and harfbuzz 2.5.1
by luigi scarso 08 Jul '19

08 Jul '19

In experimental there is now luatex 1.11.0 with harfbuzz 2.5.1 It follows from the development of harftex by K. Hosny. Please note that the code is 1) in experimental 2) marked as work in progress so it can stay as is, it can be changed , it can be removed completely. We have relaxed the constrain "only C" so a recent C++ is required; but we keep the contrain on the size the must be "small" --- the current size of the binary is around 8M so still good. Feedbacks are welcome: it would be nice to have it in texlive 2020 modulo that constrains are satisfied. -- luigi

4 7

luatex 1.11: bfchar entry empty in mode=harf
by Ulrike Fischer 01 Jul '19

01 Jul '19

When I load a font in harf mode the bfchar entry is empty: \pdfvariable compresslevel0 \pdfvariable objcompresslevel0 \documentclass{article} \usepackage{harfload} %is actually in my format ... \begin{document} \font\test={texgyreheros:mode=harf;} abcäüö \end{document} gives in the pdf /CMapName /TeX-Identity-GXAFXV-LMRoman10-Regular def /CMapType 2 def 1 begincodespacerange <0000> <FFFF> endcodespacerange 0 beginbfrange endbfrange 0 beginbfchar endbfchar With harftex or an older luatex I get: 1 beginbfchar <0052> <0031> endbfchar What's going on here? -- Ulrike Fischer https://www.troubleshooting-tex.de/

3 8

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

dev-luatex July 2019