- dev-luatex - Mailing Lists

depth of glyph nodes with y_displacement<0
by Marcel Fabian Krüger 13 Mar '20

13 Mar '20

Hi, I found a curiosity in LuaTeX's treatment of `y_displacement` in glyph nodes: Take the following ConTeXt example: \usetypescript[pagella] \setupbodyfont[pagella,12pt] \starttext f\char776\char776\char776\char807\char807\char807\vrule \stoptext (See https://github.com/latex3/luaotfload/issues/134 for a more practical case where this leads to issues) Here the \vrule shows that the marks attached at the top get their y_displacement added to their height, while for the marks added at the bottom the additional depth is ignored. (The first \char807 is still covered by the rule because that is the natural height of this glyph) This is explicitly done in texnodes.c: For glyph_height, the displacement is always added. For glyph_depth, the displacement is only added if it is positive: scaled glyph_height(halfword p) { scaled w = char_height(font(p), character(p)) + y_displace(p); if (w < 0) w = 0; return w; } scaled glyph_depth(halfword p) { scaled w = char_depth(font(p), character(p)); if (y_displace(p) > 0) w = w - y_displace(p); if (w < 0) w = 0; return w; } This seems inconsistant. Is there a reason why this would be required or could it be changed to handle height and depth consistently? Best regards, Marcel

2 5

append_to_vlist with single return value broken
by Marcel Fabian Krüger 07 Mar '20

07 Mar '20

Hi, according to the documentation for `append_to_vlist_filter`: > The prevdepth is also optional so it should be allowed to only return a box in which case the prevdepth value shouldn't change. But if we actually try this: \directlua{ callback.register("append_to_vlist_filter", function(b) return b end) } abc \bye LuaTeX answers with warning (pdf backend): no pages of output. because it discards all boxes. This is caused by a bug in luanode.c, lua_appendtovlist_callback: The callback is called with lua_pcall(Luas, 4, 2, 0). Then LuaTeX tries to determine if one or two values have been returned by looking at the type of slot -1: If this is a number, the second return value have been a number and it is evaluated as new prevdepth. Otherwise else if (lua_type(Luas, -1) != LUA_TNIL) { p = check_isnode(Luas, -1); *result = *p; } is evaluated to scan for a single return value which is a node. But because lua_pcall(Luas, 4, 2, 0) explicitly requested two return values, a callback with one return values would result in a stack where the one return value is followed by `nil`. Therefore this `if` block is not entered. The problem can be fixed by always looking at stack slot -2 for the returned node: source/texk/web2c/luatexdir/lua/luanode.c | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/source/texk/web2c/luatexdir/lua/luanode.c b/source/texk/web2c/luatexdir/lua/luanode.c index a0c97e37d..d4baab96d 100644 --- a/source/texk/web2c/luatexdir/lua/luanode.c +++ b/source/texk/web2c/luatexdir/lua/luanode.c @@ -183,12 +183,9 @@ int lua_appendtovlist_callback(halfword box, int location, halfword prev_depth, if (lua_type(Luas,-1) == LUA_TNUMBER) { *next_depth = lua_roundnumber(Luas,-1); *prev_set = true; - if (lua_type(Luas, -2) != LUA_TNIL) { - p = check_isnode(Luas, -2); - *result = *p; - } - } else if (lua_type(Luas, -1) != LUA_TNIL) { - p = check_isnode(Luas, -1); + } + if (lua_type(Luas, -2) != LUA_TNIL) { + p = check_isnode(Luas, -2); *result = *p; } return 1; -- Best regards, Marcel

3 3

Potential bug with kerning in math mode
by Matthias Nagel 07 Mar '20

07 Mar '20

Dear all, as I am unsure what is the officially correct way to submit a potential bug, I post it here and would like to draw your attention to this post, because I do not now of the tracker is still in use. http://tracker.luatex.org/view.php?id=1019 My apologies, if this is a double posting. Also, I already have posted this problem to the Libertinus project as I initially thought this would be a bug in the font, but the maintainer of Libertinus said it is an issue with LuaTex. Bests, M.N.

3 5

os.setenv()
by Reinhard Kotucha 22 Feb '20

22 Feb '20

Hi, I just tried this with texlua 1.10.0: -------------------------------------------- local function time_of_day (TZ) os.setenv('TZ', TZ) local time = os.gettimeofday() print(os.date('%c', math.floor(time))) end time_of_day ('America/New_York') time_of_day ('Europe/Paris') time_of_day ('Asia/Tokyo') -------------------------------------------- It seems that os.setenv() is only executed once and all results are in Eastern Standard Time: Fri Feb 21 16:37:13 2020 Fri Feb 21 16:37:13 2020 Fri Feb 21 16:37:13 2020 When I call "time_of_day ('Asia/Tokyo')" first I get Sat Feb 22 06:39:46 2020 Sat Feb 22 06:39:46 2020 Sat Feb 22 06:39:46 2020 Is it possible to fix this behavior? Regards, Reinhard -- ------------------------------------------------------------------ Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ------------------------------------------------------------------

2 3

Some legacy fonts cause "invalid list tail, probably missing glue"
by Daniel Benjamin Miller 20 Feb '20

20 Feb '20

