bug-gnupress
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Simon Law
Subject: Re: [Bug-gnupress] Some kind of TODO?
Date: Wed, 26 Mar 2003 09:45:02 -0500
User-agent: Mutt/1.5.3i

On Wed, Mar 26, 2003 at 01:10:13PM +0000, Ciaran O'Riordan wrote:
> I started to read up about TeX last night, then realised
> I didn't know what problem I was trying to solve :(
> 
> Could you post some kind of informal TODO?
> 
> IIRC, it was something like this:
> Change the fonts in books to a font that survives photocopying

        I've got this "done".  I got hit by a virus and am in the
process of recovering from it; but I have been able to reliably and
cleanly switch over the Palladino for the default Roman font face.

        I will hack on this more this weekend.  I hope to have something
that I can check into CVS.  I have just registered with Savannah as
userid sfllaw, so Jim can give me the appropriate permissions.

> 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.
That's next on my personal TODO.

> Look for overful H-boxes in books of interest.

        Overfull, and underfull h-boxes.  Widows and orphans.

> 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.

> Books of interest being:
> GCC user manual
> GNU Libc Reference manual
> GCC Internals manual (yes?)

        I think the Internals manual is on hold right now.

> 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?  What I do is redefine the fonts after
I have loaded texinfo.tex, so that I don't actually need to edit the
base file itself.

> P.S. I traced that savannah bug back to a config file.  I told
> savannah-hackers, who told system-hackers but since www.gnu.org
> was down over the weekend I'll assume they're real busy right now.

        Nifty.  Hope to see this list move to @gnu.org soon.

Simon




reply via email to

[Prev in Thread] Current Thread [Next in Thread]