Structured LOG files

[Paulo Ney de Souza]

How do-able would be to make TeX write a better (more structured) LOG file?

Take the example down below, where one is trying, for example, to parse the
LOG file to check which pages have overfulls:

...
[44]
Underfull \hbox (badness 1895) in paragraph at lines 1699--1700
[] []|\TU/TimesNewRoman(0)/bx/n/10 3.6.2 Conjetura de Birch y
Swinnerton-Dyer.[
] \TU/TimesNewRoman(0)/m/n/10 Hemos definido el regulador
 []

[45]
Overfull \hbox (4.49274pt too wide) in paragraph at lines 1718--1719
[]\TU/TimesNewRoman(0)/m/n/10 Gracias a esto último, podemos ahora expresar
la
conjetura completa (ver [][][][][]Tate [1995][][]):
 []

[46] [47] [48]
Package microtype Info: Loading generic protrusion settings for font family
(microtype)             `lmtt' (encoding: TU).
(microtype)             For optimal results, create family-specific
settings.
(microtype)             See the microtype manual for details.
 [49]
...


It is natural to look for the "[numbers]" after the overfull, but parsing
for things that happen in between brackets will lead you to believe the
Overfull in line  1718--1719 is at page "1995".

The "freewheelling" nature of the standard log file -- mixing page-number
with date and other info make it almost impossible to reliably extract
reasonable information from long log files, or to parse it automatically.

Paulo Ney
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/texhax/attachments/20190508/c12486e6/attachment.html>