- dev-luatex - Mailing Lists

Dropped kerning around automatic hyphens
by Marcel Fabian Krüger 03 Dec '22

03 Dec '22

Hi, currently LuaTeX does not insert kerning between hyphens and characters before discretionary hyphens if the hyphen was inserted automatically. Take for example (here `a` is used as hyphenation character to simulate a font where kerning with the hyphen is mmre common than in cmr): \showboxdepth=\maxdimen \showboxbreadth=\maxdimen \tracingonline=1 \lefthyphenmin1 \righthyphenmin1 \hyphenation{V-b} \prehyphenchar=`a \setbox0=\vbox{Vb} \showbox0 \bye This results in [...] ..\tenrm V ..\discretionary (penalty 50) ...< \tenrm a ..\tenrm b [...] with no kern between the `V` and the `a`. If the hyphenation point is inserted manually by using \setbox0=\vbox{V\-b} instead the problem disappears and we get the expected [...] ..\tenrm V ..\discretionary (penalty 50) ...< \kern-0.83334 (font) ...< \tenrm a ..\tenrm b [...] Additionally the broken version writes the dropped kern node to vlink(null) breaking any code which relies on vlink(null) being null (see e.g. my previous mail). The issue is that `add_kern_before` in luafont.c relies on alink of the right glyph being valid. Since the right glyph here is the "hyphen" glyph in a discretionary this depends on what `alink` for the beginning of a discretionary list is. Currently this is inconsistent. When set through `set_disc_field` then the `alink` is explicitly set to null to avoid exposing the temporary "nodes" in discretionaries to Lua code. his triggers the bug since the kern gets added after null instead of before the right glyph. If the discretionary gets inserted through a discretionary_cmd by append_discretionary in maincontrol.c then the alink gets explicitly set to these pseudo nodes instead avoiding the issue. It doesn't make much sense to handle this inconsistently this is likely and internal nodes are already exposed in other places, so IMO the best solution is to alink to these nodes in set_disc_field too, e.g. with diff --git a/source/texk/web2c/luatexdir/lang/texlang.c b/source/texk/web2c/luatexdir/lang/texlang.c index a0d067251..3cbbdd3b4 100644 --- a/source/texk/web2c/luatexdir/lang/texlang.c +++ b/source/texk/web2c/luatexdir/lang/texlang.c @@ -470,12 +470,7 @@ static halfword compound_word_break(halfword t, int clang) void set_disc_field(halfword f, halfword t) { if (t != null) { - /*tex - No |couple_nodes(f, t);| as we can better not expose |f| as |prev| - pointer. - */ - vlink(f) = t ; - alink(t) = null ; + couple_nodes(f, t); tlink(f) = tail_of_list(t); } else { vlink(f) = null; -- Best, Marcel

2 1

Re: [Dev-luatex] \Udelcodenum doesn't work properly
by Hans Hagen 18 Nov '22

18 Nov '22

On 11/18/2022 12:25 PM, Petr Olsak wrote: > Sorry, > > I need to set delcodes to Unicode fonts and read them. LuaTeX manual > says that > > ----- > > The following new primitives are compatible with XƎTEX: > > ... > > \Udelcode > > \Udelcodenum > > ----- > > and XeTeX manual says that \Udelcode <charnum>=<family><slot> can save > delcode. and \Udelcodenum can read or save packed <family>/<slot> data > (the packed format isn't specified, but it doesn't matter). I am using > \Udelcode for setting delcode data. I don't know nothing else how to do > this. Now, I need to read saved delcode data using \Udelcodenum for > debugging purposes. Is there another way for saving and reading it? I am > talking only about Unicode fonts, i.e. there is only single pair > <family><slot>, no two pairs like in the classical \delcode. \def\theUdelcodesmallfam {\directlua{tex.print(tex.getdelcode(token.scan_int())[1])}} \def\theUdelcodelargefam {\directlua{tex.print(tex.getdelcode(token.scan_int())[3])}} \def\theUdelcodesmallchar {\directlua{tex.print(tex.getdelcode(token.scan_int())[2])}} \def\theUdelcodelargechar {\directlua{tex.print(tex.getdelcode(token.scan_int())[4])}} \theUdelcodesmallfam \la\ \theUdelcodelargefam \la\ \theUdelcodesmallchar\la\ \theUdelcodelargechar\la\ (as you can also set them there's actually always two pairs) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

1 0

\Udelcodenum doesn't work properly
by Petr Olsak 18 Nov '22

18 Nov '22

Hello The XeTeX manual says that \Udelcodenum sets or return packet information about family/slot of the \Udelcode data. It seems that it doesn't work in LuaTeX: \chardef\lx="027E8 \Udelcode\lx=1 "027E8 \the\Udelcodenum\lx % prints 42893312, i.e. "28E8000 \Udelcodenum\lx=\Udelcodenum\lx \the\Udelcodenum\lx % prints -381681664 \bye The slot code "027E8 is mixed with 01 family and \Udelocodenum returns "28E8000. Of course, if I set new Udelcode data using \Udelcodenum\lx=\Udelcodenum\lx then I get totally bad result. On the other hand, XeTeX runing on the same testing file prints in both cases 1075849192, i.e "402027E8. The slot code "027E8 isn't mixed with the family number. Petr Olsak

2 1

\intop without \nolimits gives bas spacing
by Petr Olsak 17 Nov '22

17 Nov '22

Hello suppose following testing file: ------------------- CM, intop+nolimits: $\intop\nolimits_0^1$ CM, intop directly: $\intop_0^1$ \ifx\directlua\undefined \else \input luafonts \fi \font\fA=[latinmodern-math]:mode=base;script=math;ssty=0; \font\fB=[latinmodern-math]:mode=base;script=math;ssty=1; at7pt \Umathchardef\intop="1"00"00222B \textfont0=\fA \scriptfont0=\fB LM, intop+nolimits $\intop\nolimits_0^1$ LM, intop directly $\intop_0^1$ \bye ------------------- The first two output lines print integral via classical PlainTeX setting with Coputer Modern fonts. We can see that there is no difference between \intop without \nolimits and with \nolimits. The following two output lines shows LatinModern-math Unicode font. First prints \intop with \nolimits, the result is with somewhat tightly spacing but it is not our problem. This is due to suboptimal font parameters. But the last line prints \intop without \nolimits and there is significantly difference: big space after \intop before limits. IMHO, it is a bug in LuaTeX. If we run the same testing file via XeTeX then there is no difference between third and last line of output. Petr Olsak

2 2

letter spacing in display math
by blumens＠fi.muni.cz 24 Sep '22

24 Sep '22

Hello, using fonts with additional letter spacing does not seem to work in display formulae. (Not sure whether it's a bug in luatex or whether I should report it to luaotfload instead.) Example (LuaHBTeX, Version 1.15.0): \documentclass{minimal} \begin{document} \font\f="DejaVuSerif-Italic:letterspace=20.0" at 10pt \f % these work as expected \hfill abcdefxyz\hfill\hbox{} \hfill$\textfont1=\f abcdefxyz$\hfill\hbox{} \hfill$\textfont1=\f\displaystyle abcdefxyz$\hfill\hbox{} % these don't $$\textfont1=\f abcdefxyz$$ $$\textfont1=\f\textstyle abcdefxyz$$ \end{document} Am I missing something? Achim

2 2

\Uchar errors with "FFFD
by Ulrike Fischer 16 Aug '22

16 Aug '22

\Uchar"FFFD \bye errors with ! String contains an invalid utf-8 sequence. l.93 \Uchar"FFFD (^^^^fffd works) -- Ulrike Fischer http://www.troubleshooting-tex.de/

3 6

Fwd: Importing .tex files using \directlua to navigate files and folders
by Hans Hagen 12 Aug '22

12 Aug '22

-------- Forwarded Message -------- Subject: Re: [Dev-luatex] Importing .tex files using \directlua to navigate files and folders Date: Fri, 12 Aug 2022 09:44:24 +0200 From: Hans Hagen <j.hagen(a)xs4all.nl> To: Taco Hoekwater <taco(a)bittext.nl> On 8/12/2022 9:30 AM, Taco Hoekwater wrote: > > >> On 11 Aug 2022, at 14:08, paolo de luca <teugon(a)gmail.com> wrote: >> >> Hi all, >> >> I've been trying to import all tex files and inside a given folder, the issue I'm facing is that my lua call is not able to navigate folders: it only works for files. >> It's worth mentioning that compilation successfully completes as the document is created, but I have no errors explaining me why it's not working as intended. >> I've also opened a question on tex.stackexchange. >> >> would you mind having a look at it ? >> >> https://tex.stackexchange.com/questions/653499/understanding-implicit-error… > > > See comment on SX. Don't 'return' the nested call, and it works just fine. > > function inputAll(dir) > for content in lfs.dir(dir) do > if ("." ~= content) and (".." ~= content) then > fullpath = dir .."/".. content > contentType = lfs.attributes(fullpath, "mode") > if isTexFile(content, contentType) then > tex.sprint(" > \\ > input{" .. fullpath .. "}") > elseif ("directory" == contentType) then > -- return > inputAll(fullpath) > end > end > end > end yes, the return is quitter, but even then one can run into some nested directory handle issue especially when one does things inside that loop on one of the directories (maybe the \input results in new files there or files get deleted and or ..) and one wants to have a predictable sorted list i assume so i tend to collect first Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Importing .tex files using \directlua to navigate files and folders
by paolo de luca 12 Aug '22

12 Aug '22

Hi all, I've been trying to import all tex files and inside a given folder, the issue I'm facing is that my lua call is not able to navigate folders: it only works for files. It's worth mentioning that compilation successfully completes as the document is created, but I have no errors explaining me why it's not working as intended. I've also opened a question on tex.stackexchange. would you mind having a look at it ? https://tex.stackexchange.com/questions/653499/understanding-implicit-error… Thanks in advance for your time

3 2

Cannot load .tex when both --output-directory and \input are present
by Ikumi Keita 31 Jul '22

31 Jul '22

Hello LuaTeX developers, Let me explain an issue I encountered. I'd like to know how to circumvent it. In latex tools bundle, there is a file ".tex", which has a file name with extension only. Its path is /usr/local/texlive/2022/texmf-dist/tex/latex/tools/.tex typically. This example loads that ".tex" successfully: lualatex --jobname=abcd '\input\relax' '\input' sample2e Here '\input\relax' actually directs to load ".tex". The console log is: ---------------------------------------------------------------------- This is LuaHBTeX, Version 1.15.0 (TeX Live 2022) restricted system commands enabled. LaTeX2e <2021-11-15> patch level 1 L3 programming layer <2022-02-24> (/usr/local/texlive/2022/texmf-dist/tex/latex/tools/.tex File ignored) (/usr/local/texlive/2022/texmf-dist/tex/latex/base/sample2e.tex ... ---------------------------------------------------------------------- This is OK. Next, make a directory "build" for output directory by mkdir build . Then this command stalls with the following console output: lualatex --jobname=abcd --output-directory=build/ '\input\relax' '\input' sample2e ---------------------------------------------------------------------- This is LuaHBTeX, Version 1.15.0 (TeX Live 2022) restricted system commands enabled. LaTeX2e <2021-11-15> patch level 1 L3 programming layer <2022-02-24> ! I can't find file `'. <to be read again> \let <*> \input\relax \input sample2e (Press Enter to retry, or Control-D to exit) Please type another input file name: ---------------------------------------------------------------------- This affects preview-latex: https://lists.gnu.org/r/auctex/2022-06/msg00020.html Is this a supposed behavior of lua(la)tex? If so, is there any workaround to load ".tex" when both --output-directory and \input are present? [Supplementary information with respect to this issue] (1) pdflatex doesn't have this issue: pdflatex --jobname=abcd --output-directory=build/ '\input\relax' '\input' sample2e ---------------------------------------------------------------------- This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022) (preloaded format=pdflatex) restricted \write18 enabled. entering extended mode LaTeX2e <2021-11-15> patch level 1 L3 programming layer <2022-02-24> (/usr/local/texlive/2022/texmf-dist/tex/latex/tools/.tex File ignored) (/usr/local/texlive/2022/texmf-dist/tex/latex/base/sample2e.tex ... ---------------------------------------------------------------------- (2) In actual usage, "\input\relax" is mandatory because it is an argument of mylatex.ltx written in temporal xxx.ini file created by (kinda) script and we are trying to dump format file with -ini like this: lualatex -ini --output-directory="build/" -interaction=nonstopmode "&lualatex" prv_tst-prv.ini "\nonstopmode\nofiles\PassOptionsToPackage{active,tightpage,auctex}{preview}\AtBeginDocument{\ifx\ifPreview\undefined\RequirePackage[displaymath,floats,graphics,textmath,sections,footnotes]{preview}[2004/11/05]\fi}" "\input" tst-prv.tex (3) When I answer the prompt "Please type another input file name:" providing ".tex", the process continues and completes. However, we can't take this way because we want to use it like batch operation by -interaction=nonstopmode option. (4) When I copy the ".tex" file in the "build" subdirctory, the above command succeeds: cp /usr/local/texlive/2022/texmf-dist/tex/latex/tools/.tex build/ lualatex --jobname=abcd --output-directory=build/ '\input\relax' '\input' sample2e ---------------------------------------------------------------------- This is LuaHBTeX, Version 1.15.0 (TeX Live 2022) restricted system commands enabled. LaTeX2e <2021-11-15> patch level 1 L3 programming layer <2022-02-24> (./build//.tex File ignored) (/usr/local/texlive/2022/texmf-dist/tex/latex/base/sample2e.tex ... ---------------------------------------------------------------------- However, such approach isn't suitable for our batch-like usage. Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine

2 6

Fonts used for luatex discretionaries
by David Carlisle 30 Jul '22

30 Jul '22

Normally a hyphen inserted at a line break comes from the font used for the current word. If the luatex extended {before}{after}{nobreak} syntax is used in \hyphenation the same is true unless the nobreak field is empty in which case the font from (I think) the end of the paragraph is used. This is LuaTeX, Version 1.15.0 (TeX Live 2022) You can work around the issue by repeating the following character so {-}{w}{w} instead of {-}{}{}w in the attached example, but this seems wrong? David

3 3