bug-gnupress
[Top][All Lists]
Advanced

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

Re: [Bug-gnupress] Thank you for offering to proofread "Using GCC"


From: Simon Law
Subject: Re: [Bug-gnupress] Thank you for offering to proofread "Using GCC"
Date: Tue, 22 Apr 2003 04:44:32 -0400
User-agent: Mutt/1.3.28i

Dear volunteers,

Thank you to the people from address@hidden who are volunteering
their time.  This is the first status update to the copyediting effort.

        I have prepared the second set of proofs: these incorporate
changes from GCC's 3.3 CVS branch, and the patches whose change logs I
have appended to the end of this message.  You may find these proofs in
PDF form at the following URLs.

http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.001.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.002.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.003.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.004.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.005.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.006.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.007.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.008.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.009.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.010.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.011.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.012.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.013.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.014.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.015.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.016.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.017.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.018.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.019.pdf
http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.020.pdf

        Currently, I have recorded the following volunteers:

Ciaran O'Riordan
James Howison           Editing gcc.007.pdf and gcc.014.pdf
Richard Kreuter
Lisa Goldstein
Stephen Compall         Edited gcc.005.pdf
Alexandros Papadopoulos Editing gcc.016.pdf and gcc.017.pdf
Jack Nerad              Editing gcc.001.pdf and gcc.002.pdf
Paul Crable             Editing gcc.001.pdf and gcc.002.pdf
Rob Hughes              Editing gcc.010.pdf
Dan Colascione

        Currently, the following sections still need volunteers:

gcc.003.pdf gcc.003.pdf
gcc.004.pdf gcc.004.pdf
gcc.005.pdf
gcc.006.pdf gcc.006.pdf
gcc.007.pdf
gcc.008.pdf gcc.008.pdf
gcc.009.pdf gcc.009.pdf
gcc.010.pdf
gcc.011.pdf gcc.011.pdf
gcc.012.pdf gcc.012.pdf
gcc.013.pdf gcc.013.pdf
gcc.014.pdf
gcc.015.pdf gcc.015.pdf
gcc.016.pdf
gcc.017.pdf
gcc.018.pdf gcc.018.pdf
gcc.019.pdf gcc.019.pdf
gcc.020.pdf gcc.020.pdf

        We hope that each person edits two sections.  I'd suggest that
you pick a section that has not yet been edited, and do that.  We aim
for each section to be edited by two different people.

        I do not think that the GNU has an official style.  However, GCC
itself does have a small style guide which can be found in the
"Spelling, terminology and markup" section of this webpage:
http://gcc.gnu.org/codingconventions.html

        Once you are finished editing a portion, please e-mail the
mailing list with the section you edited, and any corrections that need
to be made.  You may either send a patch directly against the Texinfo
source [1]; or you may use standard errata notation like so:

    p. 15, line 10: "...something up with which we will not put." 
    should read "...something we will not put up with."

        You may notice black boxes in the right margin.  These boxes are
inserted by Texinfo to show that a line is extending into the right
margin.  If the protrusion is not noticable, ignore it.  If it is
unsightly, please suggest an alternate wording that allows the line to
wrap in a nicer fashion.

        Thanks again.

Simon

-----
[1] A tarball of the sources I used to generate the PDFs is available
    at http://www.csclub.uwaterloo.ca/~sfllaw/using-gcc/gcc.tar.bz2

    You will need to have checked out the GNU Press CVS repository.
    I have checked mine into the ~/gnupress directory.  In order to
    build a DVI of the manual:
    bash-2.05b$ texi2dvi -I ~/gnupress/texpress -I . -I include gcc.texi

    To view the DVI:
    bash-2.05b$ xdvi -paper 7x9.25in gcc.dvi

    To build the PDF from that, use:
    bash-2.05b$ dvipdf gcc.dvi

Patches I have applied (some don't have change logs):
=====================================================

2003-04-17  Stephen Compall  <address@hidden>

        * cppopts.texi: Specified behavior of -I with system headers when
        -nostdinc is passed.
        Changed @strong{Note:} to @strong{Please note:} to fix potential
        Info parsing problem.
        Various small grammar fixes.
        * invoke.texi: Added code tags around C constants and functions,
        as well as samp and option tags in appropriate places.
        Clarified units of `ggc-min-heapsize'.
        Fixed quote marks around "RAM".
        Various small grammar fixes.

2003-04-17  James A Morrison  <address@hidden>
        
        * invoke.texi Eliminate extra white-space caused by
        @gccoptlist{ on its own line.
        Re-wrapped option lines that were too wide.
        Added @gol to options that didn't have them.
        Ensured there are two spaces between each option.
        (Dariwn Options): Realphabetize the list. Put all the Mac OS 
        linker options in a @gccoptlist.

Hey, 

 I Needed to slightly alter the spacing on the licenses to make them
fit.  This patch is mostly simon's work.  I made the minor change in
standards.texi, if it's wrong, flame me.  This patch will be going to
gcc-patches with the diff against gcc.texi removed.

Jim

 Hey, 

  This one has already been sent to gcc-patches minus me removing the
call for fixes in the contribution list.  I don't think we need that
in the published book, and it saves a couple more lines.

Jim





reply via email to

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