Re: [Bug-gnupress] To Do List

[Ciaran O'Riordan]

On Tue, Apr 08, 2003 at 01:48:37PM -0400, Lisa M. Opus Goldstein wrote:
> Simon Law <address@hidden> wrote:
> > > 
> > > I print using the @smallbook feature.  Have you been using
> > > this when you look at layout? 
> > 
> >     Oh dear me, no.
> > 
> >     I was completely unaware that @smallbook existed.  Do you also
> > use @smalldisplay, @smallexample, @smallformat, and @smalllisp as well?
> 
> 
> Hmm...  The only variable I personally change is adding @smallbook at
> the very top of the header file.  I do not specifically add those
> other options that you mentioned.  However, @smallbook may call them.
> I am not sure about this.


@smallbook does two things:
1) generates a 7 x 9.25 inch output (instead of 8.5 x 11 inch)
2) uses a smaller font when @smallexample (etc.) is used.
   (@smallbook does not imply/call @smallexample,
    @smallexample is ignored if @smallbook is not set.)

The TeXinfo manual recommends using @example _or_ @smallexample
exclusively.  The GCC manual uses both in near equal proporatoins :)

(grep '@example' * -rs|wc -l           # ==> 384
 grep '@smallexample' * -rs|wc -l      # ==> 282)

which would everyone prefer? (@smallexample was my guess)

I cvs'd a fresh gcc-3_3-branc gcc/gcc/doc and changed all @example's
to @smallexample.

Can anyone tell me how to make a propper gcc patch though?
Here's what I did:

$ cp -a gcc cow-dir             # just a random name
$ cvs -d :pserver:address@hidden:/cvsroot/gcc diff \
  -rgcc-3_3-branch cow-dir > bad_example.patch

I've posted the patch (35kb) to:
http://compsoc.com/~coriordan/bad_example.patch

I'm assuming this isn't correct, if someone could tell me
the propper way to make a patch (or how to check if a patch
is propper)I'd make a clean one.  There are also 7 @display
tags to be converted to @smalldisplay, I'll add this to the
propper version.


thanks.
Ciaran O'Riordan

p.s. archives now online: (ml still nongnu though)
http://mail.gnu.org/archive/html/bug-gnupress/