Re: TeX error handling

[Simon Josefsson]

"Eli Zaretskii" <address@hidden> writes:

>>   Is it something worth striving for?  IMHO, things look fine
>>   anyway.
>
> It _is_ worth striving for, but if your manual has lots of strings
> that TeX cannot hyphenate (like long URLs or file names), then it
> might be hard to eliminate overfull hbox warnings below 30pt.  Above
> that value, things really don't look fine, if you ask me: the overfull
> text sticks out into the margin in a way that is really unpleasant.
> That is, I'd certainly do _something_ about a warning like this:
>
>> Overfull \hbox (124.16682pt too wide) in paragraph at lines 1869--1869
>>  address@hidden Checking whether the server can accept a bogus TLS record 
>> version in
>>  the client hello... yes[] |
>
> What I do in such cases, if I cannot fix it by rearranging text, is to
> add a space in the middle of the long string that's causing the
> problem.
>
> (I assume that you do know about @finalout and about the trick with
> \global\emergencystretch explained in the node "Overfull hboxes" in
> the Texinfo manual.  If not, perhaps those are your friends.)

When I tried emergencystretch, I got warnings about underfull boxes.
What does that mean?  How can I fix those warnings?

I probably don't need emergencystretch, though.  I think I have fixed
all overful hboxes now, except for generated texinfo and the above
example (which I believe would be fixed if I got @noindent to work).

It would help if the 'lines 1869--1869' messages (shouldn't that be
'line 1869'!?) mentioned a filename.  I get overful hbox warnings for
@include'd files, and I have no idea which file is the problem.  E.g:

Overfull \hbox (80.47473pt too wide) in paragraph at lines 1038--1044
 /address@hidden/GNUTLS[]CRL[]REASON[]AFFILIATION[]CHANGED, GNUTLS[]CRL[]REASON[
]SUPERSEEDED,

Only by grep'ing, I found out that 'x509-api.texi' was the place it
warned about.

Thanks,
Simon