Deployed 6e20991 with MkDocs version: 0.17.2

Author: waylan

404.html

@@ -106,7 +106,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:10
+        Docs Build Date UTC : 2017-12-07 01:17:43
         -->
     </body>
 </html>

authors/index.html

@@ -213,7 +213,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:12
+        Docs Build Date UTC : 2017-12-07 01:17:45
         -->
     </body>
 </html>

change_log/index.html

@@ -307,7 +307,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:12
+        Docs Build Date UTC : 2017-12-07 01:17:45
         -->
     </body>
 </html>

change_log/release-2.0/index.html

@@ -223,7 +223,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:12
+        Docs Build Date UTC : 2017-12-07 01:17:45
         -->
     </body>
 </html>

change_log/release-2.1/index.html

@@ -106,7 +106,7 @@ <h2 id="backwards-incompatible-changes">Backwards-incompatible Changes<a class="
 <a href="../../reference/">Library Reference</a> for the options available.</p>
 </li>
 <li>
-<p>If you have been using the <a href="../extensions.md">HeaderId</a> extension
+<p>If you have been using the <a href="../../extensions/header_id/">HeaderId</a> extension
 to define custom ids on headers, you will want to switch to using the new
 <a href="../../extensions/attr_list/">Attribute List</a> extension. The HeaderId extension
 now only auto-generates ids on headers which have not already had ids defined.
@@ -278,7 +278,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:12
+        Docs Build Date UTC : 2017-12-07 01:17:45
         -->
     </body>
 </html>

change_log/release-2.2/index.html

@@ -227,7 +227,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:12
+        Docs Build Date UTC : 2017-12-07 01:17:45
         -->
     </body>
 </html>

change_log/release-2.3/index.html

@@ -102,7 +102,7 @@ <h2 id="backwards-incompatible-changes">Backwards-incompatible Changes<a class="
 <li>
 <p>The <code>force_linenos</code> configuration setting of the CodeHilite extension has been
 marked as <strong>Pending Deprecation</strong> and a new setting <code>linenums</code> has been added to
-replace it. See documentation for the <a href="../extensions/codehilite.md">CodeHilite Extension</a> for an explanation
+replace it. See documentation for the <a href="../../extensions/code_hilite/">CodeHilite Extension</a> for an explanation
 of the new <code>linenums</code> setting. The new setting will honor the old
 <code>force_linenos</code> if it is set, but it will raise a <code>PendingDeprecationWarning</code>
 and will likely be removed in a future version of Python-Markdown.</p>
@@ -255,7 +255,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:12
+        Docs Build Date UTC : 2017-12-07 01:17:45
         -->
     </body>
 </html>

change_log/release-2.4/index.html

@@ -76,7 +76,7 @@ <h2 id="backwards-incompatible-changes">Backwards-incompatible Changes<a class="
 <p>The <code>force_linenos</code> configuration setting of the CodeHilite extension has been
 marked as <strong>Deprecated</strong>. It had previously been marked as &ldquo;Pending Deprecation&rdquo;
 in version 2.3 when a new setting <code>linenums</code> was added to replace it. See
-documentation for the <a href="../extensions/codehilite.md">CodeHilite Extension</a> for an explanation of the new
+documentation for the <a href="../../extensions/code_hilite/">CodeHilite Extension</a> for an explanation of the new
 <code>linenums</code> setting. The new setting will honor the old <code>force_linenos</code> if it
 is set, but <code>force_linenos</code> will raise a <code>DeprecationWarning</code> and will likely
 be removed in a future version of Python-Markdown.</p>
@@ -234,7 +234,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:12
+        Docs Build Date UTC : 2017-12-07 01:17:45
         -->
     </body>
 </html>

change_log/release-2.5/index.html

@@ -349,7 +349,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:12
+        Docs Build Date UTC : 2017-12-07 01:17:45
         -->
     </body>
 </html>

change_log/release-2.6/index.html

