- dev-luatex - NTG Mailing Lists

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

\scriptspace behavior?
by Petr Olsak 21 Jul '22

21 Jul '22

Suppose ---- $x_1=y$ \scriptspace=10pt $x_1=y$ \bye ----- When we use pdftex then we get expected result: the first formula has default script space and the second has big script space. But when we use luatex then both formulae have default script space. When the first formula is removed then the resting one has expected script space 10pt with luatex too. I am unable to understand the logic of luatex behavior. This is LuaTeX, Version 1.15.0 (TeX Live 2022) Regards Petr Olsak

1 0

Cannot compile LuaTeX on macOS / arm
by Patrick Gundlach 07 Jul '22

07 Jul '22

Hi all, I try to compile LuaTeX (master branch) on macOS / m1 (arm): ./build.sh --clang --luahb --lua53 --nojit --parallel --nostrip and after a while I get this error: libtool: link: clang++ -Wall -Wunused -Wreturn-type -Wno-write-strings -o luahbtex luatexdir/luahbtex-luatex.o mplibdir/luahbtex-lmplib.o -Wl,-bind_at_load libluahbtexspecific.a libluatex.a libff.a libluamisc.a libluasocket.a libluaffi.a libluaharfbuzz.a /Users/patrick/work/software/luaTeX/build-clang/libs/lua53/.libs/libtexlua53.a libmplibcore.a /Users/patrick/work/software/luaTeX/build-clang/libs/zziplib/libzzip.a /Users/patrick/work/software/luaTeX/build-clang/libs/libpng/libpng.a /Users/patrick/work/software/luaTeX/build-clang/libs/harfbuzz/libharfbuzz.a /Users/patrick/work/software/luaTeX/build-clang/libs/graphite2/libgraphite2.a /Users/patrick/work/software/luaTeX/build-clang/libs/pplib/libpplib.a /Users/patrick/work/software/luaTeX/build-clang/libs/zlib/libz.a lib/lib.a /Users/patrick/work/software/luaTeX/build-clang/texk/kpathsea/.libs/libkpathsea.a libmputil.a libunilib.a libmd5.a Undefined symbols for architecture arm64: "_png_do_expand_palette_rgb8_neon", referenced from: _png_do_expand_palette in libpng.a(pngrtran.o) "_png_do_expand_palette_rgba8_neon", referenced from: _png_do_expand_palette in libpng.a(pngrtran.o) "_png_init_filter_functions_neon", referenced from: _png_init_filter_functions in libpng.a(pngrutil.o) "_png_riffle_palette_neon", referenced from: _png_do_read_transformations in libpng.a(pngrtran.o) ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [luahbtex] Error 1 Is there anything I can do? Patrick

2 3

Fwd: luatex (suggestion by Ivo Welch)
by Taco Hoekwater 04 Jul '22

04 Jul '22

> Begin forwarded message: > > From: ivo welch > Subject: luatex > Date: 3 July 2022 at 21:46:46 CEST > > hi taco--- > > https://tex.stackexchange.com/questions/649666/lulatex-macos-font-mystery-f… > > I just ran into some lualatex problems with a font from macos Fontbook. > > suggestion: may I suggest improving the error messages with respect to > fonts? if a font is not found, print out *where* luatex was looking > for the font ("montserrat not found in /usr/...; /opt/..."). [maybe > also add the most similarly named font if one exists.] ulrike also > suggested that maybe the font was damaged, although it worked well > with other apps. in any case, if this could be the reason, perhaps > add a different kind of error message than "font not found." > > regards, > > /iaw > > -- > Ivo Welch (ivo.welch(a)ucla.edu) > http://www.ivo-welch.info/ > J. Fred Weston Distinguished Professor of Finance, UCLA Anderson > [please acknowledge receipt if this is the first email in a conversation] — Taco Hoekwater E: taco(a)bittext.nl genderfluid (all pronouns)

1 0

Re: [Dev-luatex] Bug#1009196: texlive-binaries: Reproducible content of .fmt files
by Norbert Preining 04 May '22

04 May '22

