[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnupress] To Do List
From: |
Simon Law |
Subject: |
Re: [Bug-gnupress] To Do List |
Date: |
Wed, 9 Apr 2003 01:03:02 -0400 |
User-agent: |
Mutt/1.3.28i |
On Wed, Apr 09, 2003 at 03:41:59AM +0100, Ciaran O'Riordan wrote:
> 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)
Oops. I guess I lied about figures in my other e-mail. Ah
well, as an engineer my numbers are always approximate anyway.
> 2) uses a smaller font when @smallexample (etc.) is used.
> (@smallbook does not imply/call @smallexample,
> @smallexample is ignored if @smallbook is not set.)
In CVS Texinfo, @smallexample _always_ uses the small font.
Check the mailing list if you want to see Karl's sheepish explanation.
> 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)
@smallexample is probably preferable. If you check in
gnupress/texpress/gnupress.tex, you will see that I have overridden
@example to _always_ behave like @smallexample. This ensures uniformity
on our part at nearly zero cost, although the GCC manual will be ugly
if they update to Texinfo >> 4.5.
> I cvs'd a fresh gcc-3_3-branc gcc/gcc/doc and changed all @example's
> to @smallexample.
I see. I'm not sure how well that will work, since all the
examples will be super small when printed on 8.5 x 11 inch.
> 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 prefer to do a `cvs update`, then I have to merge any
conflicts, and then I will do a `cvs diff -u gcc/doc/*.texi` which will
give good results. CVS remembers which server you checked something out
of, and which branch you pulled from.
> I've posted the patch (35kb) to:
> http://compsoc.com/~coriordan/bad_example.patch
I can't reach compsoc.com, sorry.
> 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.
Hold off on all that hard work for a bit. You should probably
mention this on the bug-texinfo list.
Simon
- Re: [Bug-gnupress] To Do List, (continued)
Re: [Bug-gnupress] To Do List, Ciaran O'Riordan, 2003/04/08
- Re: [Bug-gnupress] To Do List,
Simon Law <=
Re: [Bug-gnupress] To Do List, James A. Morrison, 2003/04/09