@@ -446,7 +446,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:12
+        Docs Build Date UTC : 2017-12-07 01:17:45
         -->
     </body>
 </html>

cli/index.html

@@ -67,64 +67,64 @@ <h3>Navigation</h3>
             <div class="documentwrapper">
                 <div class="bodywrapper">
                     <div class="body" role="main"><h1 id="using-python-markdown-on-the-command-line">Using Python-Markdown on the Command Line<a class="headerlink" href="#using-python-markdown-on-the-command-line" title="Permanent link">&para;</a></h1>
-<p>While Python-Markdown is primarily a python library, a command line script is 
-included as well. While there are many other command line implementations 
-of Markdown, you may not have them installed, or you may prefer to use 
+<p>While Python-Markdown is primarily a python library, a command line script is
+included as well. While there are many other command line implementations
+of Markdown, you may not have them installed, or you may prefer to use
 Python-Markdown&rsquo;s various extensions.</p>
 <p>Generally, you will want to have the Markdown library fully installed on your
-system to run the command line script. See the 
+system to run the command line script. See the
 <a href="../install/">Installation instructions</a> for details.</p>
 <p>Python-Markdown&rsquo;s command line script takes advantage of Python&rsquo;s <code>-m</code> flag.
-Therefore, assuming the python executable is on your system path, use the 
+Therefore, assuming the python executable is on your system path, use the
 following format:</p>
-<div class="codehilite"><pre><span></span>$ python -m markdown <span class="o">[</span>options<span class="o">]</span> <span class="o">[</span>args<span class="o">]</span>
+<div class="codehilite"><pre><span></span>python -m markdown <span class="o">[</span>options<span class="o">]</span> <span class="o">[</span>args<span class="o">]</span>
 </pre></div>
 
 
-<p>That will run the module as a script with the options and arguments provided. </p>
+<p>That will run the module as a script with the options and arguments provided.</p>
 <p>At its most basic usage, one would simply pass in a file name as the only argument:</p>
-<div class="codehilite"><pre><span></span>$ python -m markdown input_file.txt
+<div class="codehilite"><pre><span></span>python -m markdown input_file.txt
 </pre></div>
 
 
-<p>Piping input and output (on <code>STDIN</code> and <code>STDOUT</code>) is fully supported as well. 
+<p>Piping input and output (on <code>STDIN</code> and <code>STDOUT</code>) is fully supported as well.
 For example:</p>
-<div class="codehilite"><pre><span></span>$ <span class="nb">echo</span> <span class="s2">&quot;Some **Markdown** text.&quot;</span> <span class="p">|</span> python -m markdown &gt; output.html
+<div class="codehilite"><pre><span></span><span class="nb">echo</span> <span class="s2">&quot;Some **Markdown** text.&quot;</span> <span class="p">|</span> python -m markdown &gt; output.html
 </pre></div>
 
 
 <p>Use the <code>--help</code> option for a list all available options and arguments:</p>
-<div class="codehilite"><pre><span></span>$ python -m markdown --help
+<div class="codehilite"><pre><span></span>python -m markdown --help
 </pre></div>
 
 
-<p>If you don&rsquo;t want to call the python executable directly (using the <code>-m</code> flag), 
+<p>If you don&rsquo;t want to call the python executable directly (using the <code>-m</code> flag),
 follow the instructions below to use a wrapper script:</p>
 <h2 id="setup">Setup<a class="headerlink" href="#setup" title="Permanent link">&para;</a></h2>
 <p>Upon installation, the <code>markdown_py</code> script will have been copied to
 your Python &ldquo;Scripts&rdquo; directory. Different systems require different methods to
-ensure that any files in the Python &ldquo;Scripts&rdquo; directory are on your system 
+ensure that any files in the Python &ldquo;Scripts&rdquo; directory are on your system
 path.</p>
 <ul>
 <li>
 <p><strong>Windows</strong>:</p>
