FooBarWidget-mizuho 0.9.0

data/asciidoc/examples/website/index.txt

@@ -0,0 +1,222 @@
+AsciiDoc Home Page
+==================
+
+.{date}: AsciiDoc {revision} Released
+************************************************************************
+Useful additions include:
+
+- http://dblatex.sourceforge.net/[dblatex] is now fully supported by
+  a2x(1) and is the default a2x(1) PDF generator.
+- Added `dvi`, `ps` and `tex` output format options to a2x(1)
+  (courtesy of `dblatex(1)`).
+- URLs and email addresses are recognized without having to use the
+  macro syntax.
+- link:source-highlight-filter.html[Source code paragraphs] make small
+  code examples easier to enter.
+
+Read the link:CHANGELOG.html[CHANGELOG] for a full description of all
+the other additions and changes.
+
+mailto:srackham@gmail.com['Stuart Rackham']
+************************************************************************
+
+Introduction
+------------
+AsciiDoc is a text document format for writing short documents,
+articles, books and UNIX man pages. AsciiDoc files can be translated
+to HTML and DocBook markups using the asciidoc(1) command.
+
+AsciiDoc is highly configurable: both the AsciiDoc source file syntax
+and the backend output markups (which can be almost any type of
+SGML/XML markup) can be customized and extended by the user.
+
+TIP: The pages you are reading were written using AsciiDoc, to view
+the corresponding AsciiDoc source click on the *Page Source* menu item
+in the left hand margin.
+
+
+Overview and Examples
+---------------------
+You write an AsciiDoc document the same way you would write a
+normal text document, there are no markup tags or weird format
+notations. AsciiDoc files are designed to be viewed, edited and
+printed directly or translated to other presentation formats using
+the asciidoc(1) command.
+
+The asciidoc(1) command translates AsciiDoc files to HTML, XHTML and
+DocBook markups.  DocBook can be post-processed to presentation
+formats such as HTML, PDF, DVI, LaTeX, roff, and Postscript using
+readily available Open Source tools.
+
+Example Articles
+~~~~~~~~~~~~~~~~
+- This version of the
+  link:asciidoc.css-embedded.html[AsciiDoc User Guide]
+  was generated by AsciiDoc from
+  link:asciidoc.txt[this AsciiDoc file].
+
+- Here's the link:asciidoc.html[same document] created by first
+  generating DocBook markup using AsciiDoc and then converting the
+  DocBook markup to HTML using 'DocBook XSL Stylesheets'.
+
+- The User Guide again, this time a
+  link:chunked/index.html[chunked version].
+
+- This link:article.txt[AsciiDoc article template] produced
+  this link:article.html[HTML file] and this
+  link:article.pdf[PDF file] via DocBook markup generated by AsciiDoc.
+
+- This link:asciidoc.pdf[PDF formatted User Guide] was generated from
+  asciidoc(1) DocBook output.
+
+Example Books
+~~~~~~~~~~~~~
+AsciiDoc markup supports all the standard DocBook frontmatter and
+backmatter sections (dedication, preface, bibliography, glossary,
+index, colophon) plus footnotes and index entries.
+
+Book::
+    This link:book.txt[AsciiDoc book's] DocBook output
+    produced link:book.html[this HTML file] using the
+    'DocBook XSL Stylesheets'.
+
+Multi-part book::
+    This link:book-multi.txt[multi-part AsciiDoc book's]
+    DocBook output produced link:book-multi.html[this HTML file]
+    using the 'DocBook XSL Stylesheets'.
+
+Example UNIX Man Pages
+~~~~~~~~~~~~~~~~~~~~~~
+HTML formatted AsciiDoc man pages
+link:asciidoc.1.css-embedded.html[with stylesheets] and
+link:asciidoc.1.html[without stylesheets] were generated by AsciiDoc
+from link:asciidoc.1.txt[this file].
+
+This link:asciidoc.1[roff formatted  man page] was generated from
+asciidoc(1) DocBook output using `xsltproc(1)` and DocBook XSL
+Stylesheets.
+  
+Example Web Site
+~~~~~~~~~~~~~~~~
+The link:README-website.html[AsciiDoc website] is included in the
+AsciiDoc distribution (in `./examples/website/`) as example website
+built using AsciiDoc.  See `./examples/website/README-website.txt`.
+
+
+Music Filter
+------------
+A link:music-filter.html[music filter] is included in the distribution
+`./filters/` directory. It translates music in
+http://lilypond.org/[LilyPond] or http://abcnotation.org.uk/[ABC]
+notation to standard classical notation
+
+
+Source Code Highlight Filter
+----------------------------
+A link:source-highlight-filter.html[source code highlight filter] is
+included in the distribution `./filters/` directory.
+
+
+[[X3]]
+Mathematical Formulae
+---------------------
+You can include mathematical formulae in your AsciiDoc documents using
+link:asciimath.html[ASCIIMathML] or link:latexmath.html[LaTeXMathML]
+notation.
+
+
+Vim Syntax Highlighter
+----------------------
+An AsciiDoc syntax highlighter for the Vim text editor is included in
+the AsciiDoc distribution (see 'Appendix F' of the 'AsciiDoc User
+Guide' for details).
+
+.Syntax highlighter screenshot
+image::images/highlighter.png[height=250,caption="",link="images/highlighter.png"]
+
+Dag Wieers has implemented an alternative Vim syntax file for AsciiDoc
+which can be found here
+http://svn.rpmforge.net/svn/trunk/tools/asciidoc-vim/.
+
+
+[[X2]]
+Resources
+---------
+- Check the link:downloads.html[Downloads page] for packaged versions
+  of AsciiDoc.
+- Alex Efros has written an HTML formatted
+  http://powerman.name/doc/asciidoc[AsciiDoc Cheatsheet] using
+  Asciidoc.
+- Thomas Berker has written an
+  http://liksom.info/blog/?q=node/114[AsciiDoc Cheatsheet] in Open
+  Document and PDF formats.
+- The http://www.wikimatrix.org/[WikiMatrix] website has an excellent
+  http://www.wikimatrix.org/syntax.php[web page] that compares the
+  various Wiki markup syntaxes. An interesting attempt at Wiki markup
+  standardization is http://www.wikicreole.org/[CREOLE].
+- Terrence Brannon has written
+  http://www.metaperl.com/asciidoc-el/[AsciiDoc functions for Emacs].
+- The http://xpt.sourceforge.net/[*Nix Power Tools project] has
+  released an http://xpt.sourceforge.net/tools/doc-mode/[AsciiDoc
+  syntax highlighter for Emacs].
+
+- Franck Pommereau has written
+  http://www.univ-paris12.fr/lacl/pommereau/soft/asciidoctest.html[Asciidoctest],
+  a program that doctests snippets of Python code within your Asciidoc
+  documents.
+- The http://remips.sourceforge.net/[ReMIPS] project website has been
+  built using AsciiDoc.
+- Here are some link:asciidoc-docbook-xsl.html[DocBook XSL Stylesheets
+  Notes].
+- Karl Mowatt-Wilson has developed an http://ikiwiki.info/[ikiwiki]
+  plugin for AsciiDoc which he uses to render
+  http://mowson.org/karl[his website].  The plugin is available
+  http://www.mowson.org/karl/colophon/[here] and there is some
+  discussion of the ikiwiki integration
+  http://ikiwiki.info/users/KarlMW/discussion/[here].
+
+
+Blogpost weblog client
+----------------------
+http://srackham.wordpress.com/blogpost-readme/[blogpost] is a
+command-line weblog client for publishing AsciiDoc documents to
+http://wordpress.org/[WordPress] blog hosts. It creates and updates
+weblog posts and pages directly from AsciiDoc source documents.
+
+
+[[X1]]
+LaTeX Backend
+-------------
+An experimental LaTeX backend has been written for AsciiDoc by
+Benjamin Klum.  Benjamin has done a superhuman job (I admit it, I
+didn't think this was doable due to AsciiDoc's SGML/XML bias).
+
+Here's link:latex-backend.html[Benjamin's documentation].
+
+
+Projects using AsciiDoc
+-----------------------
+Here are some projects I know of, if you know of more drop me a line
+and I'll add them to the list.
+
+- The Linux kernel
+  http://www.kernel.org/pub/software/scm/git/docs/git.html[git source
+  code management system].
+- Some documentation about git by Nico Schottelius (in German)
+  http://nico.schotteli.us/papers/linux/git-firmen/.
+- The http://www.netpromi.com/kirbybase_ruby.html[KirbyBase for Ruby]
+  database management system manual.
+- The http://www.selenic.com/mercurial/[Mercurial distributed SCM]
+  uses asciidoc for its man pages.
+- Pascal Rapaz has written a Python script to automate AsciiDoc
+  website generation. You can find it at
+  http://www.rapazp.ch/opensource/tools/asciidoc.html.
+- The http://xpt.sourceforge.net/[*Nix Power Tools project] uses
+  AsciiDoc for documentation and has released an Emacs syntax
+  highlighter (see <<X2,Resources>> above).
+
+
+AsciiDoc version 9
+-----------------
+The next version of AsciiDoc is underway -- details
+link:version9.html[here].

