Sender:	nate AT cartsys DOT com
Message-ID:	<363E9EC3.A79B4468@cartsys.com>
Date:	Mon, 02 Nov 1998 22:12:19 -0800
From:	Nate Eldredge <nate AT cartsys DOT com>
X-Mailer:	Mozilla 4.05 [en] (X11; I; Linux 2.0.35 i486)
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: TeXing libc/libm docs
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 981102183629 DOT 13235G-100000 AT is>
Reply-To:	djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> 
> We had a discussion about this some time in the past, and I promised to
> try this.
> 
> Well, I did.  TeX happily processed both libc.tex and libm.texinfo.  The
> libc docs generated a large number of overfull box warnings, mostly due to
> the synopsis lines with those long __dpmi_bla_bla_yak_yak names.  I ran
> `find' that replaced all of the @example into @smallexample, which caused
> some of the warning to go away; but others stayed.
> 
> Libm.texinfo, on the other hand, didn't produce even a single warning.
> 
> Clearly, if we want to be able to produce printed docs, the .txh files
> need some more work.  If somebody volunteers, I can mail the libc.log
> file produced by TeX.

IMHO and FWIW, overfull boxes are not necessarily deadly and not
necessarily fixable.  It might be instructive to view the DVI and see
how bad it actually is.  (After setting @finalout to suppress the ugly
black boxes, that is.)

So you saw no errors that caused TeX to stop?  Seems to me I did on my
Linux teTeX installation, but that was with an older set of docs.  I may
also have an outdated texinfo.tex; I'll have to check that and try again
with the latest beta.
 
> For the record: libc.dvi produces a 490-page long printed version (no, I
> didn't actually send it to the printer ;-).

I wonder if anybody ever has or ever will?
-- 

Nate Eldredge
nate AT cartsys DOT com

- Raw text -