Clarify docs on block quotes.
The space after `>` is optional. Closes #2346.
This commit is contained in:
parent
e3b791eda7
commit
3e8590d8a4
1 changed files with 9 additions and 2 deletions
11
README
11
README
|
@ -1295,8 +1295,8 @@ Block quotations
|
|||
Markdown uses email conventions for quoting blocks of text.
|
||||
A block quotation is one or more paragraphs or other block elements
|
||||
(such as lists or headers), with each line preceded by a `>` character
|
||||
and a space. (The `>` need not start at the left margin, but it should
|
||||
not be indented more than three spaces.)
|
||||
and an optional space. (The `>` need not start at the left margin, but
|
||||
it should not be indented more than three spaces.)
|
||||
|
||||
> This is a block quote. This
|
||||
> paragraph has two lines.
|
||||
|
@ -1320,6 +1320,13 @@ other block quotes. That is, block quotes can be nested:
|
|||
>
|
||||
> > A block quote within a block quote.
|
||||
|
||||
If the `>` character is followed by an optional space, that space
|
||||
will be considered part of the block quote marker and not part of
|
||||
the indentation of the contents. Thus, to put an indented code
|
||||
block in a block quote, you need five spaces after the `>`:
|
||||
|
||||
> code
|
||||
|
||||
#### Extension: `blank_before_blockquote` ####
|
||||
|
||||
Standard markdown syntax does not require a blank line before a block
|
||||
|
|
Loading…
Add table
Reference in a new issue