On Thu, 9 Jan 2025 at 09:12, Werner LEMBERG <w...@gnu.org> wrote:
> >> So: can this be fixed on the side of `texinfo.tex` at least for the
> >> space character, circumventing the luatex bug for the most common
> >> case?
> >
> > I have minimal understanding of lua and luatex. I've edited
> > texinfo.tex in the obvious way: [...]
> >
> > Is there any testing you can do of this to confirm it works as
> > expected before I commit it?
>
> Yes, I tested it by simply rebuilding the LilyPond documentation (from
> current git); `gs` gets used as a post-processor if the
> `extractpdfmark` utility is installed.
>
> Alas, your patch doesn't fix the issue; I get the same bad result
> (i.e., missing entries in the outline) as before. Apparently it is
> important that the space character gets protected.
>
> I guess we have to wait until Luigi has corrected this problem in
> luatex.
>
> Luigi, Masamichi-san, can you confirm, please? Gavin's patch can be
> found here:
>
> https://lists.gnu.org/archive/html/bug-texinfo/2025-01/msg00049.html
>
> If I'm right it maybe makes sense to add a small note to Texinfo,
> mentioning that you need a luatex version XXXX or newer to get correct
> outlines.
>
Ok, I will check the patch later.
About pdf: You can see the internal data structures by prefixing the texi
file to be compiled with luatex with these lines:
%%\loggingall
\edef\pdfcompresslevel {\pdfvariable compresslevel}
\edef\pdfobjcompresslevel {\pdfvariable objcompresslevel}
\edef\pdfrecompress {\pdfvariable recompress}
\pdfcompresslevel 0
\pdfobjcompresslevel 0
\pdfrecompress 0
(\loggingall generates a complete but huge log).
--
luigi
