ronn-ng 0.8.1.beta.1 → 0.10.0.pre.SNAPSHOT

data/lib/ronn/template.rb

@@ -7,6 +7,7 @@ module Ronn
     self.template_extension = 'html'
 
     def initialize(document, style_path = ENV['RONN_STYLE'].to_s.split(':'))
+      super()
       @document = document
       @style_path = style_path + [Template.template_path]
     end

data/man/ronn-format.7

@@ -1,6 +1,6 @@
-.\" generated with Ronn-NG/v0.8.1
-.\" http://github.com/apjanke/ronn-ng/tree/0.8.1.SNAPSHOT
-.TH "RONN\-FORMAT" "7" "December 2018" "Ronn-NG 0.8.1.SNAPSHOT" "Ronn Manual"
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "RONN\-FORMAT" "7" "December 2018" "Ronn-NG 0.9.1" "Ronn Manual"
 .SH "NAME"
 \fBronn\-format\fR \- manual authoring format based on Markdown
 .SH "SYNOPSIS"
@@ -85,7 +85,7 @@ Section headings should be all uppercase and may not contain inline markup\.
 .SH "INLINE MARKUP"
 Manpages have a limited set of text formatting capabilities\. There\'s basically \fBboldface\fR and \fIitalics\fR (often displayed using \fIunderline\fR)\. Ronn uses the following bits of markdown(7) to accomplish this:
 .TP
-\fB`backticks`\fR (markdown compatible)
+\fB\e`backticks\e`\fR (markdown compatible)
 Code, flags, commands, and noun\-like things; typically displayed in in \fBboldface\fR\. All text included within \fBbackticks\fR is displayed literally; other inline markup is not processed\. HTML output: \fB<code>\fR\.
 .TP
 \fB**double\-stars**\fR (markdown compatible)

data/man/ronn.1

@@ -1,6 +1,6 @@
-.\" generated with Ronn-NG/v0.8.1
-.\" http://github.com/apjanke/ronn-ng/tree/0.8.1.SNAPSHOT
-.TH "RONN" "1" "December 2018" "Ronn-NG 0.8.1.SNAPSHOT" "Ronn Manual"
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "RONN" "1" "January 2020" "Ronn-NG 0.9.1" "Ronn Manual"
 .SH "NAME"
 \fBronn\fR \- convert markdown files to manpages
 .SH "SYNOPSIS"
@@ -13,6 +13,8 @@
 \fBronn\fR \fB\-\-pipe\fR \fIfile\fR
 .br
 \fBronn\fR < \fIfile\fR
+.br
+\fBronn\fR \fB\-E\fR|\fB\-\-encoding\fR \fIencoding\fR \|\.\|\.\|\.
 .SH "DESCRIPTION"
 \fBRonn\fR converts textfiles to standard roff\-formatted Unix manpages or HTML\. ronn\-format(7) is based on markdown(7) but includes additional rules and syntax geared toward authoring manuals\.
 .P
@@ -24,6 +26,8 @@ With no \fIfile\fR arguments, \fBronn\fR acts as simple filter\. Ronn source tex
 .SH "FILES"
 The \fBronn\fR command expects input to be valid ronn\-format(7) text\. Source files are typically named \fIname\fR\.\fIsection\fR\.ronn (e\.g\., \fBexample\.1\.ronn\fR)\. The \fIname\fR and \fIsection\fR should match the name and section defined in the \fIfile\fR\'s heading\.
 .P
+Source files must be in UTF\-8 encoding, or the encoding specified by the \fB\-E\fR/\fB\-\-encoding\fR option, regardless of the locale that \fBronn\fR is running under\.
+.P
 When building roff or HTML output files, destination filenames are determined by taking the basename of the input \fIfile\fR and adding the appropriate file extension (or removing the file extension in the case of roff output)\. For example, executing \fBronn example\.1\.ronn\fR generates \fBexample\.1\fR with roff output and \fBexample\.1\.html\fR with HTML output\.
 .SH "OPTIONS"
 These options control whether output is written to file(s), standard output, or directly to a man pager\.
