- dev-luatex - NTG Mailing Lists

Typos in the manual and in the source code
by Josef Friedrich 06 Feb '23

06 Feb '23

# Typo in the source code diff --git a/source/texk/web2c/luatexdir/luatex.c b/source/texk/web2c/luatexdir/luatex.c index 14426db6a..c11b0ca62 100644 --- a/source/texk/web2c/luatexdir/luatex.c +++ b/source/texk/web2c/luatexdir/luatex.c @@ -329,7 +329,7 @@ int shell_cmd_is_allowed(const char *cmd, char **safecmd, char **cmdname) free(buf); /* - Is *cmdname listed in a texmf.cnf vriable as shell_escape_commands = + Is *cmdname listed in a texmf.cnf variable as shell_escape_commands = foo,bar,... ? */ p = cmdlist; # Lua code example diff --git a/manual/luatex-tex.tex b/manual/luatex-tex.tex index a5e458088..9109a09db 100644 --- a/manual/luatex-tex.tex +++ b/manual/luatex-tex.tex @@ -1379,8 +1379,8 @@ tex.print(tex.romannumeral(123)) The first one returns the name only, the second one reports the size too. \startfunctioncall -tex.print(tex.fontname(tex.fontname)) -tex.print(tex.fontname(tex.fontidentidier)) +tex.print(tex.fontidentifier(1)) +tex.print(tex.fontname(1)) \stopfunctioncall \subsubsection{\type {sp}} # No longer there? 10.3.15.6 tex.getlinenumber and tex.setlinenumber diff --git a/manual/luatex-tex.tex b/manual/luatex-tex.tex index a5e458088..f88fe1bb9 100644 --- a/manual/luatex-tex.tex +++ b/manual/luatex-tex.tex @@ -1412,29 +1412,6 @@ following: \stopitem \stopitemize -\subsubsection{\type {tex.getlinenumber} and \type {tex.setlinenumber}} - -\libindex{getlinenumber} -\libindex{setlinenumber} - -You can mess with the current line number: - -\startfunctioncall -local n = tex.getlinenumber() -tex.setlinenumber(n+10) -\stopfunctioncall - -which can be shortcut to: - -\startfunctioncall -tex.setlinenumber(10,true) -\stopfunctioncall - -This might be handy when you have a callback that read numbers from a file and -combines them in one line (in which case an error message probably has to refer -to the original line). Interference with \TEX's internal handling of numbers is -of course possible. - \subsubsection{\type {error} and \type {show_context}} \topicindex{errors} @@ -2747,7 +2724,6 @@ The options match commandline arguments from \type {kpsewhich}: If \type {--output-directory} is specified and the value is a relative pathname, the file is searched first here and then in the standard tree. - \stopsubsection \startsubsection[title={\type {init_prog}}] # 14.2.7 get[from][dictionary|array|stream] -> 14.2.7 get[dictionary|array|stream] diff --git a/manual/luatex-backend.tex b/manual/luatex-backend.tex index 8d4c366c3..c4c646290 100644 --- a/manual/luatex-backend.tex +++ b/manual/luatex-backend.tex @@ -739,7 +739,7 @@ string is hex encoded. The second call returns the unencoded string. \stopsubsection -\startsubsection[title={\type {get[from][dictionary|array|stream]}}] +\startsubsection[title={\type {get[dictionary|array|stream]}}] \libindex {getdictionary} \libindex {getfromdictionary} \libindex {getarray} \libindex {getfromarray} # 14.2.8 [open|close|readfrom|whole|]stream -> 14.2.8 [open|close|readfrom|readwhole]stream diff --git a/manual/luatex-backend.tex b/manual/luatex-backend.tex index 8d4c366c3..062ec43ad 100644 --- a/manual/luatex-backend.tex +++ b/manual/luatex-backend.tex @@ -775,7 +775,7 @@ print(pdfe.open("foo.pdf").Pages[1]) \stopsubsection -\startsubsection[title={\type {[open|close|readfrom|whole|]stream}}] +\startsubsection[title={\type {[open|close|readfrom|readfromwhole]stream}}] \libindex {openstream} \libindex {closestream}

2 2

linkarea wrong in TRT context
by Ulrike Fischer 24 Jan '23

24 Jan '23

