diff --git a/doc/boostbook.xml b/doc/boostbook.xml index cd43f38..ed593a1 100644 --- a/doc/boostbook.xml +++ b/doc/boostbook.xml @@ -210,7 +210,7 @@ using boostbook documentation for libraries that do not require Doxygen. To test this, change into the directory $BOOST_ROOT/libs/function/doc and - run the command bjam --v2: it should produce HTML + run the command bjam: it should produce HTML documentation for the Boost.Function library in the html subdirectory. @@ -287,7 +287,7 @@ using fop : FOP_COMMAND To test PDF generation, switch to the directory $BOOST_ROOT/libs/function/doc and - execute the command bjam --v2 pdf. In the + execute the command bjam pdf. In the absence of any errors, Apache FOP will be executed to transform the XSL:FO output of DocBook into a PDF file. @@ -300,8 +300,8 @@ using fop : FOP_COMMAND documentation. First, change to the directory $BOOST_ROOT/doc and remove (or make writable) the .html files in - $BOOST_ROOT/doc/html. Then, run bjam - --v2 to build HTML documentation. You should see several + $BOOST_ROOT/doc/html. Then, run bjam + to build HTML documentation. You should see several warnings like these while DocBook documentation is being built from BoostBook documentation: @@ -316,12 +316,12 @@ Cannot find function named 'next' documentation for Boost will be available in $BOOST_ROOT/doc/html. You can also create HTML documentation in a single (large!) HTML file with the command line - bjam --v2 onehtml, or Unix man pages with the command - line bjam --v2 man. The complete list of output + bjam onehtml, or Unix man pages with the command + line bjam man. The complete list of output formats is listed in . Several output formats can be passed to a single invocation of bjam, e.g., - bjam --v2 html man docbook would generate HTML + bjam html man docbook would generate HTML (multiple files), man pages, and DocBook documentation.