...
\end{verbatim}
A shortcut form can also be used for specifying the language of the code
block:
\begin{verbatim}
```haskell
qsort [] = []
```
\end{verbatim}
This is equivalent to:
\begin{verbatim}
``` {.haskell}
qsort [] = []
```
\end{verbatim}
To prevent all highlighting, use the \texttt{-{}-no-highlight} flag. To
set the highlighting style, use \texttt{-{}-highlight-style}.
\subsection{Lists}
\subsubsection{Bullet lists}
A bullet list is a list of bulleted list items. A bulleted list item
begins with a bullet (\texttt{*}, \texttt{+}, or \texttt{-}). Here is a
simple example:
\begin{verbatim}
* one
* two
* three
\end{verbatim}
This will produce a ``compact'' list. If you want a ``loose'' list, in
which each item is formatted as a paragraph, put spaces between the
items:
\begin{verbatim}
* one
* two
* three
\end{verbatim}
The bullets need not be flush with the left margin; they may be indented
one, two, or three spaces. The bullet must be followed by whitespace.
List items look best if subsequent lines are flush with the first line
(after the bullet):
\begin{verbatim}
* here is my first
list item.
* and my second.
\end{verbatim}
But markdown also allows a ``lazy'' format:
\begin{verbatim}
* here is my first
list item.
* and my second.
\end{verbatim}
\subsubsection{The four-space rule}
A list item may contain multiple paragraphs and other block-level
content. However, subsequent paragraphs must be preceded by a blank line
and indented four spaces or a tab. The list will look better if the
first paragraph is aligned with the rest:
\begin{verbatim}
* First paragraph.
Continued.
* Second paragraph. With a code block, which must be indented
eight spaces:
{ code }
\end{verbatim}
List items may include other lists. In this case the preceding blank
line is optional. The nested list must be indented four spaces or one
tab:
\begin{verbatim}
* fruits
+ apples
- macintosh
- red delicious
+ pears
+ peaches
* vegetables
+ brocolli
+ chard
\end{verbatim}
As noted above, markdown allows you to write list items ``lazily,''
instead of indenting continuation lines. However, if there are multiple
paragraphs or other blocks in a list item, the first line of each must
be indented.
\begin{verbatim}
+ A lazy, lazy, list
item.
+ Another one; this looks
bad but is legal.
Second paragraph of second
list item.
\end{verbatim}
\textbf{Note:} Although the four-space rule for continuation paragraphs
comes from the official
\href{http://daringfireball.net/projects/markdown/syntax\#list}{markdown
syntax guide}, the reference implementation, \texttt{Markdown.pl}, does
not follow it. So pandoc will give different results than
\texttt{Markdown.pl} when authors have indented continuation paragraphs
fewer than four spaces.
The
\href{http://daringfireball.net/projects/markdown/syntax\#list}{markdown
syntax guide} is not explicit whether the four-space rule applies to
\emph{all} block-level content in a list item; it only mentions
paragraphs and code blocks. But it implies that the rule applies to all
block-level content (including nested lists), and pandoc interprets it
that way.
\subsubsection{Ordered lists}
Ordered lists work just like bulleted lists, except that the items begin
with enumerators rather than bullets.
In standard markdown, enumerators are decimal numbers followed by a
period and a space. The numbers themselves are ignored, so there is no
difference between this list:
\begin{verbatim}
1. one
2. two
3. three
\end{verbatim}
and this one:
\begin{verbatim}
5. one
7. two
1. three
\end{verbatim}
\emph{Pandoc extension}.
Unlike standard markdown, Pandoc allows ordered list items to be marked
with uppercase and lowercase letters and roman numerals, in addition to
arabic numerals. List markers may be enclosed in parentheses or followed
by a single right-parentheses or period. They must be separated from the
text that follows by at least one space, and, if the list marker is a
capital letter with a period, by at least two spaces.\footnote{The point
of this rule is to ensure that normal paragraphs starting with
people's initials, like
\begin{Verbatim}
B. Russell was an English philosopher.
\end{Verbatim}
do not get treated as list items.
This rule will not prevent
\begin{Verbatim}
(C) 2007 Joe Smith
\end{Verbatim}
from being interpreted as a list item. In this case, a backslash
escape can be used:
\begin{Verbatim}
(C\) 2007 Joe Smith
\end{Verbatim}
}
Pandoc also pays attention to the type of list marker used, and to the
starting number, and both of these are preserved where possible in the
output format. Thus, the following yields a list with numbers followed
by a single parenthesis, starting with 9, and a sublist with lowercase
roman numerals:
\begin{verbatim}
9) Ninth
10) Tenth
11) Eleventh
i. subone
ii. subtwo
iii. subthree
\end{verbatim}
Note that Pandoc pays attention only to the \emph{starting} marker in a
list. So, the following yields a list numbered sequentially starting
from 2:
\begin{verbatim}
(2) Two
(5) Three
1. Four
* Five
\end{verbatim}
If default list markers are desired, use \texttt{\#.}:
\begin{verbatim}
#. one
#. two
#. three
\end{verbatim}
\subsubsection{Definition lists}
\emph{Pandoc extension}.
Pandoc supports definition lists, using a syntax inspired by
\href{http://www.michelf.com/projects/php-markdown/extra/}{PHP Markdown
Extra} and
\href{http://docutils.sourceforge.net/docs/ref/rst/introduction.html}{reStructuredText}:\footnote{I
have also been influenced by the suggestions of
\href{http://www.justatheory.com/computers/markup/modest-markdown-proposal.html}{David
Wheeler}.}
\begin{verbatim}
Term 1
: Definition 1
Term 2 with *inline markup*
: Definition 2
{ some code, part of Definition 2 }
Third paragraph of definition 2.
\end{verbatim}
Each term must fit on one line, which may optionally be followed by a
blank line, and must be followed by one or more definitions. A
definition begins with a colon or tilde, which may be indented one or
two spaces. The body of the definition (including the first line, aside
from the colon or tilde) should be indented four spaces. A term may have
multiple definitions, and each definition may consist of one or more
block elements (paragraph, code block, list, etc.), each indented four
spaces or one tab stop.
If you leave space after the definition (as in the example above), the
blocks of the definitions will be considered paragraphs. In some output
formats, this will mean greater spacing between term/definition pairs.
For a compact definition list, do not leave space between the definition
and the next term:
\begin{verbatim}
Term 1
~ Definition 1
Term 2
~ Definition 2a
~ Definition 2b
\end{verbatim}
\subsubsection{Numbered example lists}
\emph{Pandoc extension}.
The special list marker \texttt{@} can be used for sequentially numbered
examples. The first list item with a \texttt{@} marker will be numbered
`1', the next `2', and so on, throughout the document. The numbered
examples need not occur in a single list; each new list using \texttt{@}
will take up where the last stopped. So, for example:
\begin{verbatim}
(@) My first example will be numbered (1).
(@) My second example will be numbered (2).
Explanation of examples.
(@) My third example will be numbered (3).
\end{verbatim}
Numbered examples can be labeled and referred to elsewhere in the
document:
\begin{verbatim}
(@good) This is a good example.
As (@good) illustrates, ...
\end{verbatim}
The label can be any string of alphanumeric characters, underscores, or
hyphens.
\subsubsection{Compact and loose lists}
Pandoc behaves differently from \texttt{Markdown.pl} on some ``edge
cases'' involving lists. Consider this source:
\begin{verbatim}
+ First
+ Second:
- Fee
- Fie
- Foe
+ Third
\end{verbatim}
Pandoc transforms this into a ``compact list'' (with no
\texttt{\textless{}p\textgreater{}} tags around ``First'', ``Second'',
or ``Third''), while markdown puts \texttt{\textless{}p\textgreater{}}
tags around ``Second'' and ``Third'' (but not ``First''), because of the
blank space around ``Third''. Pandoc follows a simple rule: if the text
is followed by a blank line, it is treated as a paragraph. Since
``Second'' is followed by a list, and not a blank line, it isn't treated
as a paragraph. The fact that the list is followed by a blank line is
irrelevant. (Note: Pandoc works this way even when the
\texttt{-{}-strict} option is specified. This behavior is consistent
with the official markdown syntax description, even though it is
different from that of \texttt{Markdown.pl}.)
\subsubsection{Ending a list}
What if you want to put an indented code block after a list?
\begin{verbatim}
- item one
- item two
{ my code block }
\end{verbatim}
Trouble! Here pandoc (like other markdown implementations) will treat
\texttt{\{ my code block \}} as the second paragraph of item two, and
not as a code block.
To ``cut off'' the list after item two, you can insert some non-indented
content, like an HTML comment, which won't produce visible output in any
format:
\begin{verbatim}
- item one
- item two
{ my code block }
\end{verbatim}
You can use the same trick if you want two consecutive lists instead of
one big list:
\begin{verbatim}
1. one
2. two
3. three
1. uno
2. dos
3. tres
\end{verbatim}
\subsection{Horizontal rules}
A line containing a row of three or more \texttt{*}, \texttt{-}, or
\texttt{\_} characters (optionally separated by spaces) produces a
horizontal rule:
\begin{verbatim}
* * * *
---------------
\end{verbatim}
\subsection{Tables}
\emph{Pandoc extension}.
Three kinds of tables may be used. All three kinds presuppose the use of
a fixed-width font, such as Courier.
\textbf{Simple tables} look like this:
\begin{verbatim}
Right Left Center Default
------- ------ ---------- -------
12 12 12 12
123 123 123 123
1 1 1 1
Table: Demonstration of simple table syntax.
\end{verbatim}
The headers and table rows must each fit on one line. Column alignments
are determined by the position of the header text relative to the dashed
line below it:\footnote{This scheme is due to Michel Fortin, who
proposed it on the
\href{http://six.pairlist.net/pipermail/markdown-discuss/2005-March/001097.html}{Markdown
discussion list}.}
\begin{itemize}
\item
If the dashed line is flush with the header text on the right side but
extends beyond it on the left, the column is right-aligned.
\item
If the dashed line is flush with the header text on the left side but
extends beyond it on the right, the column is left-aligned.
\item
If the dashed line extends beyond the header text on both sides, the
column is centered.
\item
If the dashed line is flush with the header text on both sides, the
default alignment is used (in most cases, this will be left).
\end{itemize}
The table must end with a blank line, or a line of dashes followed by a
blank line. A caption may optionally be provided (as illustrated in the
example above). A caption is a paragraph beginning with the string
\texttt{Table:} (or just \texttt{:}), which will be stripped off. It may
appear either before or after the table.
The column headers may be omitted, provided a dashed line is used to end
the table. For example:
\begin{verbatim}
------- ------ ---------- -------
12 12 12 12
123 123 123 123
1 1 1 1
------- ------ ---------- -------
\end{verbatim}
When headers are omitted, column alignments are determined on the basis
of the first line of the table body. So, in the tables above, the
columns would be right, left, center, and right aligned, respectively.
\textbf{Multiline tables} allow headers and table rows to span multiple
lines of text (but cells that span multiple columns or rows of the table
are not supported). Here is an example:
\begin{verbatim}
-------------------------------------------------------------
Centered Default Right Left
Header Aligned Aligned Aligned
----------- ------- --------------- -------------------------
First row 12.0 Example of a row that
spans multiple lines.
Second row 5.0 Here's another one. Note
the blank line between
rows.
-------------------------------------------------------------
Table: Here's the caption. It, too, may span
multiple lines.
\end{verbatim}
These work like simple tables, but with the following differences:
\begin{itemize}
\item
They must begin with a row of dashes, before the header text (unless
the headers are omitted).
\item
They must end with a row of dashes, then a blank line.
\item
The rows must be separated by blank lines.
\end{itemize}
In multiline tables, the table parser pays attention to the widths of
the columns, and the writers try to reproduce these relative widths in
the output. So, if you find that one of the columns is too narrow in the
output, try widening it in the markdown source.
Headers may be omitted in multiline tables as well as simple tables:
\begin{verbatim}
----------- ------- --------------- -------------------------
First row 12.0 Example of a row that
spans multiple lines.
Second row 5.0 Here's another one. Note
the blank line between
rows.
-------------------------------------------------------------
: Here's a multiline table without headers.
\end{verbatim}
It is possible for a multiline table to have just one row, but the row
should be followed by a blank line (and then the row of dashes that ends
the table), or the table may be interpreted as a simple table.
\textbf{Grid tables} look like this:
\begin{verbatim}
: Sample grid table.
+---------------+---------------+--------------------+
| Fruit | Price | Advantages |
+===============+===============+====================+
| Bananas | $1.34 | - built-in wrapper |
| | | - bright color |
+---------------+---------------+--------------------+
| Oranges | $2.10 | - cures scurvy |
| | | - tasty |
+---------------+---------------+--------------------+
\end{verbatim}
The row of \texttt{=}s separates the header from the table body, and can
be omitted for a headerless table. The cells of grid tables may contain
arbitrary block elements (multiple paragraphs, code blocks, lists,
etc.). Alignments are not supported, nor are cells that span multiple
columns or rows. Grid tables can be created easily using
\href{http://table.sourceforge.net/}{Emacs table mode}.
\subsection{Title block}
\emph{Pandoc extension}.
If the file begins with a title block
\begin{verbatim}
% title
% author(s) (separated by semicolons)
% date
\end{verbatim}
it will be parsed as bibliographic information, not regular text. (It
will be used, for example, in the title of standalone LaTeX or HTML
output.) The block may contain just a title, a title and an author, or
all three elements. If you want to include an author but no title, or a
title and a date but no author, you need a blank line:
\begin{verbatim}
%
% Author
% My title
%
% June 15, 2006
\end{verbatim}
The title may occupy multiple lines, but continuation lines must begin
with leading space, thus:
\begin{verbatim}
% My title
on multiple lines
\end{verbatim}
If a document has multiple authors, the authors may be put on separate
lines with leading space, or separated by semicolons, or both. So, all
of the following are equivalent:
\begin{verbatim}
% Author One
Author Two
% Author One; Author Two
% Author One;
Author Two
\end{verbatim}
The date must fit on one line.
All three metadata fields may contain standard inline formatting
(italics, links, footnotes, etc.).
Title blocks will always be parsed, but they will affect the output only
when the \texttt{-{}-standalone} (\texttt{-s}) option is chosen. In HTML
output, titles will appear twice: once in the document head -- this is
the title that will appear at the top of the window in a browser -- and
once at the beginning of the document body. The title in the document
head can have an optional prefix attached (\texttt{-{}-title-prefix} or
\texttt{-T} option). The title in the body appears as an H1 element with
class ``title'', so it can be suppressed or reformatted with CSS. If a
title prefix is specified with \texttt{-T} and no title block appears in
the document, the title prefix will be used by itself as the HTML title.
The man page writer extracts a title, man page section number, and other
header and footer information from the title line. The title is assumed
to be the first word on the title line, which may optionally end with a
(single-digit) section number in parentheses. (There should be no space
between the title and the parentheses.) Anything after this is assumed
to be additional footer and header text. A single pipe character
(\texttt{\textbar{}}) should be used to separate the footer text from
the header text. Thus,
\begin{verbatim}
% PANDOC(1)
\end{verbatim}
will yield a man page with the title \texttt{PANDOC} and section 1.
\begin{verbatim}
% PANDOC(1) Pandoc User Manuals
\end{verbatim}
will also have ``Pandoc User Manuals'' in the footer.
\begin{verbatim}
% PANDOC(1) Pandoc User Manuals | Version 4.0
\end{verbatim}
will also have ``Version 4.0'' in the header.
\subsection{Backslash escapes}
Except inside a code block or inline code, any punctuation or space
character preceded by a backslash will be treated literally, even if it
would normally indicate formatting. Thus, for example, if one writes
\begin{verbatim}
*\*hello\**
\end{verbatim}
one will get
\begin{verbatim}
*hello*
\end{verbatim}
instead of
\begin{verbatim}
hello
\end{verbatim}
This rule is easier to remember than standard markdown's rule, which
allows only the following characters to be backslash-escaped:
\begin{verbatim}
\`*_{}[]()>#+-.!
\end{verbatim}
(However, if the \texttt{-{}-strict} option is supplied, the standard
markdown rule will be used.)
A backslash-escaped space is parsed as a nonbreaking space. It will
appear in TeX output as \texttt{\textasciitilde{}} and in HTML and XML
as \texttt{\textbackslash{}\&\#160;} or
\texttt{\textbackslash{}\ }.
A backslash-escaped newline (i.e.~a backslash occurring at the end of a
line) is parsed as a hard line break. It will appear in TeX output as
\texttt{\textbackslash{}\textbackslash{}} and in HTML as
\texttt{\textless{}br /\textgreater{}}. This is a nice alternative to
markdown's ``invisible'' way of indicating hard line breaks using two
trailing spaces on a line.
Backslash escapes do not work in verbatim contexts.
\subsection{Smart punctuation}
\emph{Pandoc extension}.
If the \texttt{-{}-smart} option is specified, pandoc will produce
typographically correct output, converting straight quotes to curly
quotes, \texttt{-{}-{}-} to em-dashes, \texttt{-{}-} to en-dashes, and
\texttt{...} to ellipses. Nonbreaking spaces are inserted after certain
abbreviations, such as ``Mr.''
Note: if your LaTeX template uses the \texttt{csquotes} package, pandoc
will detect automatically this and use
\texttt{\textbackslash{}enquote\{...\}} for quoted text.
\hyperdef{}{inline-formatting}{\subsection{Inline
formatting}\label{inline-formatting}}
\subsubsection{Emphasis}
To \emph{emphasize} some text, surround it with \texttt{*}s or
\texttt{\_}, like this:
\begin{verbatim}
This text is _emphasized with underscores_, and this
is *emphasized with asterisks*.
\end{verbatim}
Double \texttt{*} or \texttt{\_} produces \textbf{strong emphasis}:
\begin{verbatim}
This is **strong emphasis** and __with underscores__.
\end{verbatim}
A \texttt{*} or \texttt{\_} character surrounded by spaces, or
backslash-escaped, will not trigger emphasis:
\begin{verbatim}
This is * not emphasized *, and \*neither is this\*.
\end{verbatim}
Because \texttt{\_} is sometimes used inside words and identifiers,
pandoc does not interpret a \texttt{\_} surrounded by alphanumeric
characters as an emphasis marker. If you want to emphasize just part of
a word, use \texttt{*}:
\begin{verbatim}
feas*ible*, not feas*able*.
\end{verbatim}
\subsubsection{Strikeout}
\emph{Pandoc extension}.
To strikeout a section of text with a horizontal line, begin and end it
with \texttt{\textasciitilde{}\textasciitilde{}}. Thus, for example,
\begin{verbatim}
This ~~is deleted text.~~
\end{verbatim}
\subsubsection{Superscripts and subscripts}
\emph{Pandoc extension}.
Superscripts may be written by surrounding the superscripted text by
\texttt{\^{}} characters; subscripts may be written by surrounding the
subscripted text by \texttt{\textasciitilde{}} characters. Thus, for
example,
\begin{verbatim}
H~2~O is a liquid. 2^10^ is 1024.
\end{verbatim}
If the superscripted or subscripted text contains spaces, these spaces
must be escaped with backslashes. (This is to prevent accidental
superscripting and subscripting through the ordinary use of
\texttt{\textasciitilde{}} and \texttt{\^{}}.) Thus, if you want the
letter P with `a cat' in subscripts, use
\texttt{P\textasciitilde{}a\textbackslash{} cat\textasciitilde{}}, not
\texttt{P\textasciitilde{}a cat\textasciitilde{}}.
\subsubsection{Verbatim}
To make a short span of text verbatim, put it inside backticks:
\begin{verbatim}
What is the difference between `>>=` and `>>`?
\end{verbatim}
If the verbatim text includes a backtick, use double backticks:
\begin{verbatim}
Here is a literal backtick `` ` ``.
\end{verbatim}
(The spaces after the opening backticks and before the closing backticks
will be ignored.)
The general rule is that a verbatim span starts with a string of
consecutive backticks (optionally followed by a space) and ends with a
string of the same number of backticks (optionally preceded by a space).
Note that backslash-escapes (and other markdown constructs) do not work
in verbatim contexts:
\begin{verbatim}
This is a backslash followed by an asterisk: `\*`.
\end{verbatim}
Attributes can be attached to verbatim text, just as with
\hyperref[delimited-code-blocks]{delimited code blocks}:
\begin{verbatim}
`<$>`{.haskell}
\end{verbatim}
\subsection{Math}
\emph{Pandoc extension}.
Anything between two \texttt{\$} characters will be treated as TeX math.
The opening \texttt{\$} must have a character immediately to its right,
while the closing \texttt{\$} must have a character immediately to its
left. Thus, \texttt{\$20,000 and \$30,000} won't parse as math. If for
some reason you need to enclose text in literal \texttt{\$} characters,
backslash-escape them and they won't be treated as math delimiters.
TeX math will be printed in all output formats. How it is rendered
depends on the output format:
\begin{description}
\item[Markdown, LaTeX, Org-Mode, ConTeXt]
It will appear verbatim between \texttt{\$} characters.
\item[reStructuredText]
It will be rendered using an interpreted text role \texttt{:math:}, as
described
\href{http://www.american.edu/econ/itex2mml/mathhack.rst}{here}.
\item[AsciiDoc]
It will be rendered as \texttt{latexmath:{[}...{]}}.
\item[Texinfo]
It will be rendered inside a \texttt{@math} command.
\item[groff man]
It will be rendered verbatim without \texttt{\$}'s.
\item[MediaWiki]
It will be rendered inside \texttt{\textless{}math\textgreater{}} tags.
\item[Textile]
It will be rendered inside
\texttt{\textless{}span class="math"\textgreater{}} tags.
\item[RTF, OpenDocument, ODT]
It will be rendered, if possible, using unicode characters, and will
otherwise appear verbatim.
\item[Docbook]
If the \texttt{-{}-mathml} flag is used, it will be rendered using
mathml in an \texttt{inlineequation} or \texttt{informalequation} tag.
Otherwise it will be rendered, if possible, using unicode characters.
\item[Docx]
It will be rendered using OMML math markup.
\item[HTML, Slidy, DZSlides, S5, EPUB]
The way math is rendered in HTML will depend on the command-line options
selected:
\begin{enumerate}[1.]
\item
The default is to render TeX math as far as possible using unicode
characters, as with RTF, DocBook, and OpenDocument output. Formulas
are put inside a \texttt{span} with \texttt{class="math"}, so that
they may be styled differently from the surrounding text if needed.
\item
If the \texttt{-{}-latexmathml} option is used, TeX math will be
displayed between \$ or \$\$ characters and put in
\texttt{\textless{}span\textgreater{}} tags with class \texttt{LaTeX}.
The \href{http://math.etsu.edu/LaTeXMathML/}{LaTeXMathML} script will
be used to render it as formulas. (This trick does not work in all
browsers, but it works in Firefox. In browsers that do not support
LaTeXMathML, TeX math will appear verbatim between \$ characters.)
\item
If the \texttt{-{}-jsmath} option is used, TeX math will be put inside
\texttt{\textless{}span\textgreater{}} tags (for inline math) or
\texttt{\textless{}div\textgreater{}} tags (for display math) with
class \texttt{math}. The
\href{http://www.math.union.edu/~dpvc/jsmath/}{jsMath} script will be
used to render it.
\item
If the \texttt{-{}-mimetex} option is used, the
\href{http://www.forkosh.com/mimetex.html}{mimeTeX} CGI script will be
called to generate images for each TeX formula. This should work in
all browsers. The \texttt{-{}-mimetex} option takes an optional URL as
argument. If no URL is specified, it will be assumed that the mimeTeX
CGI script is at \texttt{/cgi-bin/mimetex.cgi}.
\item
If the \texttt{-{}-gladtex} option is used, TeX formulas will be
enclosed in \texttt{\textless{}eq\textgreater{}} tags in the HTML
output. The resulting \texttt{htex} file may then be processed by
\href{http://www.math.uio.no/~martingu/gladtex/index.html}{gladTeX},
which will produce image files for each formula and an \texttt{html}
file with links to these images. So, the procedure is:
\begin{verbatim}
pandoc -s --gladtex myfile.txt -o myfile.htex
gladtex -d myfile-images myfile.htex
# produces myfile.html and images in myfile-images
\end{verbatim}
\item
If the \texttt{-{}-webtex} option is used, TeX formulas will be
converted to \texttt{\textless{}img\textgreater{}} tags that link to
an external script that converts formulas to images. The formula will
be URL-encoded and concatenated with the URL provided. If no URL is
specified, the Google Chart API will be used
(\texttt{http://chart.apis.google.com/chart?cht=tx\&chl=}).
\end{enumerate}
\end{description}
\subsection{Raw HTML}
Markdown allows you to insert raw HTML (or DocBook) anywhere in a
document (except verbatim contexts, where \texttt{\textless{}},
\texttt{\textgreater{}}, and \texttt{\&} are interpreted literally).
The raw HTML is passed through unchanged in HTML, S5, Slidy, DZSlides,
EPUB, Markdown, and Textile output, and suppressed in other formats.
\emph{Pandoc extension}.
Standard markdown allows you to include HTML ``blocks'': blocks of HTML
between balanced tags that are separated from the surrounding text with
blank lines, and start and end at the left margin. Within these blocks,
everything is interpreted as HTML, not markdown; so (for example),
\texttt{*} does not signify emphasis.
Pandoc behaves this way when \texttt{-{}-strict} is specified; but by
default, pandoc interprets material between HTML block tags as markdown.
Thus, for example, Pandoc will turn
\begin{verbatim}
| *one* | [a link](http://google.com) |
| one | a link |