Skip to content

Commit ed90fbe

Browse files
authored
Block quote marker choice uniformity
Require that the same block quote marker be used to avoid ambiguity in parsing strategy (compatible with the algorithm described [here](commonmark#460 (comment)))
1 parent f1d14f2 commit ed90fbe

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

spec.txt

+5-2
Original file line numberDiff line numberDiff line change
@@ -3194,9 +3194,12 @@ with a following space, or (b) a single character `>` not followed by a space.
31943194
The following rules define [block quotes]:
31953195

31963196
1. **Basic case.** If a string of lines *Ls* constitute a sequence
3197-
of blocks *Bs*, then the result of prepending a [block quote
3197+
of blocks *Bs*, then the result of prepending the same [block quote
31983198
marker] to the beginning of each line in *Ls*
3199-
is a [block quote](#block-quotes) containing *Bs*.
3199+
is a [block quote](#block-quotes) containing *Bs*. If some lines in *Ls*
3200+
are blank lines, then trailing whitespace after a block quote marker
3201+
may be omitted without affecting the interpertation of which block quote
3202+
marker was prepended.
32003203

32013204
2. **Laziness.** If a string of lines *Ls* constitute a [block
32023205
quote](#block-quotes) with contents *Bs*, then the result of deleting

0 commit comments

Comments
 (0)