@@ -41,6 +45,8 @@ The server respects the \fB\-\-style\fR and document attribute options (\fB\-\-m
 \fB\-\-pipe\fR: Don\'t generate files, write generated output to standard output\. This is the default behavior when ronn source text is piped in on standard input and no \fIfile\fR arguments are provided\.
 .IP "\[ci]" 4
 \fB\-o\fR=\fIdirectory\fR, \fB\-\-output\-dir\fR=\fIdirectory\fR: Write generated files to the specified directory instead of the default location\.
+.IP "\[ci]" 4
+\fB\-E\fR=\fIencoding\fR, \fB\-\-encoding\fR=<encoding: Specify the encoding that input files are in\. Default is UTF\-8, regardless of user\'s locale settings\. Input sent to STDIN is always treated as UTF\-8, regardless of whether \fB\-E\fR is passed\.
 .IP "" 0
 .P
 Format options control the files \fBronn\fR generates, or the output format when the \fB\-\-pipe\fR argument is specified\. When no format options are given, both \fB\-\-roff\fR and \fB\-\-html\fR are assumed\.
@@ -215,8 +221,6 @@ The paging program used for man pages\. This is typically set to something like
 .TP
 \fBPAGER\fR
 Used instead of \fBMANPAGER\fR when \fBMANPAGER\fR is not defined\.
-.SH "BUGS"
-\fBRonn\fR is written in Ruby and depends on hpricot and rdiscount, extension libraries that are non\-trivial to install on some systems\. A more portable version of this program would be welcome\.
 .SH "COPYRIGHT"
 Ronn\-NG is Copyright (C) 2009 Ryan Tomayko \fIhttp://tomayko\.com/about\fR and (C) 2018 Andrew Janke \fIhttps://apjanke\.net\fR
 .SH "SEE ALSO"

data/man/ronn.1.ronn

@@ -7,7 +7,8 @@ ronn(1) -- convert markdown files to manpages
 `ronn` `-m`|`--man` <file>...<br>
 `ronn` `-S`|`--server` <file>...<br>
 `ronn` `--pipe` <file><br>
-`ronn` &lt; <file>
+`ronn` &lt; <file><br>
+`ronn` `-E`|`--encoding` <encoding> ...
 
 ## DESCRIPTION
 
@@ -35,6 +36,9 @@ The `ronn` command expects input to be valid ronn-format(7) text.  Source files
 are typically named <name>.<section>.ronn (e.g., `example.1.ronn`).  The <name>
 and <section> should match the name and section defined in the <file>'s heading.
 
+Source files must be in UTF-8 encoding, or the encoding specified by the
+`-E`/`--encoding` option, regardless of the locale that `ronn` is running under.
+
 When building roff or HTML output files, destination filenames are determined by
 taking the basename of the input <file> and adding the appropriate file
 extension (or removing the file extension in the case of roff output).  For
@@ -78,6 +82,11 @@ directly to a man pager.
   * `-o`=<directory>, `--output-dir`=<directory>:
     Write generated files to the specified directory instead of the default
     location.
+  
+  * `-E`=<encoding>, `--encoding`=<encoding:
+    Specify the encoding that input files are in. Default is UTF-8, regardless
+    of user's locale settings. Input sent to STDIN is always treated as UTF-8,
+    regardless of whether `-E` is passed.
 
 Format options control the files `ronn` generates, or the output format when the
 `--pipe` argument is specified. When no format options are given, both `--roff`
@@ -298,12 +307,6 @@ under a `man/` directory:
   * `PAGER`:
     Used instead of `MANPAGER` when `MANPAGER` is not defined.
 
-## BUGS
-
-**Ronn** is written in Ruby and depends on hpricot and rdiscount, extension
-libraries that are non-trivial to install on some systems. A more portable
-version of this program would be welcome.
-
 ## COPYRIGHT
 
 Ronn-NG is Copyright (C) 2009 Ryan Tomayko <http://tomayko.com/about> and

data/ronn-ng.gemspec

@@ -1,7 +1,8 @@
 Gem::Specification.new do |s|
   s.name = 'ronn-ng'
-  s.version = '0.8.1.beta.1'
-  s.date = '2019-02-16'
+  s.version = '0.10.0-SNAPSHOT'
+  s.date = '2020-10-22'
+  s.required_ruby_version = '>= 2.4'
 
   s.summary     = 'Builds man pages from Markdown'
   s.description = 'Ronn-NG builds manuals in HTML and Unix man page format from Markdown.'
@@ -59,7 +60,7 @@ Gem::Specification.new do |s|
     test/basic_document.html
     test/basic_document.ronn
     test/circumflexes.ronn
-    test/code_blocks.7.ronn
+    test/code_blocks.ronn
     test/contest.rb
     test/custom_title_document.html
     test/custom_title_document.ronn
@@ -103,7 +104,6 @@ Gem::Specification.new do |s|
     test/titleless_document.ronn
     test/underline_spacing_test.roff
     test/underline_spacing_test.ronn
-    test/url_formatting.ronn
   ]
   # = MANIFEST =
 
@@ -111,16 +111,16 @@ Gem::Specification.new do |s|
   s.test_files = s.files.select { |path| path =~ /^test\/.*_test.rb/ }
 
   s.extra_rdoc_files = %w[LICENSE.txt AUTHORS]
-  s.add_dependency 'mustache',    '~> 0.7', '>= 0.7.0'
-  s.add_dependency 'nokogiri',    '~> 1.9', '>= 1.9.0'
-  s.add_dependency 'rdiscount',   '~> 2.0', '>= 2.0.7'
-  s.add_development_dependency 'rack',      '~> 2.0',  '>= 2.0.6'
-  s.add_development_dependency 'rake',      '~> 12.3', '>= 12.3.0'
-  s.add_development_dependency 'rubocop',   '~> 0.60', '>= 0.57.1'
-  s.add_development_dependency 'sinatra',   '~> 2.0',  '>= 2.0.0'
-  s.add_development_dependency 'test-unit', '~> 3.2',  '>= 3.2.7'
+  s.add_dependency 'kramdown',              '~> 2.1'
+  s.add_dependency 'kramdown-parser-gfm',   '~> 1.0.1'
+  s.add_dependency 'mustache',              '~> 1.0'
+  s.add_dependency 'nokogiri',              '~> 1.9', '>= 1.9.0'
+  s.add_development_dependency 'rack',      '~> 2.2',  '>= 2.2.3'
+  s.add_development_dependency 'rake',      '~> 12.3', '>= 12.3.3'
+  s.add_development_dependency 'rubocop',   '~> 0.88', '>= 0.88.0'
+  s.add_development_dependency 'sinatra',   '~> 2.0',  '>= 2.0.8'
+  s.add_development_dependency 'test-unit', '~> 3.3',  '>= 3.3.6'
 
   s.rdoc_options = ['--line-numbers', '--inline-source', '--title', 'Ronn']
   s.require_paths = %w[lib]
-  s.rubygems_version = '1.1.1'
 end

data/test/angle_bracket_syntax.html

@@ -13,5 +13,15 @@ code block,
 
 <p>or when <code>&lt;WORD&gt;</code> is enclosed in backticks.</p>
 
