Comment 3 for bug 1326601

Good work, Dmitry!

This solves #2 and #3 in my original list.

About the PDF versus HTML... People don't initially realize that they have a choice when they
open the doc page -- people come to me and ask why we can't produce HTML docs along with
the PDF.

I think most people are going to use both. The xrefs-as-links in the HTML docs are very useful
and they don't work as well in the PDF. And we have situations like the second half of the Planning Guide,
which has example configuration information that eats up a lot of paper and may not be worth printing.
If people look at the PDF before they print, they can specify the pages to print but otherwise... It might
be good to create a separate guide with "Configuration Examples" or something if a signigicant number
are printing it off.

As for the graphics... I DO specify the width... But graphics that are way too big in HTML are too small
to read easily in PDF. And the align property is causing problems; without it, the screen shots are
mostly defaulting to left-justified in HTML and centered in PDF.