[Bug-gnupress] Comments on gcc.006.txt

[Paul A. Crable]

>        I'm not sure how you are getting each section as a
text file since I've been rendering PDFs...

I open the file in Adobe Acrobat, click on the "text select"
button, select all the text, and copy it to the clipboard.
I then open an ascii file and paste into it the contents of
the clipboard.  I loose all formatting but at least the text
is there and I don't have to type everything in.

>        Any form of representation is fine, as long as I
can read it. If you prepare a patch, then it saves me the
work of interpreting what you typed and editing the Texinfo
myself.

I'm afraid Texinfo is a Great Mystery to me but I will look
at your web site and see what I can pick up.

>        Hmm.  An interesting idea.  However, I suspect that
neither of those will suck in Texinfo and spit it back out
again...

Probably so.  Just a thought.

>> I find that I am making changes to virtually every
paragraph, so I intend to forward completely rewritten
sections...

>        How would this work?  The options for
M68hc1x are not available for the M680x0.

Well, it's clear I don't know enough about GCC yet to mess
with the section headings.  I'll leave them as they are.

>        It may not be object code, as GCC is
merely a driver program.  It could be assembler or even a
directed acyclic graph for human consumption.

I learn more every day.  What is a "directed acyclic graph"?

>       Paul Crable             Editing gcc.{001,002,008}.pdf,
edited gcc.006.pdf

I'm sorry to say I have only provided you edits of the first
of 17 sections in gcc.006.pdf, so I couldn't claim to have
edited it yet.


Lastly, I have a sneaking suspicion I have ventured into a Unix
world, about which I am woefully ignorant. I am doing all my work on
an Intel architecture laptop running Win2k, so it will take me some
time to get acclimated.