Re: [Bug-gnupress] Some kind of TODO?

[Simon Law]

On Wed, Mar 26, 2003 at 03:51:31PM +0000, Ciaran O'Riordan wrote:
> On Wed, Mar 26, 2003 at 09:45:02AM -0500, Simon Law wrote:
> > On Wed, Mar 26, 2003 at 01:10:13PM +0000, Ciaran O'Riordan wrote:
> [TODO]
> > > Change font size or line spacing to save pages in GLibc manual(right?)
> > 
> >     That has to do with @itemize and @enumerate lists.  There is
> > most likely a \vskip in there that needs its argument turned to 0pt.
> 
> I'll take a look at this when I get a minute, it sounds like a non-bug
> annoyance in TexInfo, I think I've seen it before.  The
> solution (assuming the probem is spacing between '@item's) is
> just to take away blank lines on either side of the '@item's in
> the texinfo source.  If I'm right then it's a two minute fix with
> emacs.

        Urhm.  That's a fairly lousy way to solve the problem.  I have a
sneaking suspicion that we'll want to redefine the \smallskipamount
macro.

> > > Look for things that don't look great in books of interest.
> > 
> >     I believe that Jim had grave concerns about the correctness of
> > the GCC manual.  But I don't quite recall what they were.  Perhaps he
> > could explain them.
> 
> Hmm. Last time I checked the manual was pretty up to date, at the
> dinner on saturday I mentioned that some new features in GCC 3.2/3.3
> have not been documented but Opus said there wasn't time for that
> kind of work on the manuals, just simple fixes.

        We've eaten about two weeks into the two month deadline.  I
expect that I'll be able to churn out galley proofs of the GCC 3.3
manual by the end of next week, if all goes well.

        This should give us sufficient time to determine if that manual
is good shape with the new reality of GCC:
http://gcc.gnu.org/gcc-3.3/changes.html

> > > I've made good progress in changing font sizes so far, I'll
> > > post my methods and output tomorrow when I have some time
> > > at my home computer.
> > 
> >     Are they similar to mine?
> 
> probably not ;) Being fairly new to TeX I did a little reading then
> started butchering my system texinfo.tex.

        Ick.  I wouldn't want to have to hack texinfo.tex for every
manual we put out.

Simon