-<p>Assuming a default install of Python on Windows, your &ldquo;Scripts&rdquo; directory 
+<p>Assuming a default install of Python on Windows, your &ldquo;Scripts&rdquo; directory
 is most likely something like <code>C:\\Python26\Scripts</code>. Verify the location
 of your &ldquo;Scripts&rdquo; directory and add it to you system path.</p>
-<p>Calling <code>markdown_py</code> from the command line will call the wrapper batch 
+<p>Calling <code>markdown_py</code> from the command line will call the wrapper batch
 file <code>markdown_py.bat</code> in the <code>"Scripts"</code> directory created during install.</p>
 </li>
 <li>
 <p><strong>*nix</strong> (Linux, OSX, BSD, Unix, etc.):</p>
-<p>As each *nix distribution is different and we can&rsquo;t possibly document all 
+<p>As each *nix distribution is different and we can&rsquo;t possibly document all
 of them here, we&rsquo;ll provide a few helpful pointers:</p>
 <ul>
 <li>
-<p>Some systems will automatically install the script on your path. Try it 
+<p>Some systems will automatically install the script on your path. Try it
   and see if it works. Just run <code>markdown_py</code> from the command line.</p>
 </li>
 <li>
-<p>Other systems may maintain a separate &ldquo;Scripts&rdquo; (&ldquo;bin&rdquo;) directory which 
+<p>Other systems may maintain a separate &ldquo;Scripts&rdquo; (&ldquo;bin&rdquo;) directory which
   you need to add to your path. Find it (check with your distribution) and
   either add it to your path or make a symbolic link to it from your path.</p>
 </li>
@@ -135,78 +135,78 @@ <h2 id="setup">Setup<a class="headerlink" href="#setup" title="Permanent link">&
 </ul>
 <p>As an alternative, you could just <code>cd</code> into the directory which contains
 the source distribution, and run it from there. However, remember that your
-markdown text files will not likely be in that directory, so it is much 
+markdown text files will not likely be in that directory, so it is much
 more convenient to have <code>markdown_py</code> on your path.</p>
 </li>
 </ul>
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p>Python-Markdown uses <code>"markdown_py"</code> as a script name because
 the Perl implementation has already taken the more obvious name &ldquo;markdown&rdquo;.
-Additionally, the default Python configuration on some systems would cause a 
+Additionally, the default Python configuration on some systems would cause a
 script named <code>"markdown.py"</code> to fail by importing itself rather than the markdown
 library. Therefore, the script has been named <code>"markdown_py"</code> as a compromise. If
 you prefer a different name for the script on your system, it is suggested that
 you create a symbolic link to <code>markdown_py</code> with your preferred name.</p>
 </div>
 <h2 id="usage">Usage<a class="headerlink" href="#usage" title="Permanent link">&para;</a></h2>
-<p>To use <code>markdown_py</code> from the command line, run it as </p>
-<div class="codehilite"><pre><span></span>$ markdown_py input_file.txt
+<p>To use <code>markdown_py</code> from the command line, run it as</p>
+<div class="codehilite"><pre><span></span>markdown_py input_file.txt
 </pre></div>
 
 
-<p>or </p>
-<div class="codehilite"><pre><span></span>$ markdown_py input_file.txt &gt; output_file.html
+<p>or</p>
+<div class="codehilite"><pre><span></span>markdown_py input_file.txt &gt; output_file.html
 </pre></div>
 
 
 <p>For a complete list of options, run</p>
-<div class="codehilite"><pre><span></span>$ markdown_py --help
+<div class="codehilite"><pre><span></span>markdown_py --help
 </pre></div>
 
 
 <h2 id="using-extensions">Using Extensions<a class="headerlink" href="#using-extensions" title="Permanent link">&para;</a></h2>