There is an issue with lualatex which comes about when using a document such as this (based on a discussion here https://tex.stackexchange.com/questions/525898/combining-french-and-greek-b…) Try running lualatex on the following document, and an error will be returned. This seems to apply for all fonts whose packages were generated by autoinst (step is just an example). \documentclass[12pt]{article} \usepackage[utf8]{luainputenc}\usepackage[LGR,T1]{fontenc}\input{lgrenc.dfu} \usepackage{step} \usepackage[greek.ancient,main=french]{babel} \title{Ça marche?} %\date{} \author{me} \begin{document} \maketitle un, deux, trois \foreignlanguage{greek}{ἀγαγεῖν} \end{document} According to Marcel Krüger, this is related to an issue which was reported over a year ago: https://mailman.ntg.nl/pipermail/dev-luatex/2018-November/006138.html.

3 7

Disappearing quoteleft in luatex
by Norbert Preining 07 Feb '20

07 Feb '20

Dear all, I see a strange thing happening with the following document all with uptodate TeX Live: \documentclass{article} \usepackage{fontspec} \setmainfont{Gaultier} \begin{document} Hello `World' \end{document} xelatex: ok lualatex: quoteleft character is missing lualatex-dev with [RawFeature={mode=harf;}]: ok So it seems that the lualatex font loader seems to be broken here. The character is present in the font 325 (0x145) U+2018 "quoteleft" LEFT SINGLE QUOTATION MARK and separate from the quoteright. Any suggestions how to fix these kind of errors? Best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

2 2

Updates for (lua)HarfBuzz
by Marcel Fabian Krüger 25 Jan '20

25 Jan '20

Hello, would it be possible to pull a new version of luaharfbuzz in before TeXLive 2020 is frozen? There hasn't been an official release, but there are some new interfaces which would be very useful for luaotfload. There are also at least two bugs in HarfBuzz affecting luaotfload for which the fixes are in the repo but not yet released, but I guess the HarfBuzz version is controlled by the TeXLive team? Best regards, Marcel

3 4

Request for bugfix - rule nodes (subtypes: 1 = box, 2 = image, 3 = empty, 4 = user) in DVI mode
by Sigitas Tolusis 24 Jan '20

24 Jan '20

Three things to be fixed for the rule nodes with subtypes 1 to 4 in DVi mode. (Function dvi_place_rule from dvigen.c file) void dvi_place_rule(PDF pdf, halfword q, scaledpos size) { synch_dvi_with_pos(pdf->posstruct->pos); if ((subtype(q) >= box_rule) && (subtype(q) <= user_rule)) { /*tex place nothing, only take space */ if (textdir_is_L(pdf->posstruct->dir)) dvi.h += size.h; } else { /*tex normal_rule or >= 100 being a leader rule */ if (textdir_is_L(pdf->posstruct->dir)) { /*tex movement optimization for |dir_*L*| */ dvi_out(set_rule); dvi.h += size.h; } else dvi_out(put_rule); } dvi_four(size.v); dvi_four(size.h); } Problem 1. Bad dvi file due the arguments output without dvi command (misplaced the two last lines in the code). Possible fix: void dvi_place_rule(PDF pdf, halfword q, scaledpos size) { synch_dvi_with_pos(pdf->posstruct->pos); if ((subtype(q) >= box_rule) && (subtype(q) <= user_rule)) { /*tex place nothing, only take space */ if (textdir_is_L(pdf->posstruct->dir)) dvi.h += size.h; } else { /*tex normal_rule or >= 100 being a leader rule */ if (textdir_is_L(pdf->posstruct->dir)) { /*tex movement optimization for |dir_*L*| */ dvi_out(set_rule); dvi.h += size.h; } else dvi_out(put_rule); dvi_four(size.v); dvi_four(size.h); } } Problem 2. Not reserved space for the rule in the output. Possible fix: void dvi_place_rule(PDF pdf, halfword q, scaledpos size) { synch_dvi_with_pos(pdf->posstruct->pos); if ((subtype(q) >= box_rule) && (subtype(q) <= user_rule)) { /*tex place nothing, only take space */ if (textdir_is_L(pdf->posstruct->dir)) dvi.h += size.h; movement(size.h, right1); } else { /*tex normal_rule or >= 100 being a leader rule */ if (textdir_is_L(pdf->posstruct->dir)) { /*tex movement optimization for |dir_*L*| */ dvi_out(set_rule); dvi.h += size.h; } else dvi_out(put_rule); dvi_four(size.v); dvi_four(size.h); } } Problem 3. Broken consistency with PDF mode as process_rule callback is missing in DVI mode. Possible fix: void dvi_place_rule(PDF pdf, halfword q, scaledpos size, int callback_id) { synch_dvi_with_pos(pdf->posstruct->pos); if ((subtype(q) >= box_rule) && (subtype(q) <= user_rule)) { /*tex place nothing, only take space */ if (textdir_is_L(pdf->posstruct->dir)) dvi.h += size.h; if (subtype(q) == user_rule && callback_id != 0) { run_callback(callback_id, “Ndd->”, q, size.h, size.v); } movement(size.h, right1); } else { /*tex normal_rule or >= 100 being a leader rule */ if (textdir_is_L(pdf->posstruct->dir)) { /*tex movement optimization for |dir_*L*| */ dvi_out(set_rule); dvi.h += size.h; } else dvi_out(put_rule); dvi_four(size.v); dvi_four(size.h); } } and fix in dvigen.h < extern void dvi_place_rule(PDF pdf, halfword q, scaledpos size); > extern void dvi_place_rule(PDF pdf, halfword q, scaledpos size, int callback_id); Regards, Sigitas P.S. Some point for the discussion. For the wider usabillity maybe the rules with zero dimensions (width, height+depth) can be allowed in the output.

2 1

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