Skip to content

Commit

Permalink
Info string is trimmed of all whitespace (#505)
Browse files Browse the repository at this point in the history
* Info string is trimmed of all whitespace

As noted in github/cmark-gfm#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
  • Loading branch information
Ashe Connor authored and jgm committed Nov 5, 2017
1 parent 5a16a91 commit e592124
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions spec.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down

0 comments on commit e592124

Please sign in to comment.