[XeTeX] [texworks] Overfull boxes return status of 0 in XeTeX

[Melroch]

Den 19 mar 2016 11:00 skrev "Philip Taylor" <P.Taylor at rhul.ac.uk>:
>
>
>
> Reinhard Kotucha wrote:
>
> > It's true that only TeX /knows/ whether bad boxes occurred during a
> > TeX run.  But TeX passes this knowledge to the log file, hence
> > nothing is lost and the log file even provides more information
> > (line numbers).
>
> But, as previously pointed out, a TeX program can write to the log file
> and simulate (e.g.,) an overfull \hbox message.
>

It is worth noting that both the exit status and the content of the log
file are information which the TeX program (or rather its programmer(s))
choose to pass on to the 'outside world' at its own discretion. Neither is
inherently more true or accurate than the other. The logfile is more
detailed, which should be a good thing. If you think that some of the info
in the logfile is excessive then bear in mind that that info too would
probably trigger a potential different exit status. The TeX program would
hardly distinguish between more or less important overfull \hboxes and
choose a different exit status based on that without not also noting the
difference in the logfile. I think most users would find that absurd. If
you think that the info in the logfile isn't granular enough then that is
what you should request to be changed. It should however be born in mind
that there hardly is any automated substitute to inspecting and comparing
the logfile, the source and the output. A program (whether you call it
'script' or not is irrelevant) analysing the logfile could help you
determine where to look, which a changed exit status hardly could. I don't
think you need to worry about the time it takes to scan the log file. I
have Perl scripts which scan files containing thousands of lines in well
under a second on computers which compare to the ones my son plays games on
as a wheelbarrow compares to a race car. A TeX run itself takes far more
time than running such a script.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/xetex/attachments/20160319/e4fa4368/attachment.html>