If there is a \textdir change in a paragraph *and* if a link breaks over two lines then then link area is wrong: \hsize=5cm \parskip=1em OK: {abc \textdir TRT \pdfextension startlink attr {/Border[0 0 1]} user{ /Subtype/Link/A<</S/URI/URI(blub)>> } x y y y z \pdfextension endlink abc } end Wrong: {abc \textdir TRT \pdfextension startlink attr {/Border[0 0 1]} user{ /Subtype/Link/A<</S/URI/URI(blub)>> } x y y y y y y y y y y y y y y y z \pdfextension endlink abc } end \pardir TRT \textdir TRT OK: \pdfextension startlink attr {/Border[0 0 1]} user{ /Subtype/Link/A<</S/URI/URI(blub)>> } x y y y y y y y y y y y y y y y z \pdfextension endlink end \bye (extracted from https://tex.stackexchange.com/q/672299/2388) -- Ulrike Fischer http://www.troubleshooting-tex.de/

2 1

duplicated /MediaBox entry if pageattr is used
by Ulrike Fischer 20 Jan '23

20 Jan '23

In pdftex "if the \pdfpageattr value contains the string /MediaBox, then pdfTEX omits outputting its own /MediaBox value". That means that the following produce a PDF with only one /MediaBox in the page dictionary: \pdfcompresslevel0 \pdfobjcompresslevel0 \pdfpageattr{/MediaBox [0 0 200 300]} abc \bye The same is not true for luatex: \pdfvariable compresslevel = 0 \pdfvariable objcompresslevel = 0 \pdfvariable pageattr{/MediaBox [0 0 200 300]} abc \bye leads to two entries (using pdf.setpageattributes gives the same): /MediaBox [ 0 0 595.276 841.89 ] /MediaBox [0 0 200 300] Would it be possible to copy the pdftex behaviour also in luatex? -- Ulrike Fischer http://www.troubleshooting-tex.de/

2 3

Function name mismatch between manual and C code: font.copyfont <-> font.getcopy ?
by Josef Friedrich 17 Jan '23

17 Jan '23

I think that there is a wrong function name documented in the manual. The lfontlib.c C file exports a getcopy function: https://gitlab.lisn.upsaclay.fr/texlive/luatex/-/blob/master/source/texk/we… diff --git a/manual/luatex-fonts.tex b/manual/luatex-fonts.tex index 136d20dd3..037d252ff 100644 --- a/manual/luatex-fonts.tex +++ b/manual/luatex-fonts.tex @@ -728,10 +728,10 @@ font.setfont(<number> n, <table> f) Note that at the moment, each access to the \type {font.fonts} or call to \type {font.getfont} creates a \LUA\ table for the whole font unless you cached it. -If you want a copy of the internal data you can use \type {font.copyfont}: +If you want a copy of the internal data you can use \type {font.getcopy}: \startfunctioncall -<table> f = font.copyfont(<number> n) +<table> f = font.getcopy(<number> n) \stopfunctioncall This one will return a table of the parameters as known to \TEX. These can be

2 1

Typo in the manual
by Josef Friedrich 17 Jan '23

17 Jan '23

diff --git a/manual/luatex-fonts.tex b/manual/luatex-fonts.tex index 136d20dd3..917147c55 100644 --- a/manual/luatex-fonts.tex +++ b/manual/luatex-fonts.tex @@ -788,7 +788,7 @@ Within reasonable bounds you can extend a font after it has been defined. Becaus some properties are best left unchanged this is limited to adding characters. \startfunctioncall -font.addcharacters(<number n>, <table> f) +font.addcharacters(<number> n, <table> f) \stopfunctioncall The table passed can have the fields \type {characters} which is a (sub)table

2 2

Using Harfbuzz with dvilualatex produces invalid font references
by Zameer Manji 16 Jan '23

16 Jan '23

Hello, I have run into a bug when using HarfBuzz and dvilualatex. When the following document is compiled with dvilualatex ``` \documentclass{minimal} \usepackage{fontspec} \setmainfont[Renderer = OpenType]{OpenSans-Regular.ttf } \begin{document} Hello \end{document} ``` The produced DVI file cannot be handled by dvipdfmx. Running dvipdfmx produces the following error: ``` dvipdfmx:fatal: Unable to find TFM file "[OpenSans-Regular.ttf]:mode=harf;shaper=ot;script=latn;language=dflt;+tlig;". ``` Removing '[Render = OpenType]' and running dvipdfmx on the resulting dvi file works fine. -- Zameer Manji

1 0

Typo in the LuaTeX manual: node.type(n)
by Josef Friedrich 15 Jan '23

15 Jan '23

I found a typo in the LuaTeX manual. It would be nice if this error could be corrected. I've attached a patch. I made this patch from the mirrored repository on Github (https://github.com/TeX-Live/luatex) Despite an intensive search I could not find the current development repository of LuaTeX. I read about an upcoming Git migration in the mail archive. Is there any progress? diff --git a/manual/luatex-nodes.tex b/manual/luatex-nodes.tex index d18006df0..a4ba7cfd7 100644 --- a/manual/luatex-nodes.tex +++ b/manual/luatex-nodes.tex @@ -1248,7 +1248,7 @@ This converts a single type name to its internal numeric representation. \libindex {type} \libindex {subtype} -In the argument is a number, then the next function converts an internal numeric +If the argument is a number, then the type function converts an internal numeric representation to an external string representation. Otherwise, it will return the string \type {node} if the object represents a node, and \type {nil} otherwise.

2 1

should there be a decode array in the SMask dictionary?
by Ulrike Fischer 30 Dec '22

30 Dec '22

If I run the following with pdftex I get a rather black square (checked in three pdf viewers). With luatex I get a rather light gray square, which looks imho wrong as color values between 0 and 0.2 should be dark. The png can be found here: https://i.stack.imgur.com/8JrYD.png \ifcsname directlua\endcsname \pdfvariable compresslevel 0 \pdfvariable objcompresslevel 0 \saveimageresource attr{/Decode [0 0.2 0 0.2 0 0.2]}{blue_square.png} \useimageresource\the\lastsavedimageresourceindex \else \pdfcompresslevel 0 \pdfobjcompresslevel 0 \pdfximage attr{/Decode [0 0.2 0 0.2 0 0.2]}{blue_square.png} \leavevmode\pdfrefximage \the\pdflastximage \fi \bye pdftex adds a transparency group which is missing in luatex, but it didn't change when I added that manually. The other difference between both engines is that pdftex adds the /Decode array only to the image object dictionary and not also to the Smask dictionary: With pdftex I get as image object dictionary << /Decode [0 0.2 0 0.2 0 0.2] /Type /XObject /Subtype /Image /Width 115 /Height 115 /BitsPerComponent 8 /ColorSpace /DeviceRGB /SMask 8 0 R /Length 39675 >> and as SMask dictionary << /Type /XObject /Subtype /Image /Width 115 /Height 115 /BitsPerComponent 8 /ColorSpace /DeviceGray /Length 13225 >> The image dictionary with luatex is identical but the SMask has also a /Decode array: << /Type /XObject /Subtype /Image /Decode [0 0.2 0 0.2 0 0.2] /Width 115 /Height 115 /BitsPerComponent 8 /ColorSpace /DeviceGray /Length 13225 >> If I disable the Decode array by replacing /Decode with /Dexode then the expected dark square appears. -- Ulrike Fischer http://www.troubleshooting-tex.de/

2 1

luaotfload strange message
by Fabrice Popineau 17 Dec '22

17 Dec '22

Hi everybody, I have this message showing up for some time now: luaotfload | db : Reload initiated (formats: otf,ttf,ttc); reason: Font "CambriaB.ttf" not found. every time I compile the same file. This message is quite recent (TeXLive 2022 ?). It is also strange that I need to state explicitly : \setmainfont{Cambria.otf}[ BoldFont=CambriaB.ttf, ItalicFont=CambriaI.ttf, BoldItalicFont=CambriaI.ttf, BoldItalicFeatures={RawFeature={embolden=5}} ] at the same time (see post https://tex.stackexchange.com/questions/657372/lualatex-cannot-use-bold-cam… ) Any idea what's going wrong with Cambria ? I am using TeXLive/Windows if that matters. Thanks for your help. -- Fabrice

2 1

Wrong tail in node.ligaturing
by Marcel Fabian Krüger 03 Dec '22

03 Dec '22

Hi, in LuaTeX node.ligaturing should return the head and the tail of the list after ligatures got applied. But in the case that the tail of the new list is a discretionary the current code returns the passed in tail instead, assuming that it didn't change. This breaks if the discretionary node wasn't the tail before the ligature pass:. Take for example \directlua{ local b = token.scan_list() local h = b.head local t = node.tail(h) local post_h, post_t = node.ligaturing(h, node.tail(t)) print(node.tail(post_h), post_t) }\hpack{a\discretionary{}{f}{f}f} \bye Here the `f`s in the discretionary form ligatures with the `f` after the discretionary, so after node.ligaturing the list if effectively `a\discretionary{}{ff}{ff}` and therefore `post_t` should point to the discretionary node. But as the output shows, post_t instead is a glyph node while node.tail(post_h) is the expected disc node. This is caused by `handle_lig_word` in luafont.c. `handle_lig_word` is used in `handle_ligaturing` as while (cur != null) { if (type(cur) == glyph_node || (type(cur) == boundary_node)) { cur = handle_lig_word(cur); } prev = cur; cur = vlink(cur); } so it is expected that handle_lig_word returns the last node already handled so that afterwards the loop can continue at vlink(cur). But if the handled segment ends with a discretionary `handle_lig_word` returns the node `after` the last already handled node instead. This is fine if the last node is a non glyph/non boundary node, but if the discretionary ends the segment passed to handle_ligaturing than this means that `handle_lig_word` returns null, therefore settings `prev` to `null` instead of tracking the tail. Also this relies on `vlink(null)` being null, causing issues if this ever gets corrupted (see my next mail for an example...). It can be fixed by making sure that handle_lig_word always returns the last handled node, e.g. using diff --git a/source/texk/web2c/luatexdir/font/luafont.c b/source/texk/web2c/luatexdir/font/luafont.c index 2e08facb1..c33037244 100644 --- a/source/texk/web2c/luatexdir/font/luafont.c +++ b/source/texk/web2c/luatexdir/font/luafont.c @@ -2242,6 +2242,7 @@ static halfword handle_lig_nest(halfword root, halfword cur) static halfword handle_lig_word(halfword cur) { halfword right = null; + halfword last = null; if (type(cur) == boundary_node) { halfword prev = alink(cur); halfword fwd = vlink(cur); @@ -2481,9 +2482,10 @@ static halfword handle_lig_word(halfword cur) } else { /*tex We have glyph nor disc. */ - return cur; + return last; } /*tex Goto the next node, where |\par| allows |vlink(cur)| to be NULL. */ + last = cur; cur = vlink(cur); } return cur; -- Best regards, Marcel

2 2