- dev-luatex - NTG Mailing Lists

Duplicated italic correction in do_delimiter
by Marcel Fabian Krüger 31 Jan '21

31 Jan '21

Hi, take the following document: \font\extend ntxexx at 10pt \textfont3=\extend \showboxdepth\maxdimen \showboxbreadth\maxdimen \setbox0=\hbox{$ \big) $} \showbox0 \bye It writes to the log: > \box0= \hbox(8.5+3.1125)x4.72997, direction TLT .\mathon .\hbox(8.5+3.1125)x4.72997, direction TLT ..\mathon ..\hbox(8.5+3.1125)x4.72997, direction TLT ...\hbox(0.56+10.665)x4.72997, shifted -7.55249, direction TLT ....\extend ^A ...\vbox(8.5+0.0)x0.0, direction TLT ...\hbox(0.0+0.0)x0.0, direction TLT ..\mathoff .\mathoff Particularly note the width 4.72997 of the hbox with the delimiter. If we look at the relevant part of the tfm file (in pl format), we find the dimensions of the glyph as (CHARACTER O 1 (CHARWD R 0.313) (CHARHT R 0.056) (CHARDP R 1.0665) (CHARIC R 0.08) (NEXTLARGER O 21) ) We would expect the width of the box to be 10pt*(CHARWD+CHARIC)=10pt*(0.313+0.08)=3.93pt. Instead we get 10pt*(CHARWD+2*CHARIC)=10pt*(0.313+2*0.08)=4.73pt~4.72997. The cause of this is in mlist.c, do_delimiter (around line 1652): b = char_box(f, c, att); if (!do_new_math(f)) { /*tex Italic gets added to width. */ width(b) += char_italic(f, c); } The char_box function already adds the italic correction to the box width if new math isn't used, therefore the additionally added char_italic leads to the duplicated value. This can be fixed by removing the if block: diff --git a/source/texk/web2c/luatexdir/tex/mlist.c b/source/texk/web2c/luatexdir/tex/mlist.c index c34dee488..e9df7b13f 100644 --- a/source/texk/web2c/luatexdir/tex/mlist.c +++ b/source/texk/web2c/luatexdir/tex/mlist.c @@ -1649,11 +1649,8 @@ static pointer do_delimiter(pointer q, pointer d, int s, scaled v, boolean flat, if (same != NULL && x == c) { *same = emas; } + /*tex italic gets added to width */ b = char_box(f, c, att); - if (!do_new_math(f)) { - /*tex Italic gets added to width. */ - width(b) += char_italic(f, c); - } if (delta != NULL) { /*tex This used to be (f, x). */ *delta = char_italic(f, c); -- Best regards, Marcel

3 2

LuaTeX: autokenring in math
by Petr Olsak 29 Jan '21

29 Jan '21

Hi LuaTeX developers, please, look at the issue https://github.com/latex3/luaotfload/issues/174 including my comment there. What is your opinion to this? Petr Olsak

1 0

linkarea is wrong if startlink is used in an \rlap
by Ulrike Fischer 14 Jan '21

14 Jan '21

In the following example the link area always starts at the begin of the \rlap (and so includes the yyyy) With pdftex the link area only surrounds the link text as expected X \rlap{yyyyyyy \ifx\pdfextension\undefined \pdfstartlink \else \pdfextension startlink \fi attr {/Border[0 0 1]} user{ /Subtype/Link% /A<<% /Type/Action% /S/URI% /URI(blub)% >>% } Linktext \ifx\pdfextension\undefined \pdfendlink \else \pdfextension endlink \fi } \bye -- Ulrike Fischer http://www.troubleshooting-tex.de/

3 2

keeping in sync with pdftex changes
by Ulrike Fischer 13 Jan '21

13 Jan '21

pdftex will in texlive 2021 change in two places 1. links where \pdfstartlink is in a different boxing level as \pdfendlink are no longer a fatal error but gives only a warning: x\hbox{\pdfstartlink attr {/Border[0 0 1]} user{ /Subtype/Link% /A<<% /Type/Action% /S/URI% /URI(blkub)% >>% } Linktext} \pdfendlink \bye pdfTeX warning: \pdfendlink ended up in different nesting level than \pdfstartl ink 2. There are two new primitives \pdfrunninglinkoff & \pdfrunninglinkon which allow to interrupt a running link for example in the header or footer. Would it be possible to get this changes into luatex too? -- Ulrike Fischer http://www.troubleshooting-tex.de/

4 14

luatex segfault with huge romannumeral overfull
by Hironobu Yamashita 25 Nov '20

25 Nov '20

