aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAshe Connor <kivikakk@github.com>2017-11-06 06:00:49 +1100
committerJohn MacFarlane <jgm@berkeley.edu>2017-11-05 14:00:49 -0500
commite5921240cf2428c1ae3396c3c56de7778cfee634 (patch)
tree8fb9f291c612718428340ea4269abbac756cfec0
parent5a16a9139e72887e844cc53ab8c8bd73373328de (diff)
Info string is trimmed of all whitespace (#505)
* Info string is trimmed of all whitespace As noted in https://github.com/github/cmark/issues/60, the info string is not only trimmed of "spaces" (U+0020) but indeed all whitespace. Update the spec to reflect this. * "spaces" => "spaces or tabs" after thematic breaks
-rw-r--r--spec.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/spec.txt b/spec.txt
index a3f7ebf..d07e514 100644
--- a/spec.txt
+++ b/spec.txt
@@ -527,7 +527,7 @@ Markdown document.
A line consisting of 0-3 spaces of indentation, followed by a sequence
of three or more matching `-`, `_`, or `*` characters, each followed
-optionally by any number of spaces, forms a
+optionally by any number of spaces or tabs, forms a
[thematic break](@).
```````````````````````````````` example
@@ -1584,7 +1584,7 @@ begins with a code fence, indented no more than three spaces.
The line with the opening code fence may optionally contain some text
following the code fence; this is trimmed of leading and trailing
-spaces and called the [info string](@).
+whitespace and called the [info string](@).
The [info string] may not contain any backtick
characters. (The reason for this restriction is that otherwise
some inline code would be incorrectly interpreted as the