diff options
author | John MacFarlane <jgm@berkeley.edu> | 2015-06-13 16:33:36 -0700 |
---|---|---|
committer | John MacFarlane <jgm@berkeley.edu> | 2015-06-13 16:33:36 -0700 |
commit | 645ea4e735a85c7554e0247015ed8f61d4888a86 (patch) | |
tree | efe28f1764a8596b036d5db7df14596a7450a2c4 | |
parent | 68ab4cc72e709c86c976063945d3a37f0fbdb330 (diff) |
Updated spec.txt.
-rw-r--r-- | test/spec.txt | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/test/spec.txt b/test/spec.txt index ffaa8a2..ac2ce2a 100644 --- a/test/spec.txt +++ b/test/spec.txt @@ -1953,6 +1953,17 @@ The link destination may not be omitted: <p>[foo]</p> . +Both title and destination can contain backslash escapes +and literal backslashes: + +. +[foo]: /url\bar\*baz "foo\"bar\baz" + +[foo] +. +<p><a href="/url%5Cbar*baz" title="foo"bar\baz">foo</a></p> +. + A link can come before its corresponding definition: . @@ -5978,6 +5989,15 @@ in Markdown: <p><a href="foo):">link</a></p> . +Note that a backslash before a non-escapable character is +just a backslash: + +. +[link](foo\bar) +. +<p><a href="foo%5Cbar">link</a></p> +. + URL-escaping should be left alone inside the destination, as all URL-escaped characters are also valid URL characters. HTML entities in the destination will be parsed into the corresponding unicode |