diff options
| author | John MacFarlane <jgm@berkeley.edu> | 2015-07-10 09:21:37 -0700 |
|---|---|---|
| committer | John MacFarlane <jgm@berkeley.edu> | 2015-07-10 09:21:37 -0700 |
| commit | 114a3986053ae53b23dc4ebcbd15fc4387d278e0 (patch) | |
| tree | f5d30e646076a96348fb2048138a8435eee62d98 /spec.txt | |
| parent | 3becc272597f8054c41678265575280e866eeb06 (diff) | |
Rewrapped two lines so `+` does not begin a line.
Closes #347.
Thanks for pointing this out.
We might want to revisit the decision to allow a list to
interrupt a paragraph. It's a minority opinion:
http://johnmacfarlane.net/babelmark2/?normalize=1&text=Text+text%0A-+one%0A-+two%0A
And, in fact, in our initial discussions I was pretty strongly
opposed to it. Others felt strongly that people would naturally
create lists this way, and that it should be allowed. Some of
this is sumarized here:
http://talk.commonmark.org/t/requiring-a-blank-line-between-a-paragraph-and-list/657
The thread is a bit noisy but the point that sways me most is here:
http://talk.commonmark.org/t/requiring-a-blank-line-between-a-paragraph-and-list/657/13?u=jgm
Diffstat (limited to 'spec.txt')
| -rw-r--r-- | spec.txt | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -4400,8 +4400,8 @@ than HTML need not be HTML-entity aware. HTML renderers may either escape unicode characters as entities or leave them as they are. (However, `"`, `&`, `<`, and `>` must always be rendered as entities.) -[Named entities](@name-entities) consist of `&` -+ any of the valid HTML5 entity names + `;`. The +[Named entities](@name-entities) consist of `&` + any +of the valid HTML5 entity names + `;`. The [following document](https://html.spec.whatwg.org/multipage/entities.json) is used as an authoritative source of the valid entity names and their corresponding codepoints. @@ -4430,8 +4430,8 @@ the codepoint `U+0000` will also be replaced by `U+FFFD`. . [Hexadecimal entities](@hexadecimal-entities) -consist of `&#` + either `X` or `x` + a string of 1-8 hexadecimal digits -+ `;`. They will also be parsed and turned into the corresponding +consist of `&#` + either `X` or `x` + a string of 1-8 hexadecimal +digits + `;`. They will also be parsed and turned into the corresponding unicode codepoints in the AST. . |