-<p>To load a Python-Markdown extension from the command line use the <code>-x</code> 
-(or <code>--extension</code>) option. The extension module must be on your <code>PYTHONPATH</code> 
-(see the <a href="../extensions/api/">Extension API</a> for details). The extension can 
+<p>To load a Python-Markdown extension from the command line use the <code>-x</code>
+(or <code>--extension</code>) option. The extension module must be on your <code>PYTHONPATH</code>
+(see the <a href="../extensions/api/">Extension API</a> for details). The extension can
 then be invoked by the name of that module using Python&rsquo;s dot syntax:</p>
-<div class="codehilite"><pre><span></span>$ python -m markdown -x path.to.module input.txt
+<div class="codehilite"><pre><span></span>python -m markdown -x path.to.module input.txt
 </pre></div>
 
 
 <p>To load multiple extensions, specify an <code>-x</code> option for each extension:</p>
-<div class="codehilite"><pre><span></span>$ python -m markdown -x markdown.extensions.footnotes -x markdown.extensions.codehilite input.txt
+<div class="codehilite"><pre><span></span>python -m markdown -x markdown.extensions.footnotes -x markdown.extensions.codehilite input.txt
 </pre></div>
 
 
-<p>If the extension supports configuration options (see the documentation for the 
-extension you are using to determine what settings it supports, if any), you 
+<p>If the extension supports configuration options (see the documentation for the
+extension you are using to determine what settings it supports, if any), you
 can pass them in as well:</p>
-<div class="codehilite"><pre><span></span>$ python -m markdown -x markdown.extensions.footnotes -c config.yml input.txt
+<div class="codehilite"><pre><span></span>python -m markdown -x markdown.extensions.footnotes -c config.yml input.txt
 </pre></div>
 
 
 <p>The <code>-c</code> (or <code>--extension_configs</code>) option accepts a file name. The file must be in
 either the <a href="http://yaml.org/">YAML</a> or <a href="http://json.org/">JSON</a> format and contain YAML or JSON data that would map to
-a Python Dictionary in the format required by the <a href="../reference.html#extension_configs"><code>extension_configs</code></a> keyword 
-of the <code>markdown.Markdown</code> class. Therefore, the file <code>config.yaml</code> referenced in the 
+a Python Dictionary in the format required by the <a href="../reference.html#extension_configs"><code>extension_configs</code></a> keyword
+of the <code>markdown.Markdown</code> class. Therefore, the file <code>config.yaml</code> referenced in the
 above example might look like this:</p>
-<div class="codehilite"><pre><span></span>markdown.extensions.footnotes:
-    PLACE_MARKER: ~~~~~~~~
-    UNIQUE_IDS: True
+<div class="codehilite"><pre><span></span><span class="l l-Scalar l-Scalar-Plain">markdown.extensions.footnotes</span><span class="p p-Indicator">:</span>
+    <span class="l l-Scalar l-Scalar-Plain">PLACE_MARKER</span><span class="p p-Indicator">:</span> <span class="l l-Scalar l-Scalar-Plain">~~~~~~~~</span>
+    <span class="l l-Scalar l-Scalar-Plain">UNIQUE_IDS</span><span class="p p-Indicator">:</span> <span class="l l-Scalar l-Scalar-Plain">True</span>
 </pre></div>
 
 
-<p>Note that while the <code>--extension_configs</code> option does specify the &ldquo;markdown.extensions.footnotes&rdquo; 
+<p>Note that while the <code>--extension_configs</code> option does specify the &ldquo;markdown.extensions.footnotes&rdquo;
 extension, you still need to load the extension with the <code>-x</code> option, or the configuration for that
 extension will be ignored.</p>
 <p>The <code>--extension_configs</code> option will only support YAML configuration files if <a href="http://pyyaml.org/">PyYAML</a> is
 installed on your system. JSON should work with no additional dependencies. The format
 of your configuration file is automatically detected.</p>
 <div class="admonition warning">
 <p class="admonition-title">Warning</p>
