From 136a0df633a4ff3e68f815b57d2249c48aea1a86 Mon Sep 17 00:00:00 2001 From: John MacFarlane Date: Fri, 24 Oct 2014 11:42:53 -0700 Subject: More tweaks on emph/strong spec and tests. --- spec.txt | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) (limited to 'spec.txt') diff --git a/spec.txt b/spec.txt index e416bc6..41be5fb 100644 --- a/spec.txt +++ b/spec.txt @@ -4117,10 +4117,13 @@ the following principles resolve ambiguity: 12. An interpretation `...` is always preferred to `..`. -13. When two potential emphasis or strong emphasis spans overlap, - the first takes precedence. Thus, for example, `*foo _bar* baz_` +13. Earlier closings are preferred to later closings. Thus, + when two potential emphasis or strong emphasis spans overlap, + the first takes precedence: for example, `*foo _bar* baz_` is parsed as `foo _bar baz_` rather than - `*foo bar* baz`. + `*foo bar* baz`. For the same reason, + `**foo*bar**` is parsed as `foobar*` + rather than `foo*bar`. 14. Inline code spans, links, images, and HTML tags group more tightly than emphasis. So, when there is a choice between an interpretation @@ -4707,15 +4710,6 @@ We retain symmetry in these cases:

foo bar

. -Note that this is not a case of strong emphasis, -since the interior `*` closes regular emphasis: - -. -**foo bar* baz** -. -

foo bar baz*

-. - More cases with mismatched delimiters: . @@ -4748,7 +4742,7 @@ More cases with mismatched delimiters:

***foo bar

. -The following case illustrates rule 13: +The following cases illustrate rule 13: . *foo _bar* baz_ @@ -4756,6 +4750,12 @@ The following case illustrates rule 13:

foo _bar baz_

. +. +**foo bar* baz** +. +

foo bar baz*

+. + The following cases illustrate rule 14: . -- cgit v1.2.3