Re: [PATCH, DOC] Fortran manual typos

[FX Coudert <fxcoudert at gmail dot com>]

> gcc/fortran/ChangeLog:
> 2008-02-21  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
>
> 	* gfc-internals.texi: Fix typos and markup nits.
> 	* gfortran.texi: Likewise.
> 	* intrinsic.texi: Likewise.

OK. I have one question (out of curiosity):

>  If the current statement is one of @code{IF}, @code{DO}, @code 
> {SELECT}
> -it starts a block, i.e. a nested level in the program.  In order to
> +it starts a block, i.e.@: a nested level in the program.  In order to
>  represent this, the @code{block} member is set to point to a

I see you use a column after "i.e." while, according to Wikipedia,  
"American style guides tend to recommend that "e.g." and "i.e."  
should generally be followed by a comma, just as "for example" and  
"that is" would be; UK style tends to omit the comma." I'm not a  
native speaker and my Oxford Style Guide and Butcher's are in the  
friend's bedroom, which actually hosts friends tonight, so I can't  
look it up. Any particular reason to use a column? (I see, from a  
quick grep of GCC docs, that column and coma are equally represented.)

FX

--
François-Xavier Coudert
http://www.homepages.ucl.ac.uk/~uccafco/