-<p>The previously documented method of appending the extension configuration options as a string to the 
-extension name will be deprecated in Python-Markdown version 2.6. The <code>--extension_configs</code> 
+<p>The previously documented method of appending the extension configuration options as a string to the
+extension name will be deprecated in Python-Markdown version 2.6. The <code>--extension_configs</code>
 option should be used instead. See the <a href="../change_log/release-2.5/">2.5 release notes</a> for more information.</p>
 </div>
 
@@ -320,7 +320,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:10
+        Docs Build Date UTC : 2017-12-07 01:17:44
         -->
     </body>
 </html>

extensions/abbreviations/index.html

@@ -88,24 +88,24 @@ <h3>Navigation</h3>
                 <div class="bodywrapper">
                     <div class="body" role="main"><h1 id="abbreviations">Abbreviations<a class="headerlink" href="#abbreviations" title="Permanent link">&para;</a></h1>
 <h2 id="summary">Summary<a class="headerlink" href="#summary" title="Permanent link">&para;</a></h2>
-<p>The Abbreviations extension adds the ability to define abbreviations. 
+<p>The Abbreviations extension adds the ability to define abbreviations.
 Specifically, any defined abbreviation is wrapped in  an <code>&lt;abbr&gt;</code> tag.</p>
 <p>The Abbreviations extension is included in the standard Markdown library.</p>
 <h2 id="syntax">Syntax<a class="headerlink" href="#syntax" title="Permanent link">&para;</a></h2>
-<p>Abbreviations are defined using the syntax established in 
+<p>Abbreviations are defined using the syntax established in
 <a href="http://www.michelf.com/projects/php-markdown/extra/#abbr">PHP Markdown Extra</a>.</p>
 <p>Thus, the following text (taken from the above referenced PHP documentation):</p>
-<div class="codehilite"><pre><span></span>The HTML specification 
+<div class="codehilite"><pre><span></span>The HTML specification
 is maintained by the W3C.
 
-*[HTML]: Hyper Text Markup Language
-*[W3C]:  World Wide Web Consortium
+<span class="ge">*[HTML]: Hyper Text Markup Language</span>
+<span class="ge">*</span>[W3C]:  World Wide Web Consortium
 </pre></div>
 
 
 <p>will be rendered as:</p>
-<div class="codehilite"><pre><span></span><span class="nt">&lt;p&gt;</span>The <span class="nt">&lt;abbr</span> <span class="na">title=</span><span class="s">&quot;Hyper Text Markup Language&quot;</span><span class="nt">&gt;</span>HTML<span class="nt">&lt;/abbr&gt;</span> specification 
-is maintained by the <span class="nt">&lt;abbr</span> <span class="na">title=</span><span class="s">&quot;World Wide Web Consortium&quot;</span><span class="nt">&gt;</span>W3C<span class="nt">&lt;/abbr&gt;</span>.<span class="nt">&lt;/p&gt;</span>
+<div class="codehilite"><pre><span></span><span class="p">&lt;</span><span class="nt">p</span><span class="p">&gt;</span>The <span class="p">&lt;</span><span class="nt">abbr</span> <span class="na">title</span><span class="o">=</span><span class="s">&quot;Hyper Text Markup Language&quot;</span><span class="p">&gt;</span>HTML<span class="p">&lt;/</span><span class="nt">abbr</span><span class="p">&gt;</span> specification
+is maintained by the <span class="p">&lt;</span><span class="nt">abbr</span> <span class="na">title</span><span class="o">=</span><span class="s">&quot;World Wide Web Consortium&quot;</span><span class="p">&gt;</span>W3C<span class="p">&lt;/</span><span class="nt">abbr</span><span class="p">&gt;</span>.<span class="p">&lt;/</span><span class="nt">p</span><span class="p">&gt;</span>
 </pre></div>
 
 
@@ -244,7 +244,7 @@ <h3>Navigation</h3>
 
         <!--
         MkDocs version      : 0.17.2
-        Docs Build Date UTC : 2017-12-06 23:52:10
+        Docs Build Date UTC : 2017-12-07 01:17:44
         -->
     </body>
 </html>