Changes between Version 1 and Version 2 of BoostDocs/PDF


Ignore:
Timestamp:
Feb 8, 2009, 5:17:32 PM (14 years ago)
Author:
John Maddock
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BoostDocs/PDF

    v1 v2  
    11This page details the PDF build of the boost documentation.
    22
    3 SVN commit #51104 to trunk provides the basic support: improved fo.xsl stylesheet, tweaked individual Jamfiles so they find their images etc when being built as a PDF, and adds doc/pdf/Jamfile.v2 to build all boost libraries that can be as individual PDF's.
     3SVN commit [https://svn.boost.org/trac/boost/changeset/51104/trunk 51104] to trunk provides the basic support: improved fo.xsl stylesheet, tweaked individual Jamfiles so they find their images etc when being built as a PDF, and adds doc/pdf/Jamfile.v2 to build all boost libraries that can be as individual PDF's.
    44
    55Beta builds of the PDF's are available from http://boost.cowic.de/rc/pdf/
     6
     7The following default build options have been added to the fo.xsl stylesheet customisation layer:
     8
     9  * No indent on body text (we need all the horrizontal space we can get for code blocks).
     10  * Left and right page margins 0.5in - a little small, but as above we need all the space we can get.
     11  * Paper type is A4 - it's an ISO standard, and just a little smaller than US letter, so should print OK on both.
     12  * Draft mode is turned off so we don't go after draft.png just in case.
     13  * SVG graphics are used for admonishments.
     14  * Default path to search for images (if not overridden in a library's Jamfile) is the SVN repository.
     15
    616
    717TODO's
    818~~~~~~
    919
    10 * Some of the PDF's are badly named: for example the python tutorial is simply "tutorial.pdf", Phoenix is "users_manual.pdf" and Boost.Build is "standalone.pdf".
    11 * The libraries a, b and c do not currently build as PDF's - their XML is invalid, looks like an easy fix though - just tweak their usage of hyperlinks at global (ie not in a section) scope.
    12 * The BoostBook documentation doesn't build as a PDF: Lots of inval XML, this one looks much harder to fix.
    13 * Currently only RenderX's XEP FO processor will build all the docs correctly, Apache FOP is *still* not mature enough :-(
     20  * Some of the PDF's are badly named: for example the python tutorial is simply "tutorial.pdf", Phoenix is "users_manual.pdf" and Boost.Build is "standalone.pdf".
     21  * The libraries a, b and c do not currently build as PDF's - their XML is invalid, looks like an easy fix though - just tweak their usage of hyperlinks at global (ie not in a section) scope.
     22  * The BoostBook documentation doesn't build as a PDF: Lots of inval XML, this one looks much harder to fix.
     23  * Currently only RenderX's XEP FO processor will build all the docs correctly, Apache FOP is *still* not mature enough :-(