March 2022 - dev-luatex - NTG Mailing Lists

Luatex 1.12.0 announcement.
by luigi scarso 27 May '23

27 May '23

============================================================== LuaTeX 1.12.0 2020-03-15 ============================================================== This is the release for TeX live 2020. --shell-restricted now forbids loading of dso (dll/so object) Scaled virtual font Aadditional primitives \eTeXglue[stretch|shrink]order for querying order the etex way. Extra features runtoks tex.getmodenames() (as these can differ per engine/version) Permit nested runtoks in more complex situations of nesting (HH) More accurate and correct test for tex.[set|get]math Minor clean-up and bugs fixed -- luigi

4 8

Fix for pdf_literal Lua string / token list conversions
by Michal Vlasák 06 May '23

06 May '23

Hello, take this plain LuaTeX example: \setbox0=\hbox{\pdfextension literal{0 g}} % 1) \directlua{ local literal = tex.getbox(0).head texio.write_nl("log", "literal.data="..literal.data) } \showbox0 % 2) \directlua{ local literal = tex.getbox(0).head literal.data = "test" literal.token = "toks" texio.write_nl("log", "literal.token="..(literal.token or "nil")) } \showbox0 % 3) patch test \directlua{ tex.set("everyjob", "asd") texio.write_nl("log", tex.get("everyjob")) } \bye Expected log output (abridged): 1) literal.data=0 g .\pdfliteral origin{0 g} 2) literal.token=toks .\pdfliteral origin{toks} Actual output: 1) literal.data=data .\pdfliteral origin{0 g} 2) literal.token=characters .\pdfliteral origin <lua data reference 153> In the first case the Lua accessor returns a value which happens to be on top of the stack (the key "data" itself). In the second case an index into TeX memory is misinterpreted as a Lua registry index, so the returned data is essentially garbage. Patch for both issues is attached. I also extended `tokenlist_from_lua` (which is what `nodelib_gettoks` is defined as) to allow an index argument. The previous version used the value on top of the stack, which probably worked for every use currently in LuaTeX, but seemed rather dangerous and subtle. The patch is from git, though it can be applied normally with patch -Np1 < pdf_literal.patch Kind regards, Michal Vlasák

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

Problem with directlua and synctex_tag
by Jérôme LAURENS 30 Mar '22

30 Mar '22

We can use ``` \directlua{tex.set_synctex_tag(421)} \directlua{print('421=',tex.get_synctex_tag())} \bye ``` To set and read the synctex tag. But if we wrap this into a macro, things get broken and the synctex tag is not changed. ``` \def\test{\directlua{tex.set_synctex_tag(421)}} \test \directlua{print('421=',tex.get_synctex_tag())} \bye ``` For synctex_line there is no such problem. Is this a bug or a feature ?

4 13

Re: [Dev-luatex] 2 characters shift in error context
by luigi scarso 28 Mar '22

28 Mar '22

On Sun, Mar 27, 2022 at 5:11 PM Ikumi Keita <ikumikeita(a)jcom.home.ne.jp> wrote: > Hi, > > >>>>> luigi scarso <luigi.scarso(a)gmail.com> writes: > > I have checked it but luatex and pdftex manage the split the line in > > different way. > > For example this gives a different log > > Nullam eu ante vel est convallis dignissim.0123456789} Nulla posuere. > > \bye > > I will look at the xetex output closely. > > Do you have any news about this? > Sorry for the delay. I have to postpone it, no time now . I am not sure that I will fix it because I don't see a bug (yet). -- luigi

3 2

Re: [Dev-luatex] LuaLaTeX -- hyperlink with ragged right
by Suki, Venkatesan (TNQ Software) 26 Mar '22

26 Mar '22

Please send the LaTeX markup code also... SKV On Sat, 26 Mar, 2022, 8:34 am Kunchitapadam, Baskaran (TNQ Software), < n.k.baskaran(a)tnqsoftware.co.in> wrote: > Hi Team, > > I am working in LuaLaTeX templates. I have face the below issue in title > formatting. I have ragged right title content which is hyperlinked. > > Each line end blank also covered hyper link. We need to format like the > last line in below image. Kindly suggest a solution. > > -- > > Thanks and Regards > > Baskaran NK > > Tech. Lead – 4722 / 4847 > > M : +91 9840928250 > > TNQ Technologies Pvt. Ltd. > > Linkedin <https://www.linkedin.com/company/tnqtechnologies/> | Twitter > <https://twitter.com/TNQtechnologies> | Facebook > <https://www.facebook.com/TNQTechnologies> > > T : +91 44 4596 4800 | tnq.co.in <http://www.tnq.co.in/> > > > -- Disclaimer: The entire content of this email message, including any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee or part of the entity, you should not disseminate, distribute, or copy this email. Please notify the sender immediately by e-mail if you have received this email by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing, or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

2 characters shift in error context
by Ikumi Keita 21 Mar '22

21 Mar '22

Hello LuaTeX developers, I have a few questions I'd like to ask you. In log message, luatex engine produces slightly different error context from what pdftex does. Here is a sample code: ---------------------------------------------------------------------- Nullam eu ante vel est convallis dignissim. } Nulla posuere. \bye ---------------------------------------------------------------------- When I process this file by luatex, it results in the following error: ------ luatex result ------------------------------------------------- ! Too many }'s. l.1 Nullam eu ante vel est convallis dignissim. } Nulla posuere. ---------------------------------------------------------------------- On the other hand, pdftex results in: ------ pdftex result ------------------------------------------------- ! Too many }'s. l.1 Nullam eu ante vel est convallis dignissim. } Nulla posuere. ---------------------------------------------------------------------- The output of luatex is shifted by two characters compared with that of pdftex. (I'm using TeX Live 2021.) This discrepancy confuses preview-latex (subsystem of AUCTeX), which depends on the precise position of the log messages: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54200 I'm not sure whether this behavior is a bug or not, but is it something I can expect to be fixed? If not, is there any workaround to make the output the same as pdftex? (e.g. command line option) Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine

3 8

bug with \showbox
by Petr Olsak 08 Mar '22

08 Mar '22

Suppose this file: -------------- \immediate\openout0=test.ref \setbox13=\hbox{aha} \showbox13 \end -------------- If I run "luatex file", it ends without errors and the \showbox result is written in the test.ref file. But if the \openout line is commented or it is opened another output stream than zero, then the behavior is correct: it ends with: ---------------- ! OK (see the transcript file). l.5 \showbox13 ? ---------------- luatex --credits: This is LuaTeX, Version 1.15.0 (TeX Live 2022) ... Development id: 7503 The luatex from TL2021 (id 7430) does have this problem, i.e the \showbox result is in transcript file always. Regards Petr Olsak

2 1