This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav: Message Nav: [Date Index] [Subject Index] [Author Index] [Thread Index] [Date Prev] [Date Next] [Thread Prev] [Thread Next]

# Re: Manuals

• To: Bob Kruit <bob at ease dot nl>
• Subject: Re: Manuals
• From: "Zack Weinberg" <zackw at stanford dot edu>
• Date: Wed, 2 May 2001 00:34:42 -0700
• Cc: gcc at gcc dot gnu dot org
• References: <002a01c0d2d5$328be5b0$be0000c0@ease902>

On Wed, May 02, 2001 at 08:57:44AM +0200, Bob Kruit wrote:
>
>    I have one remark on the site. It's about the manuals. They are only
>    avalible in HTML. It would it easy if they were also avalible in PDF.
>    This makes printing them a lot easier.

Please don't send mail in HTML to this list.

source tree and configure it, run 'make dvi' in the gcc subdirectory,
then convert the .dvi files with dvipdf.  Or you can figure out the
appropriate commands and use pdftex.  Or generate the .dvi files and
print them directly, if your printer drivers can handle them.  Note
that the longest manual ("Using and Porting GCC") is 500 pages or so.

You can also order nicely printed and bound manuals from the Free
Software Foundation, but I don't know how old they are.

Maybe we should add a 'make pdf' target to the Makefiles.

As for putting pre-generated PDFs on the website, I think the major
issue would be file size.  gcc.pdf as rendered by pdftex is 2.5MB; as
rendered by plain TeX and then dvipdf, 2.6MB.  That's the biggest
manual, of course.  I don't know what the website disk space situation
is like.  If anyone has a clue how to make texinfo.tex use the fonts
would shrink 'em quite a bit.

It could be useful to have an automated process running 'make dvi' -
judging by the sheer number of bad \hbox warnings that scrolled by on
my screen, no one's bothered to do that in a long, long time.

For online viewing of PDFs we would probably want to figure out how to