Hi Luigi, hi all luatex devs, here at Debian we got a bug report about reproducability of luatex format dumps. It contains a patch to make the hyphenation exception list sorted. (I attach the patch) Could you please take a look whether this is still relevant for the latest release of luatex. Thanks Norbert On Fri, 08 Apr 2022, Roland Clobus wrote: > Hello maintainers of texlive-binaries, > > While working on the “reproducible builds” effort [1], I have noticed that the > live image for Cinnamon in bookworm is no longer reproducible [2]. > > The attached patch ensures that the output of the function 'exception_strings' > always uses the same order of the hyphenation exceptions. > I've written the solution in C, perhaps someone more versed in lua could > rewrite it more elegantly. > (The lua manual says for the 'next' function: 'The order in which the indices > are enumerated is not specified' [3]) > > With the attached patch applied, I'm able (with the help of FORCE_SOURCE_DATE=1 > and SOURCE_DATE_EPOCH) to reproducibly rebuild the .fmt files, as created by > 'fmtutil --sys --all'. > > Small test case to reproduce: > export FORCE_SOURCE_DATE=1 > export SOURCE_DATE_EPOCH=$(date +%s) > for i in `seq 1 10`; do luahbtex -ini -jobname=luahbtex -progname=luabhtex > luatex.ini > /dev/null; md5sum luahbtex.*; done > > With kind regards, > Roland Clobus > > [1]: https://wiki.debian.org/ReproducibleBuilds > [2]: > https://jenkins.debian.net/view/live/job/reproducible_debian_live_build_cin… > [3]: http://www.lua.org/manual/5.4/manual.html#pdf-next > -- PREINING Norbert https://www.preining.info Mercari Inc. + IFMGA Guide + TU Wien + TeX Live GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

4 14

Feature request: busy pdf
by Jérôme LAURENS 04 May '22

04 May '22

New CLI options --busy related to typesetting luatex --busy=0 default behavior, nothing new luatex --busy=1 Instead of writing the pdf output to jobname.pdf, write to jobname.pdf(busy) At the end remove any jobname.pdf and move jobname.pdf(busy) to jobname.pdf luatex --busy=2 foo.tex If there is a jobname.pdf(busy) bail out with a diagnostic message « typesetting already in progress » Otherwise do like --busy=1 Actually, the pdf is removed at the start of the typesetting process such that it is no longer available during that whole time. When the typesetting is a bit long, it is not practical at all. For continuous typesetting neither. Considering that we work in general on the end of a document, the first pages will not change a lot but are no longer available. synctex already supports this « busy » busyness such that the previous .synctex file is available during next typesetting process.

3 17

Setting up git mirror of luatex svn repo.
by luigi scarso 04 Apr '22

04 Apr '22

Hi all, I would like to set up a git mirror (on github or ..) of the current luatex svn repo. It should cover all directory in the current repo, i.e branches, tags , tools , trunk and vendor, all with the full history. As known, the main svn repo is experimental and not trunk, but I think that we can now switch to the usual (svn) model trunk / tags . I have done some experiments locally, but probably I have messed up some configs, so I am open to suggestions. -- luigi

2 3

Feature request: SyncTeX support
by Jérôme LAURENS 03 Apr '22

03 Apr '22

There are situations where synctex info is not available: consider ``` \immediate\openin 0 {subfile.tex} \immediate\read 0 to \My \immediate\closein 0 \My \bye ``` Synctex does not see `subfile.tex` at all, which forbids any kind of synchronization between subfile.tex and main.pdf. It would be very cool if the \openin could create a new tag and the \read could use that tag while parsing subfile.tex. A synctex information about the line number would be very nice as well, a default of 1 is far better than nothing. A tex.get_synctex_tag_for_name(‘foo') would be extremely handy. Finally, raw setters and getters should be provided for synctex tag and line, to control exactly what tag and line is written to the .synctex file. No save stack for them, no mode. Simply raw. Some global synctex state stack would help: save_synctex_state/restore_synctex_state… BTW that would be great to deactivate set_synctex_tag for mode 0 just like set_synctex_line is.

2 4