RubyGems - FooBarWidget-mizuho - Versions diffs - 0.9.0 - Mend

FooBarWidget-mizuho 0.9.0

Files changed (175) hide show

data/LICENSE.txt +20 -0
data/README.markdown +68 -0
data/Rakefile +9 -0
data/asciidoc/BUGS +34 -0
data/asciidoc/BUGS.txt +28 -0
data/asciidoc/CHANGELOG +1585 -0
data/asciidoc/CHANGELOG.txt +1595 -0
data/asciidoc/COPYING +339 -0
data/asciidoc/COPYRIGHT +18 -0
data/asciidoc/INSTALL +82 -0
data/asciidoc/INSTALL.txt +71 -0
data/asciidoc/README +46 -0
data/asciidoc/README.txt +36 -0
data/asciidoc/a2x +641 -0
data/asciidoc/asciidoc.conf +404 -0
data/asciidoc/asciidoc.py +4255 -0
data/asciidoc/common.aap +9 -0
data/asciidoc/dblatex/asciidoc-dblatex.sty +18 -0
data/asciidoc/dblatex/asciidoc-dblatex.xsl +17 -0
data/asciidoc/dblatex/dblatex-readme.txt +22 -0
data/asciidoc/doc/a2x.1 +246 -0
data/asciidoc/doc/a2x.1.txt +195 -0
data/asciidoc/doc/article.css-embedded.html +579 -0
data/asciidoc/doc/article.html +62 -0
data/asciidoc/doc/article.pdf +0 -0
data/asciidoc/doc/article.txt +124 -0
data/asciidoc/doc/asciidoc-revhistory.xml +27 -0
data/asciidoc/doc/asciidoc.1 +161 -0
data/asciidoc/doc/asciidoc.1.css-embedded.html +562 -0
data/asciidoc/doc/asciidoc.1.css.html +212 -0
data/asciidoc/doc/asciidoc.1.html +190 -0
data/asciidoc/doc/asciidoc.1.txt +118 -0
data/asciidoc/doc/asciidoc.conf +8 -0
data/asciidoc/doc/asciidoc.css-embedded.html +7954 -0
data/asciidoc/doc/asciidoc.css.html +7553 -0
data/asciidoc/doc/asciidoc.dict +673 -0
data/asciidoc/doc/asciidoc.html +3502 -0
data/asciidoc/doc/asciidoc.txt +4757 -0
data/asciidoc/doc/asciimath.txt +47 -0
data/asciidoc/doc/book-multi.css-embedded.html +575 -0
data/asciidoc/doc/book-multi.html +72 -0
data/asciidoc/doc/book-multi.txt +159 -0
data/asciidoc/doc/book.css-embedded.html +585 -0
data/asciidoc/doc/book.html +60 -0
data/asciidoc/doc/book.txt +133 -0
data/asciidoc/doc/customers.csv +18 -0
data/asciidoc/doc/faq.txt +262 -0
data/asciidoc/doc/latex-backend.html +224 -0
data/asciidoc/doc/latex-backend.txt +193 -0
data/asciidoc/doc/latexmath.txt +35 -0
data/asciidoc/doc/main.aap +293 -0
data/asciidoc/doc/music-filter.html +513 -0
data/asciidoc/doc/music-filter.pdf +0 -0
data/asciidoc/doc/music-filter.txt +158 -0
data/asciidoc/doc/source-highlight-filter.html +183 -0
data/asciidoc/doc/source-highlight-filter.pdf +0 -0
data/asciidoc/doc/source-highlight-filter.txt +174 -0
data/asciidoc/docbook-xsl/asciidoc-docbook-xsl.txt +71 -0
data/asciidoc/docbook-xsl/chunked.xsl +19 -0
data/asciidoc/docbook-xsl/common.xsl +67 -0
data/asciidoc/docbook-xsl/fo.xsl +117 -0
data/asciidoc/docbook-xsl/htmlhelp.xsl +17 -0
data/asciidoc/docbook-xsl/manpage.xsl +28 -0
data/asciidoc/docbook-xsl/shaded-literallayout.patch +32 -0
data/asciidoc/docbook-xsl/xhtml.xsl +14 -0
data/asciidoc/docbook.conf +606 -0
data/asciidoc/examples/website/CHANGELOG.html +3828 -0
data/asciidoc/examples/website/INSTALL.html +163 -0
data/asciidoc/examples/website/README-website.html +129 -0
data/asciidoc/examples/website/README-website.txt +29 -0
data/asciidoc/examples/website/README.html +125 -0
data/asciidoc/examples/website/a2x.1.html +395 -0
data/asciidoc/examples/website/asciidoc-docbook-xsl.html +165 -0
data/asciidoc/examples/website/asciimath.html +157 -0
data/asciidoc/examples/website/build-website.sh +25 -0
data/asciidoc/examples/website/downloads.html +219 -0
data/asciidoc/examples/website/downloads.txt +98 -0
data/asciidoc/examples/website/faq.html +372 -0
data/asciidoc/examples/website/index.html +398 -0
data/asciidoc/examples/website/index.txt +222 -0
data/asciidoc/examples/website/latex-backend.html +640 -0
data/asciidoc/examples/website/latexmath.html +119 -0
data/asciidoc/examples/website/layout1.conf +161 -0
data/asciidoc/examples/website/layout1.css +65 -0
data/asciidoc/examples/website/layout2.conf +158 -0
data/asciidoc/examples/website/layout2.css +93 -0
data/asciidoc/examples/website/manpage.html +266 -0
data/asciidoc/examples/website/music-filter.html +242 -0
data/asciidoc/examples/website/music1.abc +12 -0
data/asciidoc/examples/website/music1.png +0 -0
data/asciidoc/examples/website/music2.ly +9 -0
data/asciidoc/examples/website/music2.png +0 -0
data/asciidoc/examples/website/source-highlight-filter.html +251 -0
data/asciidoc/examples/website/support.html +78 -0
data/asciidoc/examples/website/support.txt +5 -0
data/asciidoc/examples/website/userguide.html +7597 -0
data/asciidoc/examples/website/version9.html +143 -0
data/asciidoc/examples/website/version9.txt +48 -0
data/asciidoc/filters/code-filter-readme.txt +37 -0
data/asciidoc/filters/code-filter-test-c++.txt +7 -0
data/asciidoc/filters/code-filter-test.txt +15 -0
data/asciidoc/filters/code-filter.conf +8 -0
data/asciidoc/filters/code-filter.py +239 -0
data/asciidoc/filters/music-filter-test.txt +40 -0
data/asciidoc/filters/music-filter.conf +40 -0
data/asciidoc/filters/music2png.py +189 -0
data/asciidoc/filters/source-highlight-filter-test.txt +19 -0
data/asciidoc/filters/source-highlight-filter.conf +100 -0
data/asciidoc/help.conf +213 -0
data/asciidoc/html4.conf +363 -0
data/asciidoc/images/highlighter.png +0 -0
data/asciidoc/images/icons/README +5 -0
data/asciidoc/images/icons/callouts/1.png +0 -0
data/asciidoc/images/icons/callouts/10.png +0 -0
data/asciidoc/images/icons/callouts/11.png +0 -0
data/asciidoc/images/icons/callouts/12.png +0 -0
data/asciidoc/images/icons/callouts/13.png +0 -0
data/asciidoc/images/icons/callouts/14.png +0 -0
data/asciidoc/images/icons/callouts/15.png +0 -0
data/asciidoc/images/icons/callouts/2.png +0 -0
data/asciidoc/images/icons/callouts/3.png +0 -0
data/asciidoc/images/icons/callouts/4.png +0 -0
data/asciidoc/images/icons/callouts/5.png +0 -0
data/asciidoc/images/icons/callouts/6.png +0 -0
data/asciidoc/images/icons/callouts/7.png +0 -0
data/asciidoc/images/icons/callouts/8.png +0 -0
data/asciidoc/images/icons/callouts/9.png +0 -0
data/asciidoc/images/icons/caution.png +0 -0
data/asciidoc/images/icons/example.png +0 -0
data/asciidoc/images/icons/home.png +0 -0
data/asciidoc/images/icons/important.png +0 -0
data/asciidoc/images/icons/next.png +0 -0
data/asciidoc/images/icons/note.png +0 -0
data/asciidoc/images/icons/prev.png +0 -0
data/asciidoc/images/icons/tip.png +0 -0
data/asciidoc/images/icons/up.png +0 -0
data/asciidoc/images/icons/warning.png +0 -0
data/asciidoc/images/smallnew.png +0 -0
data/asciidoc/images/tiger.png +0 -0
data/asciidoc/install.sh +55 -0
data/asciidoc/javascripts/ASCIIMathML.js +938 -0
data/asciidoc/javascripts/LaTeXMathML.js +1223 -0
data/asciidoc/javascripts/toc.js +69 -0
data/asciidoc/lang-es.conf +15 -0
data/asciidoc/latex.conf +663 -0
data/asciidoc/linuxdoc.conf +285 -0
data/asciidoc/math.conf +50 -0
data/asciidoc/stylesheets/docbook-xsl.css +271 -0
data/asciidoc/stylesheets/xhtml-deprecated-manpage.css +21 -0
data/asciidoc/stylesheets/xhtml-deprecated.css +247 -0
data/asciidoc/stylesheets/xhtml11-manpage.css +18 -0
data/asciidoc/stylesheets/xhtml11-quirks.css +49 -0
data/asciidoc/stylesheets/xhtml11.css +284 -0
data/asciidoc/t.conf +20 -0
data/asciidoc/text.conf +16 -0
data/asciidoc/vim/ftdetect/asciidoc_filetype.vim +53 -0
data/asciidoc/vim/syntax/asciidoc.vim +139 -0
data/asciidoc/xhtml-deprecated-css.conf +235 -0
data/asciidoc/xhtml-deprecated.conf +351 -0
data/asciidoc/xhtml11-quirks.conf +57 -0
data/asciidoc/xhtml11.conf +514 -0
data/bin/mizuho +40 -0
data/lib/mizuho/chapter.rb +54 -0
data/lib/mizuho/generator.rb +106 -0
data/lib/mizuho/heading.rb +46 -0
data/lib/mizuho/parser.rb +99 -0
data/lib/mizuho/template.rb +50 -0
data/mizuho.gemspec +34 -0
data/templates/asciidoc.css +358 -0
data/templates/asciidoc.html.erb +86 -0
data/templates/manualsonrails.css +165 -0
data/templates/manualsonrails.html.erb +97 -0
data/test/parser_spec.rb +190 -0
data/test/spec_helper.rb +43 -0
metadata +234 -0

