Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve CommonMark compatibility #11

Merged
merged 13 commits into from
Jul 1, 2020
Merged

Improve CommonMark compatibility #11

merged 13 commits into from
Jul 1, 2020

Conversation

karlb
Copy link
Contributor

@karlb karlb commented Sep 29, 2019

I checked smu's output with https://github.com/michelf/mdtest and fixed some deviations from the expected output.

This includes #10

Example:

[URL wrapped in angle brackets](</url/>).
According to https://spec.commonmark.org/0.29/#code-spans :

> If the resulting string both begins and ends with a space character,
but does not consist entirely of space characters, a single space
character is removed from the front and back. This allows you to include
code that begins or ends with backtick characters, which must be
separated by whitespace from the opening or closing backtick strings.
I could not find this in the markdown spec, but
https://github.com/michelf/mdtest/blob/master/Markdown.mdtest/Literal%20quotes%20in%20titles.text
includes it in the test suite and I actually prefer the implementation
after this change.
```
- - -

foo
```
did not work because the empty line was swallowed when parsing the
ruler.
Otherwise
```
- foo
- bar
+ baz
```
will become a nested list
* nesting did not work
* ">" without following space was not recognized as blockquote

Quoting https://spec.commonmark.org/0.29/#example-5:
> Normally the > that begins a block quote may be followed optionally by
a space, which is not considered part of the content.
@Gottox Gottox merged commit 2a8d5b1 into Gottox:master Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants