Re: \tracinglostchars

Hi Ross,

Le 15 févr. 2021 à 21:14, Ross Moore <[email protected]> a écrit :

> … and all this extra noise would just turn off most users anyway.
> 
> Serious users, who are aware of how useful the  .log  file really is,
> should have the ability to make adjustments for themselves.
> 
> You can always put the directive:
>   \tracinglostchars2
> in your preamble.
> It doesn’t need to be a LaTeX default.

I mentioned LaTeX, which was my mistake because
it was not a latex question on this why I did not address
it to the latex team ; however it is relevant to LaTeX
as typically LaTeX produces tons of log output

what I was trying to say is that both

\tracinglostchars1

and

\tracinglostchars2

are lacking imho in usefulness because, whether to terminal
or to the log, their output might easily go unnoticed,
and it is very important indeed what they try to tell the user

sure, if you get a whole bunch of 20 of them in a row,
you might see them in console output, but if you have
only one such warning and are building a 200 pages document
which nowadays is faster than 20 years ago,
the stdout stream flashes bye so quick, you might not 
see it

hence my query for a stronger behavior which would
be to add to both stdout and the log file a one-line
warning at end of run

either that, or  a 

\tracinglostchars3

which would trigger that

it would match then with some other
of etex report mechanisms

Thanks,

Jean-François