data/asciidoc/examples/website/latex-backend.html

@@ -0,0 +1,640 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+<meta name="generator" content="AsciiDoc 8.2.7" />
+<link rel="stylesheet" href="./xhtml11.css" type="text/css" />
+<link rel="stylesheet" href="./xhtml11-quirks.css" type="text/css" />
+<link rel="stylesheet" href="./layout1.css" type="text/css" />
+<title>LaTeX backend for Asciidoc</title>
+</head>
+<body>
+<div id="layout-banner">
+  <div id="layout-title">AsciiDoc</div>
+  <div id="layout-description">Text based document generation</div>
+</div>
+<table>
+<tr valign="top">
+<td id="layout-menu">
+  <div>&#187;<a href="index.html">Home</a></div>
+  <div>&#187;<a href="manpage.html">Man&nbsp;Page</a></div>
+  <div>&#187;<a href="userguide.html">User&nbsp;Guide</a></div>
+  <div>&#187;<a href="http://powerman.name/doc/asciidoc">Cheatsheet</a></div>
+  <div>&#187;<a href="a2x.1.html">a2x</a></div>
+  <div>&#187;<a href="README.html">README</a></div>
+  <div>&#187;<a href="CHANGELOG.html">ChangeLog</a></div>
+  <div>&#187;<a href="INSTALL.html">Installation</a></div>
+  <div>&#187;<a href="downloads.html">Downloads</a></div>
+  <div>&#187;<a href="faq.html">FAQ</a></div>
+  <div>&#187;<a href="support.html">Support</a></div>
+  <div id="page-source">&#187;<a href="latex-backend.txt">Page&nbsp;Source</a></div>
+</td>
+<td>
+<div id="layout-content">
+<div id="header">
+<h1>LaTeX backend for Asciidoc</h1>
+<span id="author">Benjamin Klum</span><br />
+<span id="email"><tt>&lt;<a href="mailto:benjamin.klum@gmail.com">benjamin.klum@gmail.com</a>&gt;</tt></span><br />
+<span id="revision">version 1.0,</span>
+June 2006
+</div>
+<h2 id="_introduction">Introduction</h2>
+<div class="sectionbody">
+<div class="para"><p>LaTeX backend is a configuration file for Stuart Rackham's <a href="http://www.methods.co.nz/asciidoc/">Asciidoc</a>. It generates high-level LaTeX markup from Asciidoc documents. LaTeX is a document preparation system for TeX which in turn is a popular typesetting system. It is well known for producing excellently typesetted high quality printouts, especially suited for scientific text.</p></div>
+</div>
+<h2 id="_tutorial">Tutorial</h2>
+<div class="sectionbody">
+<div class="para"><p>Getting a ready-to-print document from an Asciidoc document using the LaTeX backend involves at least two steps:</p></div>
+<div class="olist"><ol>
+<li>
+<p>
+Conversion of the Asciidoc document into a LaTeX document (this is done by Asciidoc using the LaTeX backend)
+</p>
+</li>
+<li>
+<p>
+Conversion of the LaTeX document into a PDF document (this is done by the TeX system)
+</p>
+</li>
+</ol></div>
+<div class="para"><p>Try to create a PDF document from the Asciidoc document <tt>article.txt</tt> which resides in the <tt>doc</tt> directory of Asciidoc:</p></div>
+<div class="olist2"><ol>
+<li>
+<p>
+Make a copy of <tt>article.txt</tt> in a directory of your choice, let's call it <tt>latex-test</tt>.
+</p>
+</li>
+<li>
+<p>
+Make sure that all images referenced in <tt>article.txt</tt> exist in <tt>latex-test</tt>. Brute force approach: Copy the whole <tt>images</tt> directory from Asciidoc directory into <tt>latex-test</tt>.
+</p>
+</li>
+<li>
+<p>
+Change directory to <tt>latex-test</tt> and type following commands:
+</p>
+<div class="literalblock">
+<div class="content">
+<pre><tt>asciidoc --unsafe --backend=latex article.txt
+pdflatex article.tex</tt></pre>
+</div></div>
+</li>
+<li>
+<p>
+Now there should be a file <tt>article.pdf</tt> in the <tt>latex-test</tt> directory.
+</p>
+</li>
+</ol></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/important.png" alt="Important" />
+</td>
+<td class="content">
+<div class="ilist"><ul>
+<li>
+<p>
+Asciidoc has to be started in <em>unsafe mode</em> when using LaTeX backend.
+</p>
+</li>
+<li>
+<p>
+Note that some special LaTeX packages are necessary, see <a href="#packageRequirements">here</a>.
+</p>
+</li>
+</ul></div>
+</td>
+</tr></table>
+</div>
+</div>
+<h2 id="_general_notes">General notes</h2>
+<div class="sectionbody">
+<h3 id="_quality_of_latex_output">Quality of LaTeX output</h3><div style="clear:left"></div>
+<div class="para"><p>High-level LaTeX is not very straightforward to generate. Therefore there's no guarantee that the generated output is valid and compiles successfully. At all, this backend should be considered as rather experimental.  You should have been already in touch with LaTeX in order to use the backend effectively because LaTeX compilation errors can be really nasty.</p></div>
+<div class="para"><p>Nevertheless good results can be achieved by using LaTeX backend. Try for example to compile Stuart Rackham's Asciidoc documentation, a rather large document. It should compile without problems. However, the code filter might have to be reconfigured for the code filter example to work.</p></div>
+<h3 id="_configuration_file_customization">Configuration file customization</h3><div style="clear:left"></div>
+<div class="para"><p>Like every other Asciidoc backend the LaTeX backend can be customized easily to fit the user's needs. Actually it is very important to have this option since LaTeX doesn't have a companion language like CSS which allows to put styling information in a separate file. Read more about the LaTeX backend configuration file <a href="#configurationFile">here</a>.</p></div>
+<h3 id="_output_optimization">Output optimization</h3><div style="clear:left"></div>
+<div class="para"><p>The LaTeX output is optimized for creating PDF documents using <em>pdflatex</em>.</p></div>
+<h3 id="unicodeSupport">Unicode support</h3><div style="clear:left"></div>
+<div class="para"><p>Unfortunately TeX/LaTeX does not have native unicode support. The package <em>ucs</em> adds elementary unicode support by introducing UTF-8 input encoding recognition and by defining lookup tables which contain the corresponding LaTeX commands for unicode characters. But these lookup tables are far from being complete. When a unicode character is found which is not defined in the lookup tables an error is raised by the TeX/LaTeX compiler. Note that TeX/LaTeX compilation errors caused by missing unicode character definitions are not fatal, that means the result is probably readable but undefined unicode characters are replaced with <tt>[U+&#8230;]</tt>. You may (de)activate the recognition of escaped unicode characters. See the <a href="#latex-recognize-escaped-unicode">[latex-recognize-escaped-unicode]</a> backend option.</p></div>
+</div>
+<h2 id="_backend_specific_features">Backend specific features</h2>
+<div class="sectionbody">
+<h3 id="_special_sections">Special sections</h3><div style="clear:left"></div>
+<div class="para"><p>LaTeX backend supports the following special sections and replaces them with corresponding LaTeX commands or environments:</p></div>
+<div class="ilist"><ul>
+<li>
+<p>
+Abstract (only for document type <em>article</em>)
+</p>
+</li>
+<li>
+<p>
+Dedication (only for document type <em>book</em>)
+</p>
+</li>
+<li>
+<p>
+Index
+</p>
+</li>
+<li>
+<p>
+Bibliography (only when the attribute <em>latex-use-bibliography-environment</em> is set)
+</p>
+</li>
+<li>
+<p>
+Appendix
+</p>
+</li>
+<li>
+<p>
+Contents
+</p>
+</li>
+</ul></div>
+<h3 id="internalCrossReferences">Internal cross references</h3><div style="clear:left"></div>
+<div class="para"><p>Macros for internal cross references have been extended by the attribute <em>style</em>.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>xref:&lt;id&gt;[&lt;caption&gt;, style=&lt;style&gt;]</tt></pre>
+</div></div>
+<div class="para"><p>or</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>&lt;&lt;&lt;id&gt;,&lt;caption&gt;,&lt;style&gt;&gt;&gt;</tt></pre>
+</div></div>
+<div class="para"><p>The additional attribute <em>style</em> can have following values:</p></div>
+<div class="vlist"><dl>
+<dt>
+page
+</dt>
+<dd>
+<p>
+Let's LaTeX print the page number of the referenced anchor.
+</p>
+</dd>
+<dt>
+ref
+</dt>
+<dd>
+<p>
+Let's LaTeX print the number of the section, subsection, figure, table or theorem the referenced anchor resides.
+</p>
+</dd>
+<dt>
+autoref
+</dt>
+<dd>
+<p>
+Let's LaTeX print the number of the section, subsection, figure, table or theorem the referenced anchor resides preceded with a contextual label.
+</p>
+</dd>
+<dt>
+cite
+</dt>
+<dd>
+<p>
+Let's LaTeX interprete this reference as a reference to a bibliography entry. If the attribute <em>latex-use-bibliography-environment</em> is set, references with <em>cite</em> style as well as their corresponding bibliography anchors are presented as automatically generated numbers.
+</p>
+</dd>
+</dl></div>
+<div class="para"><p>If the <em>style</em> attribute is not set the reference is printed the common way.</p></div>
+<h3 id="_options">Options</h3><div style="clear:left"></div>
+<div class="para"><p>LaTeX document generation is influenced by the following attributes:</p></div>
+<div class="vlist"><dl>
+<dt>
+latex-table-rowlimit
+</dt>
+<dd>
+<p>
+The maximum number of rows for typesetting tables using the <em>tabular</em> environment. If a table has more rows than <em>latex-table-rowlimit</em>, <em>longtable</em> environment is used instead of <em>tabular</em> environment. <em>longtable</em> environment supports tables spanning over several pages.
+</p>
+</dd>
+<dt>
+latex-use-bibliography-environment
+</dt>
+<dd>
+<p>
+If <em>latex-use-bibliography-environment</em> is defined, <em>thebibliography</em> environment is used for the bibliography section. As a result bibliography entries are automatically numbered. Note that this works only if the bibliography section contains exclusively bibliography list items which start with a bibliography entry ([[[&#8230;]]]). Otherwise a TeX/LaTeX compilation error will occur. In order to display bibliography references correctly their <em>style</em> attribute must be set to <em>cite</em>. For more information see <a href="#internalCrossReferences">Internal cross references</a>.
+</p>
+</dd>
+<dt>
+latex-indent-paragraphs
+</dt>
+<dd>
+<p>
+If <em>latex-indent-paragraphs</em> is defined, the first line of paragraphs will be indented. By default LaTeX backend prevents paragraph indentation and prints paragraphs with preceding vertical space.
+</p>
+</dd>
+<dt>
+<a id="latex-recognize-escaped-unicode"></a> latex-recognize-escaped-unicode
+</dt>
+<dd>
+<p>
+If <em>latex-recognize-escaped-unicode</em> is defined, escaped unicode characters (e.g. <tt><span>{amp}#960;</span></tt> or <tt><span>{amp}#x3C0;</span></tt>) will be recognized. This can lead to LaTeX compilation errors since LaTeX unicode support is only rudimentary. For more information see <a href="#unicodeSupport">Unicode support</a>.
+</p>
+</dd>
+<dt>
+latex-use-custom-list-items
+</dt>
+<dd>
+<p>
+If <em>latex-use-custom-list-items</em> is defined, lists will be bulleted or enumerated the way you have typed them in the original Asciidoc document. That means, <tt>*</tt> turns into a circle bullet, <tt>-</tt> turns into a dash, <tt>.</tt> turns into a number and <tt>..</tt> turns into a letter. Otherwise LaTeX will use different bullets and enumeration characters depending on the level of nesting.
+</p>
+</dd>
+<dt>
+latex-use-colored-tables
+</dt>
+<dd>
+<p>
+If <em>latex-use-colored-tables</em> is defined, tables will be printed colored.
+</p>
+</dd>
+<dt>
+latex-use-running-title-headings
+</dt>
+<dd>
+<p>
+If <em>latex-use-running-title-headings</em> is defined, <em>pagestyle</em> will be set to <em>headings</em> which results in running titles in the head.
+</p>
+</dd>
+<dt>
+latex-use-colored-sidebar-blocks
+</dt>
+<dd>
+<p>
+If <em>latex-use-colored-sidebar-blocks</em> is defined, sidebar block content will be put in a color box instead of being indented by a vertical bar.
+</p>
+</dd>
+<dt>
+icons
+</dt>
+<dd>
+<p>
+Link admonition paragraph and admonition block icon images and badge images. By default icons is undefined and text is used in place of icon images.
+</p>
+</dd>
+<dt>
+encoding
+</dt>
+<dd>
+<p>
+Set the input and output document character set encoding. Currently <tt>ISO-8859-1</tt> and <tt>UTF-8</tt> are supported.
+</p>
+</dd>
+</dl></div>
+</div>
+<h2 id="_requirements">Requirements</h2>
+<div class="sectionbody">
+<h3 id="_general">General</h3><div style="clear:left"></div>
+<div class="para"><p>The following software is necessary for using the LaTeX backend:</p></div>
+<div class="ilist"><ul>
+<li>
+<p>
+An up-to-date version of <a href="http://www.methods.co.nz/asciidoc/">Asciidoc</a>
+</p>
+</li>
+<li>
+<p>
+An up-to-date TeX distribution, e.g.:
+</p>
+<div class="ilist"><ul>
+<li>
+<p>
+<a href="http://www.miktex.org/">MiKTeX</a> for Windows
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.tug.org/tetex/">teTeX</a> for Linux
+</p>
+</li>
+</ul></div>
+</li>
+</ul></div>
+<h3 id="packageRequirements">TeX/LaTeX Package requirements</h3><div style="clear:left"></div>
+<div class="para"><p>LaTeX backend makes use of some LaTeX specialities which don't belong to a minimal TeX/LaTeX distribution. However, I took special care not to employ exotic packages. Hence the following packages should be available in most package repositories. The table is not complete yet because I don't know the package names for all TeX distributions.</p></div>
+<div class="tableblock">
+<table rules="all"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="160" />
+<col width="160" />
+<col width="160" />
+<col width="160" />
+<col width="160" />
+<thead>
+  <tr>
+    <th align="left">
+    Speciality
+    </th>
+    <th align="left">
+    MiKTeX package name
+    </th>
+    <th align="left">
+    teTeX package name
+    </th>
+    <th align="left">
+    TeX Live package name
+    </th>
+    <th align="left">
+    Description
+    </th>
+  </tr>
+</thead>
+<tbody valign="top">
+  <tr>
+    <td align="left">
+    KOMA-Script
+    </td>
+    <td align="left">
+    koma-script
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    LaTeX backend uses the document classes <em>scrartcl</em> and <em>scrbook</em> as well as some other specialities defined in the <em>KOMA-Script</em> package, e.g. the commands <tt>\addmargin{}</tt> and <tt>\minisec{}</tt>.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    xcolor.sty
+    </td>
+    <td align="left">
+    xcolor
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    Used to produce colored boxes and tables.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    colortbl.sty
+    </td>
+    <td align="left">
+    colortbl
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    Used to produce colored tables.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    type1ec.sty
+    </td>
+    <td align="left">
+    cm-super
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    Enables high quality fonts for PDF output.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    hyperref.sty
+    </td>
+    <td align="left">
+    hyperref
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    Extensive support for hypertext in PDF documents.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    enumerate.sty
+    </td>
+    <td align="left">
+    tools
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    When <em>latex-use-custom-list-items</em> is defined this package is used for determining the enumeration character.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    graphicx.sty
+    </td>
+    <td align="left">
+    graphics
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    Used for including images.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    longtable.sty
+    </td>
+    <td align="left">
+    tools
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    Enables page spanning tables.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    ucs.sty
+    </td>
+    <td align="left">
+    unicode
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    Enables support for unicode characters.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    textcomp
+    </td>
+    <td align="left">
+    ltxbase
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    Used for printing various symbols like arrows. Should be already installed.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    alltt
+    </td>
+    <td align="left">
+    ltxbase
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    Used in literal-like blocks for retaining line and whitespace formatting. Should be already installed.
+    </td>
+  </tr>
+  <tr>
+    <td align="left">
+    listings.sty
+    </td>
+    <td align="left">
+    listings
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    </td>
+    <td align="left">
+    Used for listing blocks.
+    </td>
+  </tr>
+</tbody>
+</table>
+</div>
+</div>
+<h2 id="configurationFile">About the LaTeX backend configuration file</h2>
+<div class="sectionbody">
+<div class="para"><p>An important note for people who want to adapt the LaTeX backend configuration file to their own needs:</p></div>
+<div class="para"><p>LaTeX markup has a lot of special characters, most importantly <tt>\</tt>, <tt>{</tt>, <tt>}</tt>. In order to make things less complicated, I changed the default substitution order (see entry <em>subsnormal</em> in the <tt>[miscellaneous]</tt> section). In contrast to the backends <em>docbook</em> and <em>xhtml11</em>, the <em>specialcharacters</em> substitution is applied very late. As a result all special characters produced by <em>quotes</em>, <em>specialwords</em>, <em>replacements</em>, <em>attributes</em> and <em>macros</em> become escaped at the end. If you don't want special characters in the corresponding sections to get escaped, you've to use following symbols instead of the special characters.</p></div>
+<div class="ilist"><ul>
+<li>
+<p>
+<tt><span>!..backslash..!</span></tt> instead of <tt>\</tt>
+</p>
+</li>
+<li>
+<p>
+<tt><span>!..braceleft..!</span></tt> instead of <tt>{</tt>
+</p>
+</li>
+<li>
+<p>
+<tt><span>!..braceright..!</span></tt> instead of <tt>}</tt>
+</p>
+</li>
+</ul></div>
+<div class="para"><p>For more special characters take a look in the <tt>[replacements2]</tt> sections. <tt>[replacements2]</tt> section is responsible for replacing the symbols with their corresponding special characters.</p></div>
+</div>
+<h2 id="_ideas">Ideas</h2>
+<div class="sectionbody">
+<h3 id="_code_listing_block">Code listing block</h3><div style="clear:left"></div>
+<div class="para"><p>For creating highlighted code listings I suggest the use of <a href="http://www.andre-simon.de/">Highlight</a> or <a href="http://www.gnu.org/software/src-highlite/">GNU Source Highlight</a>. Both are suited for use as Asciidoc filters.</p></div>
+</div>
+<h2 id="_known_bugs">Known Bugs</h2>
+<div class="sectionbody">
+<div class="ilist"><ul>
+<li>
+<p>
+Sometimes LaTeX backend handles things differently from the default backends
+</p>
+</li>
+<li>
+<p>
+A lot of little bugs
+</p>
+</li>
+</ul></div>
+</div>
+<h2 id="_todo_list">Todo List</h2>
+<div class="sectionbody">
+<div class="ilist"><ul>
+<li>
+<p>
+Remove bugs
+</p>
+</li>
+<li>
+<p>
+Support for <em>grid</em> attribute in tables
+</p>
+</li>
+<li>
+<p>
+Better looking tables
+</p>
+</li>
+<li>
+<p>
+Option for squeezing output (smaller lists)
+</p>
+</li>
+<li>
+<p>
+Support for different languages (That would be a nice feature for Asciidoc in general)
+</p>
+</li>
+<li>
+<p>
+Option for switching titlepage on and off
+</p>
+</li>
+</ul></div>
+</div>
+<div id="footer">
+<div id="footer-text">
+Version 1.0<br />
+Last updated 2008-07-04 23:29:27 NZDT
+</div>
+<div id="footer-badges">
+<a href="http://validator.w3.org/check?uri=referer">
+  <img style="border:none; width:88px; height:31px;"
+       src="http://www.w3.org/Icons/valid-xhtml11"
+       alt="Valid XHTML 1.1!" />
+</a>
+<a href="http://jigsaw.w3.org/css-validator/check/referer">
+  <img style="border:none; width:88px; height:31px;"
+       src="http://jigsaw.w3.org/css-validator/images/vcss"
+       alt="Valid CSS!" />
+</a>
+<a href="http://www.mozilla.org/products/firefox/">
+  <img style="border:none; width:110px; height:32px;"
+       src="http://www.spreadfirefox.com/community/images/affiliates/Buttons/110x32/safer.gif"
+       alt="Get Firefox!" />
+</a>
+</div>
+</div>
+</div>
+</td>
+</tr>
+</table>
+</body>
+</html>