data/asciidoc/examples/website/faq.html ADDED Viewed

@@ -0,0 +1,372 @@
+<!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" />
+<script type="text/javascript">
+/*<![CDATA[*/
+window.onload = function(){generateToc(2)}
+/*]]>*/
+</script>
+<script type="text/javascript" src="./toc.js"></script>
+<title>AsciiDoc Frequently Asked Questions</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="faq.txt">Page&nbsp;Source</a></div>
+</td>
+<td>
+<div id="layout-content">
+<div id="header">
+<h1>AsciiDoc Frequently Asked Questions</h1>
+</div>
+<div id="toc">
+  <div id="toctitle">Table of Contents</div>
+  <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
+</div>
+<div id="preamble">
+<div class="sectionbody">
+<div class="para"><p>An embryonic <em>AsciiDoc</em> FAQ.</p></div>
+</div>
+</div>
+<h2 id="_how_can_i_preserve_paragraph_line_boundaries">1. How can I preserve paragraph line boundaries?</h2>
+<div class="sectionbody">
+<div class="para"><p>Apply the The <em>verse</em> paragraph style, the rendered text preserves
+line boundaries and is useful for lyrics and poems.  For example:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>[verse]
+Consul *necessitatibus* per id,
+consetetur, eu pro everti postulant
+homero verear ea mea, qui.</tt></pre>
+</div></div>
+</div>
+<h2 id="_how_can_i_include_non_breaking_space_characters">2. How can I include non-breaking space characters?</h2>
+<div class="sectionbody">
+<div class="para"><p>The predefined <tt>{nbsp}</tt> attribute reference will be replaced by a
+non-breaking space character.</p></div>
+</div>
+<h2 id="_how_do_i_include_spaces_in_url_addresses">3. How do I include spaces in URL addresses?</h2>
+<div class="sectionbody">
+<div class="para"><p>URL inline macro targets (addresses) cannot contain white space
+characters. If you need spaces encode them as <tt>%20</tt>. For example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>image:large%20image.png[]
+http://www.foo.bar.com/an%20example%20document.html</tt></pre>
+</div></div>
+</div>
+<h2 id="_how_can_i_get_asciidoc_to_assign_the_correct_docbook_language_attribute">4. How can I get AsciiDoc to assign the correct DocBook language attribute?</h2>
+<div class="sectionbody">
+<div class="para"><p>Set the <em>AsciiDoc</em> <em>lang</em> attribute to the appropriate language code.
+For example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>$ a2x -a lang=es doc/article.txt</tt></pre>
+</div></div>
+<div class="para"><p>This will ensure that downstream DocBook processing will generate the
+correct language specific document headings (things like table of
+contents, revision history, figure and table captions, admonition
+captions).</p></div>
+</div>
+<h2 id="_why_does_asciidoc_give_me_a_8220_malformed_author_8221_error">5. Why does AsciiDoc give me a &#8220;malformed author&#8221; error?</h2>
+<div class="sectionbody">
+<div class="para"><p>This is normally because there are more than three names (up to three
+are expected: first name, middle name and last name). For example,
+this author line would result in an error:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>Vincent Willem van Gogh</tt></pre>
+</div></div>
+<div class="para"><p>You can enter multi-word first, middle and last names in the author
+line using the underscore as a word separator. For example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>Vincent Willem van_Gogh</tt></pre>
+</div></div>
+<div class="para"><p>You could also resolve the problem by replacing the author line with
+explicit attribute entries:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>:First name:  Vincent
+:Middle name: Willem
+:Last name:   Van Gogh</tt></pre>
+</div></div>
+</div>
+<h2 id="_how_can_i_assign_multiple_author_names">6. How can I assign multiple author names?</h2>
+<div class="sectionbody">
+<div class="para"><p>A quick way to do this is put both authors in a single first name, for
+example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>My Document
+===========
+:Author: Bill_and_Ben_the_Flowerpot_Men
+:Author Initials: BB &amp; BC</tt></pre>
+</div></div>
+<div class="para"><p><tt>asciidoc(1)</tt> replaces the underscores with spaces.</p></div>
+<div class="para"><p>The longer, but semantically correct way, is to override the
+<tt>[header]</tt> configuration file section in a document specific <tt>.conf</tt>
+file. For example if your document is <tt>mydoc.txt</tt> then a file called
+<tt>mydoc.conf</tt> in the document directory would be picked up
+automatically by <tt>asciidoc(1)</tt>.  Copy and paste the default
+<tt>docbook.conf</tt> file <tt>[header]</tt> to <tt>mydoc.conf</tt> and modify the author
+related markup:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>[header]
+  :
+&lt;authorgroup&gt;...
+  :</tt></pre>
+</div></div>
+</div>
+<h2 id="_how_can_i_escape_asciidoc_markup">7. How can I escape AsciiDoc markup?</h2>
+<div class="sectionbody">
+<div class="para"><p>Most <em>AsciiDoc</em> inline elements can be suppressed by preceding them with
+a backslash character. These elements include:</p></div>
+<div class="ilist"><ul>
+<li>
+<p>
+Attribute references.
+</p>
+</li>
+<li>
+<p>
+Text formatting.
+</p>
+</li>
+<li>
+<p>
+Quoting,
+</p>
+</li>
+<li>
+<p>
+<em>URLs</em>, <em>image</em> and <em>link</em> macros.
+</p>
+</li>
+<li>
+<p>
+Replacements.
+</p>
+</li>
+<li>
+<p>
+Special words.
+</p>
+</li>
+</ul></div>
+<div class="para"><p>In some cases you may need to escape both left and right quotes (see
+the <em><em>AsciiDoc</em> User Guide</em>).</p></div>
+</div>
+<h2 id="_how_can_i_escape_a_labeled_list_entry">8. How can I escape a labeled list entry?</h2>
+<div class="sectionbody">
+<div class="para"><p>Two colons or semicolons in a paragraph may be confused with a labeled
+list entry. Use the predefined <tt>{two_colons}</tt> and <tt>{two_semicolons}</tt>
+to suppress this behavior, for example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>Qui in magna commodo{two_colons} est labitur dolorum an. Est ne
+magna primis adolescens.</tt></pre>
+</div></div>
+<div class="para"><p>Will be rendered as:</p></div>
+<div class="para"><p>Qui in magna commodo:: est labitur dolorum an. Est ne
+magna primis adolescens.</p></div>
+</div>
+<h2 id="_how_can_i_disable_a_quoted_text_substitution">9. How can I disable a quoted text substitution?</h2>
+<div class="sectionbody">
+<div class="para"><p>Omitting the tag will disable quoting. For example, if you don't want
+superscripts or subscripts then put the following in a custom
+configuration file or edit the global <tt>asciidoc.conf</tt> configuration
+file:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>[quotes]
+^=
+~=</tt></pre>
+</div></div>
+</div>
+<h2 id="_i_have_a_paragraph_containing_some_funky_urls_is_there_a_way_to_suppress_asciidoc_substitutions_in_the_url_address">10. I have a paragraph containing some funky URLs, is there a way to suppress AsciiDoc substitutions in the URL address?</h2>
+<div class="sectionbody">
+<div class="para"><p>You can selectively choose which substitutions to perform by setting
+the <em>subs</em> attribute at the start of a block. For example:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>[subs="macros"]
+~subscripts~ and ^superscripts^ quotes won't be substituted.
+Nor will the non-alphanumeric characters in the following URL:
+http://host/~user/file#_anchor_tag_str_</tt></pre>
+</div></div>
+</div>
+<h2 id="_how_can_i_customize_the_localdate_format">11. How can I customize the {localdate} format?</h2>
+<div class="sectionbody">
+<div class="para"><p>The default format for the <tt>{localdate}</tt> attribute is the ISO 8601
+<tt>yyyy-mm-dd</tt> format. You can change this format by explicitly setting
+the <tt>{localdate}</tt> attribute. For example by setting it using the
+<tt>asciidoc(1)</tt> <tt>-a</tt> command-line option:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>$ asciidoc -a localdate=`date +%d-%d-%Y` mydoc.txt</tt></pre>
+</div></div>
+<div class="para"><p>You could also set it by adding an Attribute Entry to your souce
+document, for example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>:localdate: {sys: date +%Y-%m-%d}</tt></pre>
+</div></div>
+<div class="para"><p>Since it's set using an executable attribute you'll also need to
+include the <tt>&#8212;unsafe</tt> option when you run asciidoc).</p></div>
+</div>
+<h2 id="_why_doesn_t_asciidoc_support_strike_through_text">12. Why doesn't AsciiDoc support strike through text?</h2>
+<div class="sectionbody">
+<div class="para"><p>The reason it's not in the distribution is that DocBook does not have
+provision for strike through text and one of the <em>AsciiDoc</em> design goals
+is that <em>AsciiDoc</em> markup should be applicable to all output formats.</p></div>
+<div class="para"><p>Strike through is normally used to mark deleted text &#8212; a more
+comprehensive way to manage document revisions is to use a version
+control system such as Subversion. You can also use the <em>AsciiDoc</em>
+<em>CommentLines</em> and <em>CommentBlocks</em> to retain revised text in the
+source document.</p></div>
+<div class="para"><p>If you really need strike through text for (X)HTML outputs then adding
+the following to a configuration file will allow you to quote strike
+through text with hyphen characters:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt> ifdef::basebackend-html[]
+ [quotes]
+ -=strikethrough
+ [tags]
+ strikethrough=&lt;span style="text-decoration: line-through;"&gt;|&lt;/span&gt;
+ endif::basebackend-html[]</tt></pre>
+</div></div>
+</div>
+<h2 id="_where_can_i_find_examples_of_commands_used_to_build_output_documents">13. Where can I find examples of commands used to build output documents?</h2>
+<div class="sectionbody">
+<div class="para"><p>The User Guide has some. You could also look at <tt>./doc/main.aap</tt> in
+the <em>AsciiDoc</em> distribution, it has all the commands used to build the
+<em>AsciiDoc</em> documentation (even if you don't use A-A-P you'll still find
+it useful).</p></div>
+</div>
+<h2 id="_how_can_i_place_a_backslash_character_in_front_of_an_attribute_reference_without_escaping_the_reference">14. How can I place a backslash character in front of an attribute reference without escaping the reference?</h2>
+<div class="sectionbody">
+<div class="para"><p>Use the predefined <tt>{backslash}</tt> attribute reference instead of an
+actual backslash, for example if the <tt>{projectname}</tt> attribute has
+the value <tt>foobar</tt> then:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>d:\data{backslash}{projectname}</tt></pre>
+</div></div>
+<div class="para"><p>would be rendered as:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>d:\data\foobar</tt></pre>
+</div></div>
+</div>
+<h2 id="_why_have_you_used_the_docbook_lt_simpara_gt_element_instead_of_lt_para_gt">15. Why have you used the DocBook &lt;simpara&gt; element instead of &lt;para&gt;?</h2>
+<div class="sectionbody">
+<div class="para"><p><tt>&lt;simpara&gt;</tt> is really the same as <tt>&lt;para&gt;</tt> except it can't contain
+block elements &#8212; this matched, more closely, the <em>AsciiDoc</em> paragraph
+semantics.</p></div>
+</div>
+<h2 id="_how_can_i_format_text_inside_a_listting_block">16. How can I format text inside a listting block?</h2>
+<div class="sectionbody">
+<div class="para"><p>By default only <em>specialcharacters</em> and <em>callouts</em> are substituted in
+listing blocks; you can add quotes substitutions by explicitly setting
+the block <em>subs</em> attribute, for example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>[subs="specialcharacters,callouts,quotes"]
+------------------------------------------
+$ ls *-al*
+------------------------------------------</tt></pre>
+</div></div>
+<div class="para"><p>The <tt>-al</tt> will rendered bold. Note that:</p></div>
+<div class="ilist"><ul>
+<li>
+<p>
+You would need to explicitly escape text you didn't want quoted.
+</p>
+</li>
+<li>
+<p>
+Don't do this in source code listing blocks because it modifies the
+  source code which confuses the syntax highlighter.
+</p>
+</li>
+<li>
+<p>
+This only works if your DocBook processor recognizes DocBook
+  <tt>&lt;emphasis&gt;</tt> elements inside <tt>&lt;screen&gt;</tt> elements.
+</p>
+</li>
+</ul></div>
+</div>
+<h2 id="_why_doesn_t_the_include1_macro_work">17. Why doesn't the include1::[] macro work?</h2>
+<div class="sectionbody">
+<div class="para"><p>Internally the <tt>include1</tt> macro is translated to the <tt>include1</tt> system
+attribute which means it must be evaluated in a region where attribute
+substitution is enabled. For example, if you want to evaluate it
+inside a listing block you will need to enable attribute substitution
+inside the block, for example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>[subs="attributes"]
+-----------------------------------------
+include1::blogpost_media_processing.txt[]
+-----------------------------------------</tt></pre>
+</div></div>
+<div class="para"><p>Or, preferably, use the <tt>include</tt> block macro instead.</p></div>
+</div>
+<div id="footer">
+<div id="footer-text">
+Version 8.2.7<br />
+Last updated 2008-07-04 23:29:23 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>