Hi, I happened to find that luatex and luahbtex crash: $ luatex \\romannumeral2000000000\\end This is LuaTeX, Version 1.13.0 (TeX Live 2021/dev) restricted system commands enabled. Segmentation fault: 11 (I'm using self-build from current TL svn.) Best, Hironobu

2 1

Hyphenation issue regarding frozen glyph nodes
by Marcel Fabian Krüger 09 Nov '20

09 Nov '20

Hi, as recently discussed on the luatex list there is an issue regarding hyphenation ehn a frozen glyph appears next to an explicit hyphenation character. E.g. \setbox0\hbox{X} X-\unhbox0 \bye triggers an assertion error. I noticed that with the latest experimental code a TeX error is triggered instead but IMO this should not be an error. Therefore I suggest to fix this by treating glyph nodes failing is_simple_character just like non-glyph nodes, e.g. with --- source/texk/web2c/luatexdir/lang/texlang.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/texk/web2c/luatexdir/lang/texlang.c b/source/texk/web2c/luatexdir/lang/texlang.c index 48a242fa0..e7635903a 100644 --- a/source/texk/web2c/luatexdir/lang/texlang.c +++ b/source/texk/web2c/luatexdir/lang/texlang.c @@ -1049,7 +1049,7 @@ void hnj_hyphenation(halfword head, halfword tail) if (explicit_hyphen == true) { /*tex we are not at the start, so we only need to look ahead */ halfword t = vlink(r) ; - if ((automatic_hyphen_mode_par == 0 || automatic_hyphen_mode_par == 1) && (t != null) && ((type(t) == glyph_node) && (character(t) != ex_hyphen_char_par))) { + if ((automatic_hyphen_mode_par == 0 || automatic_hyphen_mode_par == 1) && (t != null) && ((type(t) == glyph_node) && is_simple_character(t) && (character(t) != ex_hyphen_char_par))) { /*tex we have a word already but the next character may not be a hyphen too */ r = compound_word_break(r, char_lang(r)); if (compound_hyphen) { @@ -1063,7 +1063,7 @@ void hnj_hyphenation(halfword head, halfword tail) } } else { /*tex we jump over the sequence of hyphens */ - while ((t != null) && (type(t) == glyph_node) && (character(t) == ex_hyphen_char_par)) { + while ((t != null) && (type(t) == glyph_node) && is_simple_character(t) && (character(t) == ex_hyphen_char_par)) { r = t ; t = vlink(r) ; } -- 2.29.2 Best regards, Marcel

2 1

Using \global with \toksapp
by Esger Renkema 17 Jul '20

17 Jul '20

Dear list, Trying to use \global with \toksapp, e.g. when saying »\global\toksapp0{}«, luatex throws a fatal error: --------------------------------------------------------- This is LuaTeX, Version 1.13.0 (TeX Live 2021/dev) restricted system commands enabled. **! This can't happen (prefix). <*> \global\toksapp 0{} ! ==> Fatal error occurred, no output PDF file produced! Transcript written on texput.log. --------------------------------------------------------- While I know \gtoksapp exists, this seems surprising nevertheless; the error message seems to agree. Is this indeed unintended? Best wishes, Esger Renkema

1 0

Flaw in find_math_kern()
by David Jones 25 Jun '20

25 Jun '20

I recently filed a bug report on the XeTeX repo about the kerning of sub- and superscripts in OpenType fonts: https://sourceforge.net/p/xetex/bugs/175/ luaTeX's find_math_kern() has many of the same flaws. Cheers, David. P.S. I don't think the related bug https://sourceforge.net/p/xetex/bugs/173/ is relevant here because luaTeX's analyze_script() already does essentially the same thing (I haven't compared the two implementations in detail). In fact, analyze_script() does more, since it also handles the sub_box case. ________________________________ David Jones Publications Technical Specialist +1 401.455.4000 (t) [https://www.ams.org/images/ams-logo-270x72.jpg] 201 Charles Street | Providence, RI 02904-2213 USA [https://www.ams.org/images/url.jpg]<https://www.ams.org> | [https://www.ams.org/images/Facebook-icon.jpg] <https://www.facebook.com/amermathsoc> [https://www.ams.org/images/instagram-icon.jpg] <https://www.instagram.com/amermathsoc/> [https://www.ams.org/images/linkedin-icon.jpg] <https://www.linkedin.com/company/51001/> [https://www.ams.org/images/twitter-icon.jpg] <https://twitter.com/amermathsoc> [https://www.ams.org/images/youtube-icon.jpg] <https://www.youtube.com/user/amermathsoc> We appreciate your patience during the Coronavirus Emergency as staff is working remotely.

1 0

warning when trying to include pdf 2.0
by Ulrike Fischer 25 May '20

25 May '20

When I try to include a pdf 2.0 image in a pdf set to 2.0 I get a warning: PDF inclusion: found PDF version '2.0', but at most version '2.0' allowed Example: \pdfvariable compresslevel=0 \pdfvariable majorversion=2 \pdfvariable minorversion=0 \saveimageresource {version20.pdf} abc \bye The warning disappears when I set \pdfvariable minorversion=2, so it looks as if the code would set the minor version of the included pdf to 2 instead of 0. -- Ulrike Fischer http://www.troubleshooting-tex.de/

2 1

lastnodetype=7 ?
by Robert 27 Apr '20

27 Apr '20

Hi, \lastnodetype doesn't give the expected result for ligature nodes (7), registering them as char nodes (0) instead. This happens for both legacy and opentype fonts: \font\x=cmr12 \x \setbox0\hbox{fl} \unhbox0 \the\lastnodetype \ifdefined\directlua \input luaotfload.sty \font\x=[lmroman12-regular.otf]:script=latn;+trep;+tlig;%mode=base; \x \setbox0\hbox{fl} \unhbox0 \the\lastnodetype \fi \bye It seems to work fine with the other node types (but I haven't tested all of them ...). Best, -- Robert

2 1