This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: PR other/29972: typos in the manual
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Mon, 28 Jan 2008 01:57:00 +0100 (CET)
- Subject: Re: PATCH: PR other/29972: typos in the manual
- References: <20080124181751.GD14722@ins.uni-bonn.de>
On Thu, 24 Jan 2008, Ralf Wildenhues wrote:
> It would be nice if someone could review and apply this patch for me.
> Tested `make dvi info' with texinfo 4.8. Thanks Manuel for reminding me
> of it.
After reading the following
Use a comma after "e.g." or "i.e." if and only if it is appropriate
in the context and the slight pause a comma means helps the reader; do
not add them automatically in all cases just because some style guides
say so. (In Texinfo manuals, <code>@:</code> should to be used after
"e.g." and "i.e." when a comma isn't used.)</p>
at http://gcc.gnu.org/codingconventions.html I am not completely sure
whether the changes to replace "i.e." by "i.e.," all are fine. Have
you carefully considered each case?
Also, in
* doc/invoke.texi (C++ Dialect Options, Optimize Options)
(HPPA Options, i386 and x86-64 Options, IA-64 Options)
(RS/6000 and PowerPC Options): Fix typos.
I believe we don't need parenthesis around each line, or is this
specified in some coding standard I may have missed? (I can make
this change myself in case, just wanted to double check.)
Gerald