I haven't followed the discussion in detail, but IMHO it would be nonsense to
turn overfull boxes into errors, because they are not errors, rather the line
breaking algorithm could not find a proper way to fix things differently.
Remember, there is always the "draft" mode which will clearly show all overfull
boxes marked with black lines in the final PDF.
Wilfred
On Sunday, March 13, 2016 7:54 PM, Philip Taylor <p.tay...@rhul.ac.uk>
wrote:
Zdenek Wagner wrote:
> This is not even mentioned on the console, the user must read the log
> file. Overfull boxes make the output at least readable, missing
> characters present a serious problem.
No, they can both render the output meaningless, particularly when the
overfull box horizontally abuts another box. This is not to say that I
by any means disagree that missing glyphs should (be capable of)
generating a non-zero status code; they most certainly should, as should
all warnings that TeX is capable of emitting. And they could usefully
be (capable of) appearing in the console output as well as in the log
file (perhaps a second new command-line parameter, or a side-effect of
the first).
** Phil.
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