-<p>or when <var>WORD</var> has a &lt;dot.&gt; or &lt;foo:colon&gt;.</p>
+<p>or when <var>WORD</var> has a <dot.> or <colon>.</colon></dot.></p>
+
+<h2 id="Escaping-angle-brackets">Escaping angle brackets</h2>
+
+<p>You can escape &lt;angle&gt; &lt;brackets&gt; with backslashes, since we're using GitHub Flavored Markdown.</p>
+
+<p>Example:</p>
+
+<p><code>pxzgrep</code> [<code>-p</code>&lt;n&gt;] [<code>-V</code>] [&lt;xzgrep options&gt;] &lt;pattern&gt; &lt;file1&gt; &lt;file2&gt; [&lt;more files&gt;]</p>
+
+<p>(Though really you should just put that in a fenced code block.)</p>
 </div>

data/test/angle_bracket_syntax.ronn

@@ -10,3 +10,13 @@ A <WORD> in angle brackets is converted to <var>WORD</var>,
 or when `<WORD>` is enclosed in backticks.
 
 or when <WORD> has a <dot.> or <foo:colon>.
+
+## Escaping angle brackets
+
+You can escape \<angle\> \<brackets\> with backslashes, since we're using GitHub Flavored Markdown.
+
+Example:
+
+`pxzgrep` [`-p`\<n\>] [`-V`] [\<xzgrep options\>] \<pattern\> \<file1\> \<file2\> [\<more files\>]
+
+(Though really you should just put that in a fenced code block.)

data/test/definition_list_syntax.html

@@ -13,9 +13,9 @@
 <dd>The definition may span
 multiple lines and even
 
-<p>start</p>
+    <p>start</p>
 
-<p>new paragraphs</p>
+    <p>new paragraphs</p>
 </dd>
 <dt>
 <code>--somearg</code>=<var>VALUE</var>

data/test/definition_list_syntax.roff

@@ -1,4 +1,4 @@
-.TH "DEFINITION_LIST_SYNTAX" "5" "January 1979" "" ""
+.TH "DEFINITION_LIST_SYNTAX" "5" "January 1979" ""
 .SH "NAME"
 \fBdefinition_list_syntax\fR \- hiya
 .P

data/test/dots_at_line_start_test.roff

@@ -1,10 +1,10 @@
-.TH "DOTS_AT_LINE_START_TEST" "" "January 1979" "" ""
+.TH "DOTS_AT_LINE_START_TEST" "" "January 1979" ""
 .SH "NAME"
 \fBdots_at_line_start_test\fR
 .P
-There\'s a weird issue where dots at the beginning of a line generate troff warnings due to escaping\.
+There's a weird issue where dots at the beginning of a line generate troff warnings due to escaping\.
 .P
-\&\.\. let\'s see what happens\.
+\&\.\. let's see what happens\.
 .IP "" 4
 .nf
 \&\. A dot on an indented line

data/test/ellipses.roff

@@ -1,7 +1,7 @@
-.TH "ELLIPSES" "7" "January 1979" "" ""
+.TH "ELLIPSES" "7" "January 1979" ""
 .SH "NAME"
 \fBellipses\fR \- testing ellipses
 .P
 Ellipses should be replaced\|\.\|\.\|\.
 .P
-\|\.\|\.\|\.also, they shouldn\'t interfere with regular dots at the beginning of a line\.
+\|\.\|\.\|\.also, they shouldn't interfere with regular dots at the beginning of a line\.

data/test/entity_encoding_test.html

@@ -15,20 +15,28 @@
 <p>Here's some special entities:</p>
 
 <ul>
-<li>&amp;bull;       •</li>
-<li>&amp;nbsp;        </li>
-<li>&amp;copy;       ©</li>
-<li>&amp;rdquo;      ”</li>
-<li>&amp;mdash;      —</li>
-<li>&amp;reg;        ®</li>
-<li>&amp;sect;       §</li>
-<li>&amp;ge;         ≥</li>
-<li>&amp;le;         ≤</li>
-<li>&amp;ne;         ≠</li>
-<li>&amp;equiv;      ≡</li>
+  <li>&amp;bull;       •</li>
+  <li>&amp;nbsp;        </li>
+  <li>&amp;copy;       ©</li>
+  <li>&amp;rdquo;      ”</li>
+  <li>&amp;mdash;      —</li>
+  <li>&amp;reg;        ®</li>
+  <li>&amp;sect;       §</li>
+  <li>&amp;ge;         ≥</li>
+  <li>&amp;le;         ≤</li>
+  <li>&amp;ne;         ≠</li>
+  <li>&amp;equiv;      ≡</li>
 </ul>
 
-
 <p>Here's a line that uses non-breaking spaces to force the
 last few words to wrap together.</p>
+
+<p>And stuff like this:</p>
+
+<p>git bulk [-g] ([-a]|[-w <ws-name>]) <git command> </git></ws-name><br>
+git bulk --addworkspace <ws-name> <ws-root-directory> (--from <url or file>) </url></ws-root-directory></ws-name><br>
+git bulk --removeworkspace &lt;ws-name&gt; <br></p>
+
+<p>Should have the <code>&amp;lt;</code>/<code>&amp;gt;</code> entities stay as <code>&amp;lt;</code>/<code>&amp;gt;</code> in HTML, but be
+turned into literal brackets in the ROFF.</p>
 </div>

data/test/entity_encoding_test.roff

@@ -1,4 +1,4 @@
-.TH "HELLO" "1" "January 1979" "" ""
+.TH "HELLO" "1" "January 1979" ""
 .SH "NAME"
 \fBhello\fR \- hello world
 .P
@@ -12,29 +12,40 @@ Your output <i>might</i> look like this:
 .fi
 .IP "" 0
 .P
