diff options
| -rw-r--r-- | test/spec.txt | 53 | 
1 files changed, 27 insertions, 26 deletions
diff --git a/test/spec.txt b/test/spec.txt index e2b6834..7d97e1e 100644 --- a/test/spec.txt +++ b/test/spec.txt @@ -1985,7 +1985,7 @@ by their start and end conditions.  The block begins with a line that  meets a [start condition](@) (after up to three spaces  optional indentation).  It ends with the first subsequent line that  meets a matching [end condition](@), or the last line of -the document or other [container block](@), if no line is encountered that meets the +the document or other [container block]), if no line is encountered that meets the  [end condition].  If the first line meets both the [start condition]  and the [end condition], the block will contain just that line. @@ -2015,7 +2015,8 @@ followed by one of the strings (case-insensitive) `address`,  `article`, `aside`, `base`, `basefont`, `blockquote`, `body`,  `caption`, `center`, `col`, `colgroup`, `dd`, `details`, `dialog`,  `dir`, `div`, `dl`, `dt`, `fieldset`, `figcaption`, `figure`, -`footer`, `form`, `frame`, `frameset`, `h1`, `head`, `header`, `hr`, +`footer`, `form`, `frame`, `frameset`, +`h1`, `h2`, `h3`, `h4`, `h5`, `h6`, `head`, `header`, `hr`,  `html`, `iframe`, `legend`, `li`, `link`, `main`, `menu`, `menuitem`,  `meta`, `nav`, `noframes`, `ol`, `optgroup`, `option`, `p`, `param`,  `section`, `source`, `summary`, `table`, `tbody`, `td`, @@ -4730,8 +4731,7 @@ takes four spaces (a common case), but diverge in other cases.  A [list](@) is a sequence of one or more  list items [of the same type].  The list items -may be separated by single [blank lines], but two -blank lines end all containing lists. +may be separated by any number of blank lines.  Two list items are [of the same type](@)  if they begin with a [list marker] of the same type. @@ -4809,10 +4809,11 @@ Foo  `Markdown.pl` does not allow this, through fear of triggering a list  via a numeral in a hard-wrapped line: -```````````````````````````````` markdown +``` markdown  The number of windows in my house is  14.  The number of doors is 6. -```````````````````````````````` +``` +  Oddly, though, `Markdown.pl` *does* allow a blockquote to  interrupt a paragraph, even though the same considerations might  apply. @@ -4821,10 +4822,12 @@ In CommonMark, we do allow lists to interrupt paragraphs, for  two reasons.  First, it is natural and not uncommon for people  to start lists without blank lines: -    I need to buy -    - new shoes -    - a coat -    - a plane ticket +``` markdown +I need to buy +- new shoes +- a coat +- a plane ticket +```  Second, we are attracted to a @@ -4836,20 +4839,24 @@ Second, we are attracted to a  (Indeed, the spec for [list items] and [block quotes] presupposes  this principle.) This principle implies that if -      * I need to buy -        - new shoes -        - a coat -        - a plane ticket +``` markdown +  * I need to buy +    - new shoes +    - a coat +    - a plane ticket +```  is a list item containing a paragraph followed by a nested sublist,  as all Markdown implementations agree it is (though the paragraph  may be rendered without `<p>` tags, since the list is "tight"),  then -    I need to buy -    - new shoes -    - a coat -    - a plane ticket +``` markdown +I need to buy +- new shoes +- a coat +- a plane ticket +```  by itself should be a paragraph followed by a nested sublist. @@ -6558,7 +6565,7 @@ Note that in the preceding case, the interpretation  is precluded by the condition that a delimiter that -can both open and close (like the `*` after `foo` +can both open and close (like the `*` after `foo`)  cannot form emphasis if the sum of the lengths of  the delimiter runs containing the opening and  closing delimiters is a multiple of 3. @@ -6590,12 +6597,6 @@ omitted:  ```````````````````````````````` -```````````````````````````````` example -*foo**bar*** -. -<p><em>foo<strong>bar</strong></em></p> -```````````````````````````````` -  Indefinite levels of nesting are possible:  ```````````````````````````````` example @@ -9045,7 +9046,7 @@ blocks.  But we cannot close unmatched blocks yet, because we may have a  [lazy continuation line].  2.  Next, after consuming the continuation markers for existing -blocks, we look for new block starts (e.g. `>` for a block quote. +blocks, we look for new block starts (e.g. `>` for a block quote).  If we encounter a new block start, we close any blocks unmatched  in step 1 before creating the new block as a child of the last  matched block.  | 
