[Bug-gnupress] [DOCPATCH] Section 2 (was: Now I have a real question)

[Simon Law]

On Fri, May 09, 2003 at 06:15:06PM -0500, J. Otto Tennant wrote:
>    Do you want to hear about instances of really trivial typographical
>    errors?

        Yes we do!

>    For example, in gcc.002.pdf, we read towards the very end of the file:
> 
>      In this case,G++ will place B::f2 into the same byte asA::f1; other
> 
>    The "asA" should be "as A".

        Ouch.  Attached is a patch.

>    I'm learning more than I want to know about PDF files.  Is there a way to
>    recover the line number, so I do not have to say anything as vague as
>    "towards the very end of the file"?

        Not particularly, no.

        If you are familiar with a text editor, you should download the
gcc.tar.bz2 file off my website and edit the *.texi files in there.  If
you can produce a patch, that would be superb.

>    Thanks.
> 
>    (By the way, I "randomly" picked 3 and 17.  My note on "2" is only because
>    I had to glance at it to make sense of 3.)

        Thanks.  That's fine.  I'll put you down for 3 and 17.  You
should send these messages to address@hidden, since it is a public
effort.  I am forwarding this there.

Simon

2003-05-09  J. Otto Tennant  <address@hidden>

        * doc/invoke.texi: Fixed minor spacing error.

--- invoke.texi.orig    2003-05-09 20:46:36.000000000 -0400
+++ invoke.texi 2003-05-09 20:46:45.000000000 -0400
@@ -1503,7 +1503,7 @@
 
 @noindent
 In this case, G++ will place @code{B::f2} into the same byte
address@hidden::f1}; other compilers will not.  You can avoid this problem 
+as @code{A::f1}; other compilers will not.  You can avoid this problem 
 by explicitly padding @code{A} so that its size is a multiple of the
 byte size on your platform; that will cause G++ and other compilers to
 layout @code{B} identically.