-Here\'s some special entities:
-.IP "\[ci]" 4
-&bull; \[ci]
-.IP "\[ci]" 4
+Here's some special entities:
+.IP "\(bu" 4
+&bull; \(bu
+.IP "\(bu" 4
 &nbsp; \~
-.IP "\[ci]" 4
+.IP "\(bu" 4
 &copy; \(co
-.IP "\[ci]" 4
+.IP "\(bu" 4
 &rdquo; \(rs
-.IP "\[ci]" 4
+.IP "\(bu" 4
 &mdash; \(em
-.IP "\[ci]" 4
+.IP "\(bu" 4
 &reg; \(rg
-.IP "\[ci]" 4
+.IP "\(bu" 4
 &sect; \(sc
-.IP "\[ci]" 4
+.IP "\(bu" 4
 &ge; \(>=
-.IP "\[ci]" 4
+.IP "\(bu" 4
 &le; \(<=
-.IP "\[ci]" 4
+.IP "\(bu" 4
 &ne; \(!=
-.IP "\[ci]" 4
+.IP "\(bu" 4
 &equiv; \(==
 .IP "" 0
 .P
-Here\'s a line that uses non\-breaking spaces to force the last\~few\~words\~to\~wrap\~together\.
+Here's a line that uses non\-breaking spaces to force the last\~few\~words\~to\~wrap\~together\.
+.P
+And stuff like this:
+.P
+git bulk [\-g] ([\-a]|[\-w
+.br
+git bulk \-\-addworkspace
+.br
+git bulk \-\-removeworkspace <ws\-name>
+.br
+.P
+Should have the \fB&lt;\fR/\fB&gt;\fR entities stay as \fB&lt;\fR/\fB&gt;\fR in HTML, but be turned into literal brackets in the ROFF\.

data/test/entity_encoding_test.ronn

@@ -23,3 +23,12 @@ Here's some special entities:
 
 Here's a line that uses non-breaking spaces to force the
 last few words to wrap together.
+
+And stuff like this:
+
+git bulk [-g] ([-a]|[-w &lt;ws-name&gt;]) &lt;git command&gt; <br/>
+git bulk --addworkspace &lt;ws-name&gt; &lt;ws-root-directory&gt; (--from &lt;URL or file&gt;) <br/>
+git bulk --removeworkspace &lt;ws-name&gt; <br/>
+
+Should have the `&lt;`/`&gt;` entities stay as `&lt;`/`&gt;` in HTML, but be
+turned into literal brackets in the ROFF.

data/test/markdown_syntax.html

@@ -602,16 +602,15 @@ on a line by itself:</p>
 <p>That is:</p>
 
 <ul>
-<li>Square brackets containing the link identifier (optionally
+  <li>Square brackets containing the link identifier (optionally
 indented from the left margin using up to three spaces);</li>
-<li>followed by a colon;</li>
-<li>followed by one or more spaces (or tabs);</li>
-<li>followed by the URL for the link;</li>
-<li>optionally followed by a title attribute for the link, enclosed
+  <li>followed by a colon;</li>
+  <li>followed by one or more spaces (or tabs);</li>
+  <li>followed by the URL for the link;</li>
+  <li>optionally followed by a title attribute for the link, enclosed
 in double or single quotes, or enclosed in parentheses.</li>
 </ul>
 
-
 <p>The following three link definitions are equivalent:</p>
 
 <pre><code>[foo]: http://example.com/  "Optional Title Here"
@@ -853,15 +852,14 @@ for links, allowing for two styles: <em>inline</em> and <em>reference</em>.</p>
 <p>That is:</p>
 
 <ul>
-<li>An exclamation mark: <code>!</code>;</li>
-<li>followed by a set of square brackets, containing the <code>alt</code>
+  <li>An exclamation mark: <code>!</code>;</li>
+  <li>followed by a set of square brackets, containing the <code>alt</code>
 attribute text for the image;</li>
-<li>followed by a set of parentheses, containing the URL or path to
+  <li>followed by a set of parentheses, containing the URL or path to
 the image, and an optional <code>title</code> attribute enclosed in double
 or single quotes.</li>
 </ul>
 
-
 <p>Reference-style image syntax looks like this:</p>
 
 <pre><code>![Alt text][id]

data/test/markdown_syntax.roff

@@ -1,4 +1,4 @@
-.TH "MARKDOWN" "5" "January 1979" "" ""
+.TH "MARKDOWN" "5" "January 1979" ""
 .SH "NAME"
 \fBmarkdown\fR \- humane markup syntax
 .SH "SYNOPSIS"
@@ -37,15 +37,15 @@ Inline markup like _italics_,  **bold**, and `code()`\.
 .SS "Philosophy"
 Markdown is intended to be as easy\-to\-read and easy\-to\-write as is feasible\.
 .P
-Readability, however, is emphasized above all else\. A Markdown\-formatted document should be publishable as\-is, as plain text, without looking like it\'s been marked up with tags or formatting instructions\. While Markdown\'s syntax has been influenced by several existing text\-to\-HTML filters \-\- including Setext \fI\%http://docutils\.sourceforge\.net/mirror/setext\.html\fR, atx \fI\%http://www\.aaronsw\.com/2002/atx/\fR, Textile \fI\%http://textism\.com/tools/textile/\fR, reStructuredText \fI\%http://docutils\.sourceforge\.net/rst\.html\fR, Grutatext \fI\%http://www\.triptico\.com/software/grutatxt\.html\fR, and EtText \fI\%http://ettext\.taint\.org/doc/\fR \-\- the single biggest source of inspiration for Markdown\'s syntax is the format of plain text email\.
+Readability, however, is emphasized above all else\. A Markdown\-formatted document should be publishable as\-is, as plain text, without looking like it's been marked up with tags or formatting instructions\. While Markdown's syntax has been influenced by several existing text\-to\-HTML filters \-\- including Setext \fIhttp://docutils\.sourceforge\.net/mirror/setext\.html\fR, atx \fIhttp://www\.aaronsw\.com/2002/atx/\fR, Textile \fIhttp://textism\.com/tools/textile/\fR, reStructuredText \fIhttp://docutils\.sourceforge\.net/rst\.html\fR, Grutatext \fIhttp://www\.triptico\.com/software/grutatxt\.html\fR, and EtText \fIhttp://ettext\.taint\.org/doc/\fR \-\- the single biggest source of inspiration for Markdown's syntax is the format of plain text email\.
 .P
-To this end, Markdown\'s syntax is comprised entirely of punctuation characters, which punctuation characters have been carefully chosen so as to look like what they mean\. E\.g\., asterisks around a word actually look like *emphasis*\. Markdown lists look like, well, lists\. Even blockquotes look like quoted passages of text, assuming you\'ve ever used email\.
+To this end, Markdown's syntax is comprised entirely of punctuation characters, which punctuation characters have been carefully chosen so as to look like what they mean\. E\.g\., asterisks around a word actually look like *emphasis*\. Markdown lists look like, well, lists\. Even blockquotes look like quoted passages of text, assuming you've ever used email\.
 .SS "Inline HTML"
-Markdown\'s syntax is intended for one purpose: to be used as a format for \fIwriting\fR for the web\.
+Markdown's syntax is intended for one purpose: to be used as a format for \fIwriting\fR for the web\.
 .P
-Markdown is not a replacement for HTML, or even close to it\. Its syntax is very small, corresponding only to a very small subset of HTML tags\. The idea is \fInot\fR to create a syntax that makes it easier to insert HTML tags\. In my opinion, HTML tags are already easy to insert\. The idea for Markdown is to make it easy to read, write, and edit prose\. HTML is a \fIpublishing\fR format; Markdown is a \fIwriting\fR format\. Thus, Markdown\'s formatting syntax only addresses issues that can be conveyed in plain text\.
+Markdown is not a replacement for HTML, or even close to it\. Its syntax is very small, corresponding only to a very small subset of HTML tags\. The idea is \fInot\fR to create a syntax that makes it easier to insert HTML tags\. In my opinion, HTML tags are already easy to insert\. The idea for Markdown is to make it easy to read, write, and edit prose\. HTML is a \fIpublishing\fR format; Markdown is a \fIwriting\fR format\. Thus, Markdown's formatting syntax only addresses issues that can be conveyed in plain text\.
 .P
-For any markup that is not covered by Markdown\'s syntax, you simply use HTML itself\. There\'s no need to preface it or delimit it to indicate that you\'re switching from Markdown to HTML; you just use the tags\.
+For any markup that is not covered by Markdown's syntax, you simply use HTML itself\. There's no need to preface it or delimit it to indicate that you're switching from Markdown to HTML; you just use the tags\.
 .P
 The only restrictions are that block\-level HTML elements \-\- e\.g\. \fB<div>\fR, \fB<table>\fR, \fB<pre>\fR, \fB<p>\fR, etc\. \-\- must be separated from surrounding content by blank lines, and the start and end tags of the block should not be indented with tabs or spaces\. Markdown is smart enough not to add extra (unwanted) \fB<p>\fR tags around HTML block\-level tags\.
 .P
@@ -64,15 +64,15 @@ This is another regular paragraph\.
 .fi
 .IP "" 0
 .P
-Note that Markdown formatting syntax is not processed within block\-level HTML tags\. E\.g\., you can\'t use Markdown\-style \fB*emphasis*\fR inside an HTML block\.
+Note that Markdown formatting syntax is not processed within block\-level HTML tags\. E\.g\., you can't use Markdown\-style \fB*emphasis*\fR inside an HTML block\.
 .P
-Span\-level HTML tags \-\- e\.g\. \fB<span>\fR, \fB<cite>\fR, or \fB<del>\fR \-\- can be used anywhere in a Markdown paragraph, list item, or header\. If you want, you can even use HTML tags instead of Markdown formatting; e\.g\. if you\'d prefer to use HTML \fB<a>\fR or \fB<img>\fR tags instead of Markdown\'s link or image syntax, go right ahead\.
+Span\-level HTML tags \-\- e\.g\. \fB<span>\fR, \fB<cite>\fR, or \fB<del>\fR \-\- can be used anywhere in a Markdown paragraph, list item, or header\. If you want, you can even use HTML tags instead of Markdown formatting; e\.g\. if you'd prefer to use HTML \fB<a>\fR or \fB<img>\fR tags instead of Markdown's link or image syntax, go right ahead\.
 .P
 Unlike block\-level HTML tags, Markdown syntax \fIis\fR processed within span\-level tags\.
 .SS "Automatic Escaping for Special Characters"
 In HTML, there are two characters that demand special treatment: \fB<\fR and \fB&\fR\. Left angle brackets are used to start tags; ampersands are used to denote HTML entities\. If you want to use them as literal characters, you must escape them as entities, e\.g\. \fB&lt;\fR, and \fB&amp;\fR\.
 .P
-Ampersands in particular are bedeviling for web writers\. If you want to write about \'AT&T\', you need to write \'\fBAT&amp;T\fR\'\. You even need to escape ampersands within URLs\. Thus, if you want to link to:
+Ampersands in particular are bedeviling for web writers\. If you want to write about 'AT&T', you need to write '\fBAT&amp;T\fR'\. You even need to escape ampersands within URLs\. Thus, if you want to link to:
 .IP "" 4
 .nf
 http://images\.google\.com/images?num=30&q=larry+bird
@@ -111,7 +111,7 @@ AT&amp;T
 .fi
 .IP "" 0
 .P
-Similarly, because Markdown supports \fI\%#html\fR, if you use angle brackets as delimiters for HTML tags, Markdown will treat them as such\. But if you write:
+Similarly, because Markdown supports \fIinline HTML\fR, if you use angle brackets as delimiters for HTML tags, Markdown will treat them as such\. But if you write:
 .IP "" 4
 .nf
 4 < 5
@@ -130,13 +130,13 @@ However, inside Markdown code spans and blocks, angle brackets and ampersands ar
 .SS "Paragraphs and Line Breaks"
 A paragraph is simply one or more consecutive lines of text, separated by one or more blank lines\. (A blank line is any line that looks like a blank line \-\- a line containing nothing but spaces or tabs is considered blank\.) Normal paragraphs should not be indented with spaces or tabs\.
 .P
-The implication of the "one or more consecutive lines of text" rule is that Markdown supports "hard\-wrapped" text paragraphs\. This differs significantly from most other text\-to\-HTML formatters (including Movable Type\'s "Convert Line Breaks" option) which translate every line break character in a paragraph into a \fB<br />\fR tag\.
+The implication of the "one or more consecutive lines of text" rule is that Markdown supports "hard\-wrapped" text paragraphs\. This differs significantly from most other text\-to\-HTML formatters (including Movable Type's "Convert Line Breaks" option) which translate every line break character in a paragraph into a \fB<br />\fR tag\.
 .P
 When you \fIdo\fR want to insert a \fB<br />\fR break tag using Markdown, you end a line with two or more spaces, then type return\.
 .P
-Yes, this takes a tad more effort to create a \fB<br />\fR, but a simplistic "every line break is a \fB<br />\fR" rule wouldn\'t work for Markdown\. Markdown\'s email\-style \fI\%#blockquote\fR and multi\-paragraph \fI\%#list\fR work best \-\- and look better \-\- when you format them with hard breaks\.
+Yes, this takes a tad more effort to create a \fB<br />\fR, but a simplistic "every line break is a \fB<br />\fR" rule wouldn't work for Markdown\. Markdown's email\-style \fIblockquoting\fR and multi\-paragraph \fIlist items\fR work best \-\- and look better \-\- when you format them with hard breaks\.
 .SS "Headers"
-Markdown supports two styles of headers, Setext \fI\%http://docutils\.sourceforge\.net/mirror/setext\.html\fR and atx \fI\%http://www\.aaronsw\.com/2002/atx/\fR\.
+Markdown supports two styles of headers, Setext \fIhttp://docutils\.sourceforge\.net/mirror/setext\.html\fR and atx \fIhttp://www\.aaronsw\.com/2002/atx/\fR\.
 .P
 Setext\-style headers are "underlined" using equal signs (for first\-level headers) and dashes (for second\-level headers)\. For example:
 .IP "" 4
@@ -149,7 +149,7 @@ This is an H2
 .fi
 .IP "" 0
 .P
-Any number of underlining \fB=\fR\'s or \fB\-\fR\'s will work\.
+Any number of underlining \fB=\fR's or \fB\-\fR's will work\.
 .P
 Atx\-style headers use 1\-6 hash characters at the start of the line, corresponding to header levels 1\-6\. For example:
 .IP "" 4
@@ -162,7 +162,7 @@ Atx\-style headers use 1\-6 hash characters at the start of the line, correspond
 .fi
 .IP "" 0
 .P
-Optionally, you may "close" atx\-style headers\. This is purely cosmetic \-\- you can use this if you think it looks better\. The closing hashes don\'t even need to match the number of hashes used to open the header\. (The number of opening hashes determines the header level\.) :
+Optionally, you may "close" atx\-style headers\. This is purely cosmetic \-\- you can use this if you think it looks better\. The closing hashes don't even need to match the number of hashes used to open the header\. (The number of opening hashes determines the header level\.) :
 .IP "" 4
 .nf
 # This is an H1 #
@@ -173,7 +173,7 @@ Optionally, you may "close" atx\-style headers\. This is purely cosmetic \-\- yo
 .fi
 .IP "" 0
 .SS "Blockquotes"
-Markdown uses email\-style \fB>\fR characters for blockquoting\. If you\'re familiar with quoting passages of text in an email message, then you know how to create a blockquote in Markdown\. It looks best if you hard wrap the text and put a \fB>\fR before every line:
+Markdown uses email\-style \fB>\fR characters for blockquoting\. If you're familiar with quoting passages of text in an email message, then you know how to create a blockquote in Markdown\. It looks best if you hard wrap the text and put a \fB>\fR before every line:
 .IP "" 4
 .nf
 > This is a blockquote with two paragraphs\. Lorem ipsum dolor sit amet,
@@ -216,7 +216,7 @@ Blockquotes can contain other Markdown elements, including headers, lists, and c
 > 1\.   This is the first list item\.
 > 2\.   This is the second list item\.
 >
-> Here\'s some example code:
+> Here's some example code:
 >
 >     return shell_exec("echo $input | $markdown_script");
 .fi
@@ -262,7 +262,7 @@ Ordered lists use numbers followed by periods:
 .fi
 .IP "" 0
 .P
-It\'s important to note that the actual numbers you use to mark the list have no effect on the HTML output Markdown produces\. The HTML Markdown produces from the above list is:
+It's important to note that the actual numbers you use to mark the list have no effect on the HTML output Markdown produces\. The HTML Markdown produces from the above list is:
 .IP "" 4
 .nf
 <ol>
@@ -291,7 +291,7 @@ or even:
 .fi
 .IP "" 0
 .P
-you\'d get the exact same HTML output\. The point is, if you want to, you can use ordinal numbers in your ordered Markdown lists, so that the numbers in your source match the numbers in your published HTML\. But if you want to be lazy, you don\'t have to\.
+you'd get the exact same HTML output\. The point is, if you want to, you can use ordinal numbers in your ordered Markdown lists, so that the numbers in your source match the numbers in your published HTML\. But if you want to be lazy, you don't have to\.
 .P
 If you do use lazy list numbering, however, you should still start the list with the number 1\. At some point in the future, Markdown may support starting ordered lists at an arbitrary number\.
 .P
@@ -308,7 +308,7 @@ To make lists look nice, you can wrap items with hanging indents:
 .fi
 .IP "" 0
 .P
-But if you want to be lazy, you don\'t have to:
+But if you want to be lazy, you don't have to:
 .IP "" 4
 .nf
 *   Lorem ipsum dolor sit amet, consectetuer adipiscing elit\.
@@ -376,7 +376,7 @@ It looks nice if you indent every line of the subsequent paragraphs, but here ag
 .nf
 *   This is a list item with two paragraphs\.
 
-    This is the second paragraph in the list item\. You\'re
+    This is the second paragraph in the list item\. You're
 only required to indent the first line\. Lorem ipsum dolor
 sit amet, consectetuer adipiscing elit\.
 
@@ -384,7 +384,7 @@ sit amet, consectetuer adipiscing elit\.
 .fi
 .IP "" 0
 .P
-To put a blockquote within a list item, the blockquote\'s \fB>\fR delimiters need to be indented:
+To put a blockquote within a list item, the blockquote's \fB>\fR delimiters need to be indented:
 .IP "" 4
 .nf
 *   A list item with a blockquote:
@@ -403,7 +403,7 @@ To put a code block within a list item, the code block needs to be indented \fIt
 .fi
 .IP "" 0
 .P
-It\'s worth noting that it\'s possible to trigger an ordered list by accident, by writing something like this:
+It's worth noting that it's possible to trigger an ordered list by accident, by writing something like this:
 .IP "" 4
 .nf
 1986\. What a great season\.
@@ -482,7 +482,7 @@ will turn into:
 .fi
 .IP "" 0
 .P
-Regular Markdown syntax is not processed within code blocks\. E\.g\., asterisks are just literal asterisks within a code block\. This means it\'s also easy to use Markdown to write about Markdown\'s own syntax\.
+Regular Markdown syntax is not processed within code blocks\. E\.g\., asterisks are just literal asterisks within a code block\. This means it's also easy to use Markdown to write about Markdown's own syntax\.
 .SS "Horizontal Rules"
 You can produce a horizontal rule tag (\fB<hr />\fR) by placing three or more hyphens, asterisks, or underscores on a line by themselves\. If you wish, you may use spaces between the hyphens or asterisks\. Each of the following lines will produce a horizontal rule:
 .IP "" 4
@@ -504,7 +504,7 @@ Markdown supports two style of links: \fIinline\fR and \fIreference\fR\.
 .P
 In both styles, the link text is delimited by [square brackets]\.
 .P
-To create an inline link, use a set of regular parentheses immediately after the link text\'s closing square bracket\. Inside the parentheses, put the URL where you want the link to point, along with an \fIoptional\fR title for the link, surrounded in quotes\. For example:
+To create an inline link, use a set of regular parentheses immediately after the link text's closing square bracket\. Inside the parentheses, put the URL where you want the link to point, along with an \fIoptional\fR title for the link, surrounded in quotes\. For example:
 .IP "" 4
 .nf
 This is [an example](http://example\.com/ "Title") inline link\.
@@ -524,7 +524,7 @@ title attribute\.</p>
 .fi
 .IP "" 0
 .P
-If you\'re referring to a local resource on the same server, you can use relative paths:
+If you're referring to a local resource on the same server, you can use relative paths:
 .IP "" 4
 .nf
 See my [About](/about/) page for details\.
@@ -553,15 +553,15 @@ Then, anywhere in the document, you define your link label like this, on a line
 .IP "" 0
 .P
 That is:
-.IP "\[ci]" 4
+.IP "\(bu" 4
 Square brackets containing the link identifier (optionally indented from the left margin using up to three spaces);
-.IP "\[ci]" 4
+.IP "\(bu" 4
 followed by a colon;
-.IP "\[ci]" 4
+.IP "\(bu" 4
 followed by one or more spaces (or tabs);
-.IP "\[ci]" 4
+.IP "\(bu" 4
 followed by the URL for the link;
-.IP "\[ci]" 4
+.IP "\(bu" 4
 optionally followed by a title attribute for the link, enclosed in double or single quotes, or enclosed in parentheses\.
 .IP "" 0
 .P
@@ -569,7 +569,7 @@ The following three link definitions are equivalent:
 .IP "" 4
 .nf
 [foo]: http://example\.com/  "Optional Title Here"
-[foo]: http://example\.com/  \'Optional Title Here\'
+[foo]: http://example\.com/  'Optional Title Here'
 [foo]: http://example\.com/  (Optional Title Here)
 .fi
 .IP "" 0
@@ -631,9 +631,9 @@ And then define the link:
 .fi
 .IP "" 0
 .P
-Link definitions can be placed anywhere in your Markdown document\. I tend to put them immediately after each paragraph in which they\'re used, but if you want, you can put them all at the end of your document, sort of like footnotes\.
+Link definitions can be placed anywhere in your Markdown document\. I tend to put them immediately after each paragraph in which they're used, but if you want, you can put them all at the end of your document, sort of like footnotes\.
 .P
-Here\'s an example of reference links in action:
+Here's an example of reference links in action:
 .IP "" 4
 .nf
 I get 10 times more traffic from [Google] [1] than from
@@ -667,7 +667,7 @@ or <a href="http://search\.msn\.com/" title="MSN Search">MSN</a>\.</p>
 .fi
 .IP "" 0
 .P
-For comparison, here is the same paragraph written using Markdown\'s inline link style:
+For comparison, here is the same paragraph written using Markdown's inline link style:
 .IP "" 4
 .nf
 I get 10 times more traffic from [Google](http://google\.com/ "Google")
@@ -676,11 +676,11 @@ than from [Yahoo](http://search\.yahoo\.com/ "Yahoo Search") or
 .fi
 .IP "" 0
 .P
-The point of reference\-style links is not that they\'re easier to write\. The point is that with reference\-style links, your document source is vastly more readable\. Compare the above examples: using reference\-style links, the paragraph itself is only 81 characters long; with inline\-style links, it\'s 176 characters; and as raw HTML, it\'s 234 characters\. In the raw HTML, there\'s more markup than there is text\.
+The point of reference\-style links is not that they're easier to write\. The point is that with reference\-style links, your document source is vastly more readable\. Compare the above examples: using reference\-style links, the paragraph itself is only 81 characters long; with inline\-style links, it's 176 characters; and as raw HTML, it's 234 characters\. In the raw HTML, there's more markup than there is text\.
 .P
-With Markdown\'s reference\-style links, a source document much more closely resembles the final output, as rendered in a browser\. By allowing you to move the markup\-related metadata out of the paragraph, you can add links without interrupting the narrative flow of your prose\.
+With Markdown's reference\-style links, a source document much more closely resembles the final output, as rendered in a browser\. By allowing you to move the markup\-related metadata out of the paragraph, you can add links without interrupting the narrative flow of your prose\.
 .SS "Emphasis"
-Markdown treats asterisks (\fB*\fR) and underscores (\fB_\fR) as indicators of emphasis\. Text wrapped with one \fB*\fR or \fB_\fR will be wrapped with an HTML \fB<em>\fR tag; double \fB*\fR\'s or \fB_\fR\'s will be wrapped with an HTML \fB<strong>\fR tag\. E\.g\., this input:
+Markdown treats asterisks (\fB*\fR) and underscores (\fB_\fR) as indicators of emphasis\. Text wrapped with one \fB*\fR or \fB_\fR will be wrapped with an HTML \fB<em>\fR tag; double \fB*\fR's or \fB_\fR's will be wrapped with an HTML \fB<strong>\fR tag\. E\.g\., this input:
 .IP "" 4
 .nf
 *single asterisks*
@@ -715,7 +715,7 @@ un*frigging*believable
 .fi
 .IP "" 0
 .P
-But if you surround an \fB*\fR or \fB_\fR with spaces, it\'ll be treated as a literal asterisk or underscore\.
+But if you surround an \fB*\fR or \fB_\fR with spaces, it'll be treated as a literal asterisk or underscore\.
 .P
 To produce a literal asterisk or underscore at a position where it would otherwise be used as an emphasis delimiter, you can backslash escape it:
 .IP "" 4
@@ -773,14 +773,14 @@ will produce:
 With a code span, ampersands and angle brackets are encoded as HTML entities automatically, which makes it easy to include example HTML tags\. Markdown will turn this:
 .IP "" 4
 .nf
-Please don\'t use any `<blink>` tags\.
+Please don't use any `<blink>` tags\.
 .fi
 .IP "" 0
 .P
 into:
 .IP "" 4
 .nf
-<p>Please don\'t use any <code>&lt;blink&gt;</code> tags\.</p>
+<p>Please don't use any <code>&lt;blink&gt;</code> tags\.</p>
 .fi
 .IP "" 0
 .P
@@ -799,7 +799,7 @@ equivalent of <code>&amp;mdash;</code>\.</p>
 .fi
 .IP "" 0
 .SS "Images"
-Admittedly, it\'s fairly difficult to devise a "natural" syntax for placing images into a plain text document format\.
+Admittedly, it's fairly difficult to devise a "natural" syntax for placing images into a plain text document format\.
 .P
 Markdown uses an image syntax that is intended to resemble the syntax for links, allowing for two styles: \fIinline\fR and \fIreference\fR\.
 .P
@@ -813,11 +813,11 @@ Inline image syntax looks like this:
 .IP "" 0
 .P
 That is:
-.IP "\[ci]" 4
+.IP "\(bu" 4
 An exclamation mark: \fB!\fR;
-.IP "\[ci]" 4
+.IP "\(bu" 4
 followed by a set of square brackets, containing the \fBalt\fR attribute text for the image;
-.IP "\[ci]" 4
+.IP "\(bu" 4
 followed by a set of parentheses, containing the URL or path to the image, and an optional \fBtitle\fR attribute enclosed in double or single quotes\.
 .IP "" 0
 .P
@@ -871,9 +871,9 @@ into something like this:
 .P
 which will render in a browser as a clickable link to "address@example\.com"\.
 .P
-(This sort of entity\-encoding trick will indeed fool many, if not most, address\-harvesting bots, but it definitely won\'t fool all of them\. It\'s better than nothing, but an address published in this way will probably eventually start receiving spam\.)
+(This sort of entity\-encoding trick will indeed fool many, if not most, address\-harvesting bots, but it definitely won't fool all of them\. It's better than nothing, but an address published in this way will probably eventually start receiving spam\.)
 .SS "Backslash Escapes"
-Markdown allows you to use backslash escapes to generate literal characters which would otherwise have special meaning in Markdown\'s formatting syntax\. For example, if you wanted to surround a word with literal asterisks (instead of an HTML \fB<em>\fR tag), you can use backslashes before the asterisks, like this:
+Markdown allows you to use backslash escapes to generate literal characters which would otherwise have special meaning in Markdown's formatting syntax\. For example, if you wanted to surround a word with literal asterisks (instead of an HTML \fB<em>\fR tag), you can use backslashes before the asterisks, like this:
 .IP "" 4
 .nf
 \e*literal asterisks\e*
@@ -900,8 +900,8 @@ _   underscore
 .SH "AUTHOR"
 Markdown was created by John Gruber\.
 .P
-Manual page by Ryan Tomayko\. It\'s pretty much a direct copy of the Markdown Syntax Reference \fI\%http://daringfireball\.net/projects/markdown/syntax\fR, also by John Gruber\.
+Manual page by Ryan Tomayko\. It's pretty much a direct copy of the Markdown Syntax Reference \fIhttp://daringfireball\.net/projects/markdown/syntax\fR, also by John Gruber\.
 .SH "SEE ALSO"
 ronn(5)
 .br
-\fI\%http://daringfireball\.net/projects/markdown/\fR
+\fIhttp://daringfireball\.net/projects/markdown/\fR