data/asciidoc/examples/website/index.html ADDED Viewed

@@ -0,0 +1,398 @@
+<!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" />
+<meta name="description" content="Text based document generation" />
+<meta name="keywords" content="text to HTML, text to DocBook, text to XML, AsciiDoc" />
+<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" />
+<script type="text/javascript">
+/*<![CDATA[*/
+window.onload = function(){generateToc(1)}
+/*]]>*/
+</script>
+<script type="text/javascript" src="./toc.js"></script>
+<title>AsciiDoc Home Page</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="index.txt">Page&nbsp;Source</a></div>
+</td>
+<td>
+<div id="layout-content">
+<div id="header">
+<h1>AsciiDoc Home Page</h1>
+</div>
+<div id="toc">
+  <div id="toctitle">Table of Contents</div>
+  <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
+</div>
+<div id="preamble">
+<div class="sectionbody">
+<div class="sidebarblock">
+<div class="sidebar-content">
+<div class="sidebar-title">4 July 2008: AsciiDoc 8.2.7 Released</div>
+<div class="para"><p>Useful additions include:</p></div>
+<div class="ilist"><ul>
+<li>
+<p>
+<a href="http://dblatex.sourceforge.net/">dblatex</a> is now fully supported by
+  <tt>a2x(1)</tt> and is the default <tt>a2x(1)</tt> PDF generator.
+</p>
+</li>
+<li>
+<p>
+Added <tt>dvi</tt>, <tt>ps</tt> and <tt>tex</tt> output format options to <tt>a2x(1)</tt>
+  (courtesy of <tt>dblatex(1)</tt>).
+</p>
+</li>
+<li>
+<p>
+URLs and email addresses are recognized without having to use the
+  macro syntax.
+</p>
+</li>
+<li>
+<p>
+<a href="source-highlight-filter.html">Source code paragraphs</a> make small
+  code examples easier to enter.
+</p>
+</li>
+</ul></div>
+<div class="para"><p>Read the <a href="CHANGELOG.html">CHANGELOG</a> for a full description of all
+the other additions and changes.</p></div>
+<div class="para"><p><a href="mailto:srackham@gmail.com"><em>Stuart Rackham</em></a></p></div>
+</div></div>
+</div>
+</div>
+<h2 id="_introduction">Introduction</h2>
+<div class="sectionbody">
+<div class="para"><p><em>AsciiDoc</em> is a text document format for writing short documents,
+articles, books and UNIX man pages. <em>AsciiDoc</em> files can be translated
+to HTML and DocBook markups using the <tt>asciidoc(1)</tt> command.</p></div>
+<div class="para"><p><em>AsciiDoc</em> is highly configurable: both the <em>AsciiDoc</em> 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.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/tip.png" alt="Tip" />
+</td>
+<td class="content">The pages you are reading were written using <em>AsciiDoc</em>, to view
+the corresponding <em>AsciiDoc</em> source click on the <strong>Page Source</strong> menu item
+in the left hand margin.</td>
+</tr></table>
+</div>
+</div>
+<h2 id="_overview_and_examples">Overview and Examples</h2>
+<div class="sectionbody">
+<div class="para"><p>You write an <em>AsciiDoc</em> document the same way you would write a
+normal text document, there are no markup tags or weird format
+notations. <em>AsciiDoc</em> files are designed to be viewed, edited and
+printed directly or translated to other presentation formats using
+the <tt>asciidoc(1)</tt> command.</p></div>
+<div class="para"><p>The <tt>asciidoc(1)</tt> command translates <em>AsciiDoc</em> 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.</p></div>
+<h3 id="_example_articles">Example Articles</h3><div style="clear:left"></div>
+<div class="ilist"><ul>
+<li>
+<p>
+This version of the
+  <a href="asciidoc.css-embedded.html"><em>AsciiDoc</em> User Guide</a>
+  was generated by <em>AsciiDoc</em> from
+  <a href="asciidoc.txt">this <em>AsciiDoc</em> file</a>.
+</p>
+</li>
+<li>
+<p>
+Here's the <a href="asciidoc.html">same document</a> created by first
+  generating DocBook markup using <em>AsciiDoc</em> and then converting the
+  DocBook markup to HTML using <em>DocBook XSL Stylesheets</em>.
+</p>
+</li>
+<li>
+<p>
+The User Guide again, this time a
+  <a href="chunked/index.html">chunked version</a>.
+</p>
+</li>
+<li>
+<p>
+This <a href="article.txt"><em>AsciiDoc</em> article template</a> produced
+  this <a href="article.html">HTML file</a> and this
+  <a href="article.pdf">PDF file</a> via DocBook markup generated by <em>AsciiDoc</em>.
+</p>
+</li>
+<li>
+<p>
+This <a href="asciidoc.pdf">PDF formatted User Guide</a> was generated from
+  <tt>asciidoc(1)</tt> DocBook output.
+</p>
+</li>
+</ul></div>
+<h3 id="_example_books">Example Books</h3><div style="clear:left"></div>
+<div class="para"><p><em>AsciiDoc</em> markup supports all the standard DocBook frontmatter and
+backmatter sections (dedication, preface, bibliography, glossary,
+index, colophon) plus footnotes and index entries.</p></div>
+<div class="vlist"><dl>
+<dt>
+Book
+</dt>
+<dd>
+<p>
+    This <a href="book.txt"><em>AsciiDoc</em> book's</a> DocBook output
+    produced <a href="book.html">this HTML file</a> using the
+    <em>DocBook XSL Stylesheets</em>.
+</p>
+</dd>
+<dt>
+Multi-part book
+</dt>
+<dd>
+<p>
+    This <a href="book-multi.txt">multi-part <em>AsciiDoc</em> book's</a>
+    DocBook output produced <a href="book-multi.html">this HTML file</a>
+    using the <em>DocBook XSL Stylesheets</em>.
+</p>
+</dd>
+</dl></div>
+<h3 id="_example_unix_man_pages">Example UNIX Man Pages</h3><div style="clear:left"></div>
+<div class="para"><p>HTML formatted <em>AsciiDoc</em> man pages
+<a href="asciidoc.1.css-embedded.html">with stylesheets</a> and
+<a href="asciidoc.1.html">without stylesheets</a> were generated by <em>AsciiDoc</em>
+from <a href="asciidoc.1.txt">this file</a>.</p></div>
+<div class="para"><p>This <a href="asciidoc.1">roff formatted  man page</a> was generated from
+<tt>asciidoc(1)</tt> DocBook output using <tt>xsltproc(1)</tt> and DocBook XSL
+Stylesheets.</p></div>
+<h3 id="_example_web_site">Example Web Site</h3><div style="clear:left"></div>
+<div class="para"><p>The <a href="README-website.html"><em>AsciiDoc</em> website</a> is included in the
+<em>AsciiDoc</em> distribution (in <tt>./examples/website/</tt>) as example website
+built using <em>AsciiDoc</em>.  See <tt>./examples/website/README-website.txt</tt>.</p></div>
+</div>
+<h2 id="_music_filter">Music Filter</h2>
+<div class="sectionbody">
+<div class="para"><p>A <a href="music-filter.html">music filter</a> is included in the distribution
+<tt>./filters/</tt> directory. It translates music in
+<a href="http://lilypond.org/">LilyPond</a> or <a href="http://abcnotation.org.uk/">ABC</a>
+notation to standard classical notation</p></div>
+</div>
+<h2 id="_source_code_highlight_filter">Source Code Highlight Filter</h2>
+<div class="sectionbody">
+<div class="para"><p>A <a href="source-highlight-filter.html">source code highlight filter</a> is
+included in the distribution <tt>./filters/</tt> directory.</p></div>
+</div>
+<h2 id="X3">Mathematical Formulae</h2>
+<div class="sectionbody">
+<div class="para"><p>You can include mathematical formulae in your <em>AsciiDoc</em> documents using
+<a href="asciimath.html">ASCIIMathML</a> or <a href="latexmath.html">LaTeXMathML</a>
+notation.</p></div>
+</div>
+<h2 id="_vim_syntax_highlighter">Vim Syntax Highlighter</h2>
+<div class="sectionbody">
+<div class="para"><p>An <em>AsciiDoc</em> syntax highlighter for the Vim text editor is included in
+the <em>AsciiDoc</em> distribution (see <em>Appendix F</em> of the <em><em>AsciiDoc</em> User
+Guide</em> for details).</p></div>
+<div class="imageblock">
+<div class="content">
+<a class="image" href="images/highlighter.png">
+<img src="images/highlighter.png" alt="images/highlighter.png" height="250"/>
+</a>
+</div>
+<div class="image-title">Syntax highlighter screenshot</div>
+</div>
+<div class="para"><p>Dag Wieers has implemented an alternative Vim syntax file for <em>AsciiDoc</em>
+which can be found here
+<a href="http://svn.rpmforge.net/svn/trunk/tools/asciidoc-vim/">http://svn.rpmforge.net/svn/trunk/tools/asciidoc-vim/</a>.</p></div>
+</div>
+<h2 id="X2">Resources</h2>
+<div class="sectionbody">
+<div class="ilist"><ul>
+<li>
+<p>
+Check the <a href="downloads.html">Downloads page</a> for packaged versions
+  of <em>AsciiDoc</em>.
+</p>
+</li>
+<li>
+<p>
+Alex Efros has written an HTML formatted
+  <a href="http://powerman.name/doc/asciidoc"><em>AsciiDoc</em> Cheatsheet</a> using
+  Asciidoc.
+</p>
+</li>
+<li>
+<p>
+Thomas Berker has written an
+  <a href="http://liksom.info/blog/?q=node/114"><em>AsciiDoc</em> Cheatsheet</a> in Open
+  Document and PDF formats.
+</p>
+</li>
+<li>
+<p>
+The <a href="http://www.wikimatrix.org/">WikiMatrix</a> website has an excellent
+  <a href="http://www.wikimatrix.org/syntax.php">web page</a> that compares the
+  various Wiki markup syntaxes. An interesting attempt at Wiki markup
+  standardization is <a href="http://www.wikicreole.org/">CREOLE</a>.
+</p>
+</li>
+<li>
+<p>
+Terrence Brannon has written
+  <a href="http://www.metaperl.com/asciidoc-el/"><em>AsciiDoc</em> functions for Emacs</a>.
+</p>
+</li>
+<li>
+<p>
+The <a href="http://xpt.sourceforge.net/">*Nix Power Tools project</a> has
+  released an <a href="http://xpt.sourceforge.net/tools/doc-mode/"><em>AsciiDoc</em>
+  syntax highlighter for Emacs</a>.
+</p>
+</li>
+<li>
+<p>
+Franck Pommereau has written
+  <a href="http://www.univ-paris12.fr/lacl/pommereau/soft/asciidoctest.html">Asciidoctest</a>,
+  a program that doctests snippets of Python code within your Asciidoc
+  documents.
+</p>
+</li>
+<li>
+<p>
+The <a href="http://remips.sourceforge.net/">ReMIPS</a> project website has been
+  built using <em>AsciiDoc</em>.
+</p>
+</li>
+<li>
+<p>
+Here are some <a href="asciidoc-docbook-xsl.html">DocBook XSL Stylesheets
+  Notes</a>.
+</p>
+</li>
+<li>
+<p>
+Karl Mowatt-Wilson has developed an <a href="http://ikiwiki.info/">ikiwiki</a>
+  plugin for <em>AsciiDoc</em> which he uses to render
+  <a href="http://mowson.org/karl">his website</a>.  The plugin is available
+  <a href="http://www.mowson.org/karl/colophon/">here</a> and there is some
+  discussion of the ikiwiki integration
+  <a href="http://ikiwiki.info/users/KarlMW/discussion/">here</a>.
+</p>
+</li>
+</ul></div>
+</div>
+<h2 id="_blogpost_weblog_client">Blogpost weblog client</h2>
+<div class="sectionbody">
+<div class="para"><p><a href="http://srackham.wordpress.com/blogpost-readme/">blogpost</a> is a
+command-line weblog client for publishing <em>AsciiDoc</em> documents to
+<a href="http://wordpress.org/">WordPress</a> blog hosts. It creates and updates
+weblog posts and pages directly from <em>AsciiDoc</em> source documents.</p></div>
+</div>
+<h2 id="X1">LaTeX Backend</h2>
+<div class="sectionbody">
+<div class="para"><p>An experimental LaTeX backend has been written for <em>AsciiDoc</em> by
+Benjamin Klum.  Benjamin has done a superhuman job (I admit it, I
+didn't think this was doable due to <em>AsciiDoc</em>'s SGML/XML bias).</p></div>
+<div class="para"><p>Here's <a href="latex-backend.html">Benjamin's documentation</a>.</p></div>
+</div>
+<h2 id="_projects_using_asciidoc">Projects using AsciiDoc</h2>
+<div class="sectionbody">
+<div class="para"><p>Here are some projects I know of, if you know of more drop me a line
+and I'll add them to the list.</p></div>
+<div class="ilist"><ul>
+<li>
+<p>
+The Linux kernel
+  <a href="http://www.kernel.org/pub/software/scm/git/docs/git.html">git source
+  code management system</a>.
+</p>
+</li>
+<li>
+<p>
+Some documentation about git by Nico Schottelius (in German)
+  <a href="http://nico.schotteli.us/papers/linux/git-firmen/">http://nico.schotteli.us/papers/linux/git-firmen/</a>.
+</p>
+</li>
+<li>
+<p>
+The <a href="http://www.netpromi.com/kirbybase_ruby.html">KirbyBase for Ruby</a>
+  database management system manual.
+</p>
+</li>
+<li>
+<p>
+The <a href="http://www.selenic.com/mercurial/">Mercurial distributed SCM</a>
+  uses asciidoc for its man pages.
+</p>
+</li>
+<li>
+<p>
+Pascal Rapaz has written a Python script to automate <em>AsciiDoc</em>
+  website generation. You can find it at
+  <a href="http://www.rapazp.ch/opensource/tools/asciidoc.html">http://www.rapazp.ch/opensource/tools/asciidoc.html</a>.
+</p>
+</li>
+<li>
+<p>
+The <a href="http://xpt.sourceforge.net/">*Nix Power Tools project</a> uses
+  <em>AsciiDoc</em> for documentation and has released an Emacs syntax
+  highlighter (see <a href="#X2">Resources</a> above).
+</p>
+</li>
+</ul></div>
+</div>
+<h2 id="_asciidoc_version_9">AsciiDoc version 9</h2>
+<div class="sectionbody">
+<div class="para"><p>The next version of <em>AsciiDoc</em> is underway &#8212; details
+<a href="version9.html">here</a>.</p></div>
+</div>
+<div id="footer">
+<div id="footer-text">
+Version 8.2.7<br />
+Last updated 2008-07-04 23:29:25 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>