asterisk1
This tests *two* *emphasized* texts chunks next to another, with blank in between.
Rendered HTML
<p>This tests <em>two</em> <em>emphasized</em> texts chunks next to another, with blank in between.
</p>
asterisk1
double-asterisk0
double-asterisk1
asterisk3
asterisk4
underscore1
backslash-escape0
backslash-escape1
backslash-escape2
backticks0
backticks1
backticks2
double-backticks0
double-backticks1
double-backticks2
underscore-in-backticks0
hard-break0
hard-break1
hard-break2
sgmlproc <your-file.md>
where <your-file.md> is replaced by the actual file
used for storing.
This tests *two* *emphasized* texts chunks next to another, with blank in between.
<p>This tests <em>two</em> <em>emphasized</em> texts chunks next to another, with blank in between.
</p>
This demonstrates using **double asterisks** to strongly emphasize text.
<p>This demonstrates using <strong>double asterisks</strong> to strongly emphasize text.
</p>
This demontrates **two****consecutive** strongly emphasised text portions.
<p>This demontrates <strong>two</strong><strong>consecutive</strong> strongly emphasised text portions.
</p>
This goes to show that an * asterisk* without directly following non-blank text
isn't interpreted as emphasis syntax,
and neither is an *asterisk * without directly *preceding* non-blank text.
Note that pandoc behaves somewhat different: it will put the 2nd "asterisk"
(and "preceding") in em tags.
<p>This goes to show that an * asterisk* without directly following non-blank text
isn't interpreted as emphasis syntax,
and neither is an <em>asterisk * without directly *preceding</em> non-blank text.
Note that pandoc behaves somewhat different: it will put the 2nd "asterisk"
(and "preceding") in em tags.
</p>
This is put in "em" tags: *text*subsequent non-space,
and so is this: preceding non-space*text*
and this: nonspace*text*nonspace
(as opposed to underscore1.txt)
<p>This is put in "em" tags: <em>text</em>subsequent non-space,
and so is this: preceding non-space<em>text</em>
and this: nonspace<em>text</em>nonspace
(as opposed to underscore1.txt)
</p>
This isn't put in "em" tags: _text_subsequent non-space,
and neither is this: preceding non-space_text_
or this: nonspace_text_nonspace
(as opposed to asterisk4.txt)
<p>This isn't put in "em" tags: _text_subsequent non-space,
and neither is this: preceding non-space_text_
or this: nonspace_text_nonspace
(as opposed to asterisk4.txt)
</p>
This backslash escapes `*`: \*.
And this one: \_ escapes `_`.
<p>This backslash escapes <code>*</code>: *.
And this one: _ escapes <code>_</code>.
</p>
A backslash can escape backticks like this: \`this isn't code\`.
<p>A backslash can escape backticks like this: `this isn't code`.
</p>
Backslashes have no special interpretation within backticks.
as `shown \\ here`.
`Backslashes preceeding a backtick\` in backticked verbatim text` are
no exception to this (so the backticked ends after the backslash).
<p>Backslashes have no special interpretation within backticks.
as <code>shown \\ here</code>.
<code>Backslashes preceeding a backtick\</code> in backticked verbatim text` are
no exception to this (so the backticked ends after the backslash).
</p>
This test `span-level code blocks`.
<p>This test <code>span-level code blocks</code>.
</p>
Within `backticks`, reserved HTML characters (such as `<`, `>`, or `&`)
get replaced by character entities.
<p>Within <code>backticks</code>, reserved HTML characters (such as <code><</code>, <code>></code>, or <code>&</code>)
get replaced by character entities.
</p>
This is how you write HTML character entities verbatim: `&`, `<`, `>`
<p>This is how you write HTML character entities verbatim: <code>&amp;</code>, <code>&lt;</code>, <code>&gt;</code>
</p>
Within `backticked code, a sequence of two consecutive backticks `` are
reproduced as two backticks`, so don't expand to a single backtick,
like, say, in SQL.
<p>Within <code>backticked code, a sequence of two consecutive backticks `` are
reproduced as two backticks</code>, so don't expand to a single backtick,
like, say, in SQL.
</p>
Text with `backticked code with two non-consecutive backticks ` ` are `
handled as two consecutive spans of inline code.
<p>Text with <code>backticked code with two non-consecutive backticks</code> <code>are</code>
handled as two consecutive spans of inline code.
</p>
To place a verbatim backtick within backticks, start and
end `` the inline code span with two backticks and a blank; then use ` ``
<p>To place a verbatim backtick within backticks, start and
end <code>the inline code span with two backticks and a blank; then use `</code>
</p>
Underscore chars within backticks (`like _these_ ones`) aren't treated
as markdown syntax
<p>Underscore chars within backticks (<code>like _these_ ones</code>) aren't treated
as markdown syntax
</p>
This line is ended with (invisible) double space after the comma,
which will make markdown put a `<br>` tag before this next line.
<p>This line is ended with (invisible) double space after the comma,<br>
which will make markdown put a <code><br></code> tag before this next line.
</p>
- Hard breaks are also inserted
when list item lines end in
double spaces
<ul><li><p>Hard breaks are also inserted<br>
when list item lines end in<br>
double spaces
</p></li></ul>
Hard breaks are also inserted on the last (or only) line ending in double-space
<p>Hard breaks are also inserted on the last (or only) line ending in double-space<br>
</p>