From e5921240cf2428c1ae3396c3c56de7778cfee634 Mon Sep 17 00:00:00 2001 From: Ashe Connor Date: Mon, 6 Nov 2017 06:00:49 +1100 Subject: 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 --- spec.txt | 4 ++-- 1 file 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 -- cgit v1.2.3