On Tue, Mar 31, 2026 at 11:58:50AM +0100, Gavin Smith wrote:
> On Tue, Mar 31, 2026 at 12:40:27AM -0300, Jamenson Espindula wrote:
> > Em seg., 30 de mar. de 2026 às 10:38, Gavin Smith
> > <[email protected]> escreveu:
> > >
> > > Can you please send texinfo.pt_BR.texi (the Texinfo source file) not
> > > texinfo.pt_BR.log?
> > >
> > I got the PDF format anyway. It seems the several messages does not
> > prevent the PDF to be output. As far as I know, all the internal links
> > on the generated PDF works as expected.
>
> I got the same "Missing characters" in the log file and am investigating.
> It's possible these warnings are not a real problem with the generation of
> the output, but at the least they are confusing and bloat the log.
I believe I have fixed the issue in the latest version of texinfo.tex in
the git repository. It was I expected - not a real problem with the output.
It was due to an unusual method we used with TeX in order to extract
@sortas{...} commands (and a couple of others) from index entries - typeset
the entries in a dummy hbox, and then ignore the result. Because we were in
the middle of outputting to an auxiliary index file, bytes were to be output
literally with no combination of bytes in a UTF-8 sequence for a character,
but this led to the missing glyph errors for the non-ASCII bytes.
I've reimplemented this to use a more conventional macro expansion
approach. As is often the case with TeX macros, the new code is also
somewhat obscure, although I doubt there is a much simpler way of
accomplishing what it does. In terms of execution times, it seems not
to make any difference, though.
