_res/" by default) containing all the
resources referenced by the processed pages.Whatever the file layout of the input HTML pages and their resources, all the files and directories are always created in a single output directory, which makes this output directory self-contained.
In addition to the processed
pages, the Processor automatically creates an HTML page (called
"_toc_frame.html" by default) containing a table of
contents and the manifest of all the resources found in the resource
directory (in the form of
<link href="XXX" rel="resource" type="YYY"/>
elements).
The Processor also automatically creates an HTML page
(called "_frameset.html" by default) containing a frameset. The only purpose of this
frameset is to be able to quickly navigate the output of
the Processor when testing and debugging.
_toc_frame.html" and "_frameset.html" are
discarded._toc_frame.html" by the means of the
xsl/epub/epub.xsl stylesheet and then archiving[1] the contents of
the output directory._toc_frame.html" by the means of the
xsl/webhelp/webhelp.xsl stylesheet and then processing the
contents of the output directory using XMLmind
Web Help Compiler.xsl/fo/fo.xsl stylesheet. After
that, it's up to an XSL-FO processor — Apache
FOP, RenderX
XEP or Antenna House Formatter for the PostScript and
PDF formats, XMLmind XSL-FO Converter for the RTF, WML, DOCX
and ODT formats— to create the output file.apply-css-styles) and stored in
processing-instructions (<?css-styles?>) prior to be
transformed by the xsl/fo/fo.xsl stylesheet. This
preparatory step is implemented by the "CSS to XSL-FO properties"
component depicted in the above figure.