<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet
 href="urn:x-daps:xslt:profiling:docbook45-profile.xsl"
 type="text/xml"
 title="Profiling step"?>
<!DOCTYPE tgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.docbook.org/xml/4.5/docbookx.dtd"
[<!ENTITY % entities SYSTEM "entity-decl.ent">
%entities;
]>
<tgroup cols="2">
    <colspec colnum="1" colname="1" colwidth="30*"/>
    <colspec colnum="2" colname="2" colwidth="70*"/>
    <thead>
     <row>
      <entry>
       <para>
         Subcommand
        </para>
      </entry>
      <entry>
       <para>
         Output/Note
        </para>
      </entry>
     </row>
    </thead>
    <tbody>
     <row>
      <entry>
       <para>
         pdf
        </para>
      </entry>
      <entry>
       <para>
         Creates a color PDF. Open the result in a
         PDF viewer.
        </para>
       <para>
        Requires an FO formatter.
        <!--It is also possible to create one PDF
        containing all the contents of a <sgmltag>set</sgmltag>&mdash; however,
        for large documentation projects you might run into problems with the
         java memory stack.-->
       </para>
      </entry>
      </row>
     <row>
      <entry>
       <para>
         pdf --grayscale
        </para>
      </entry>
      <entry>
       <para>
         Creates a black-and-white PDF. 
         Open the result in a PDF viewer.
       </para>
      <para>
        Requires an FO formatter. All color images are automatically
        converted to grayscale images. If you need a PDF for a printing shop, add the 
        <option>--cropmarks</option> option. Creation of crop marks is currently only
        supported by the XEP FO formatter. 
       </para>
      </entry>
      </row>
     <row>
      <entry>
       <para>
         html
        </para>
      </entry>
      <entry>
       <para>
         Creates a subdirectory containing individual HTML files for all
         chapters of a book (including also preface, glossary or appendix
         files). The HTML files are named according to the ID of the
         respective root element.
         Open the generated <filename>index.html</filename> file in a Web
         browser to view the generated HTML from the starting point (ROOTID
         of the top-level element).
        </para>
       <para>
         Images and CSS files are only linked in the resulting directory
         that contains the HTML files. To copy these files to the same
         location as the HTML files, use the <option>--static</option>
         option. This is useful for creating distributable HTML builds.
       </para>
       </entry>
      </row>
     <row>
      <entry>
       <para>
         html --single
        </para>
      </entry>
      <entry>
       <para>
         Creates a single HTML file, named after the &dc; file used to
         create the output. Open the generated <filename>*.html</filename>
         file in a Web browser.
        </para>
       <para>
         Single HTML files are more convenient for full text searches.
         Images and CSS files are only linked in the resulting directory
         that contains the HTML files. To copy these files to the same
         location like the HTML files, use the <option>--static</option>
         option. This is useful for creating distributable HTML builds.
       </para>
       </entry>
      </row>
     <row>
      <entry>
       <para>
         epub
        </para>
      </entry>
      <entry>
       <para>
         Creates an &epub; 2 document. Open the resulting file in a portable e-book
         reader (or with a software like Calibre).
       </para>
       <para>If you need an &epub; 3 document, add the <option>--epub3</option> option.</para>
       <para>
        <remark>taroth 2012-03-23: check with fs/toms: only books? what about
        conversion of articles to epub?</remark>
        <remark>toms, 2012-04-15: This seems to be an issue with the
           current DocBook stylesheets. Need to check this.</remark>
       </para>
       </entry>
     </row>
     <row>
      <entry>
       <para>
        mobi
       </para>
      </entry>
      <entry>
    <para>Creates an Amazon Kindle e-book in Mobipocket format. Open the resulting file in a portable
     e-book reader (or with a software like Calibre).</para>
    <para>Requires Calibre. &dapsacr; first generates an &epub; file which is then converted
     to <filename>*.mobi</filename> format with Calibre.</para>
      </entry>
     </row>
     <row>
      <entry>
       <para>
         webhelp
       </para>
      </entry>
      <entry>
       <para>
         Creates a DocBook &webh; output. Open the resulting
         <filename>index.html</filename> file in a Web browser to view the
         generated document from the starting point (ROOTID of the top-level
         element).
        </para>
       <para>
         Experimental feature. Requires the most recent version of the DocBook
         stylesheets. DocBook &webh; consists of HTML pages with an
         additional pane, featuring a table of contents and a search
         function. The table of contents can be expanded and collapsed, and
         is automatically synchronized with the contents pane. The search
         function orders the search results so that the most relevant
         results are listed first.
        </para>
      </entry>
     </row>
     <row>
      <entry>
       <para>
         text
        </para>
      </entry>
      <entry>
       <para>
         Creates an ASCII text output. Open the resulting file in a text editor.
        </para>
       <para>
         All images are removed from the output, but their location is
         indicated in the text by the respective image base name printed in
         square brackets. A table of contents is automatically generated and
         is inserted at the beginning of the text document.
        </para>
      </entry>
     </row>
     <row>
      <entry>
       <para>
         man
        </para>
      </entry>
      <entry>
       <para>
         Creates one or multiple man pages.
        </para>
       <para>
         To create man pages, your XML files must contain at least one
         <sgmltag>refentry</sgmltag>&mdash;be it in a
         <sgmltag>chapter</sgmltag>, <sgmltag>appendix</sgmltag>, or
         collected in a <sgmltag>reference</sgmltag> element. When
         processing a DocBook document with multiple
         <sgmltag>refentry</sgmltag> elements (regardless where they
         appear), &dapsacr; generates one man page file per
         <sgmltag>refentry</sgmltag> element. All other parts of the
         document will be ignored.
        </para>
<!--taroth 2012-04-11: additional
        information to be covered in User Guide: The file name for each man
        page is generated from refentry content elements. The file name prefix
        is the refname, and the suffix is the manvolnum from within the
        refmeta element. If you are processing many refentrys from the same
        document, make sure they will all produce unique file names, or else
        any duplicates will overwrite each other.-->
      </entry>
     </row>
    <!--taroth 2013-01-15: commented jsp and mediawiki format on behalf of
    toms&apos; feedback, too exotic for most users-->
    <!-- <row>
      <entry>
       <para>
         jsp
        </para>
      </entry>
      <entry>
       <para>
         Creates Java Server Pages (JSP files). The generated
         <filename>jsp</filename> subdirectory contains individual JSP files
         for all chapters of a book (including also preface, glossary or
         appendix files). The JSP files are named according to the ID of the
         respective root element.
       </para>
       <para>
         A JSP file is an HTML page containing a reference to Java servlets
         or Java Server Side Applets.
        </para>
      </entry>
     </row>
     <row>
      <entry>
       <para>
         wiki
        </para>
      </entry>
      <entry>
       <para>
         Creates a MediaWiki output in a single file. Open the result in a
         text or MediaWiki editor, and use it as raw input for a MediaWiki
         article.
        </para>
        <para>
         Experimental feature. The output is very basic: Section titles are
         converted in headlines according to their hierarchy, itemized
         lists, ordered lists and <sgmltag>screen</sgmltag> elements are
         converted to the respective MediaWiki elements.
        </para>
      </entry>
     </row>-->
    </tbody>
   </tgroup>
