-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
Left-flanking / right-flanking (again?) #310
Comments
+++ Xavier Mendez [Mar 10 15 13:59 ]:
My original instinct in adjusting the spec was just to add: For the sake of simplicity, would it be better to say the
|
Yeah. |
See commonmark/commonmark.js#12 for a related issue. |
This change mirrors commonmark/commonmark.js@0b40889 Additional information: - commonmark/commonmark-spec#310 - commonmark/commonmark-spec#317 - commonmark/commonmark.js#12
This change mirrors commonmark/commonmark.js@0b40889 Additional information: - commonmark/commonmark-spec#310 - commonmark/commonmark-spec#317 - commonmark/commonmark.js#12
I'm kinda pissed off. I implemented emphasis according to the spec, and now my parser is rendering
_foo_
as<p>_foo_</p>
. I verified that, according to the rules in 0.17, the two delimiter runs are both right- and left- flanking. So my parser is actually right!So I go checkout 0.18 and I find the definition has changed a bit, it's now even more permissive. So
_foo_
is still<p>_foo_</p>
. I also checked master before submitting this.Then I find in #302 (and in CMark code) that the code treats start of line and end of line as whitespace, and @jgm attempted to correct the spec. However
_foo_
is still having both left- and right- flanking delimiter runs.I suppose this would be fixed by changing:
But those two definitions are getting very messy IMO...
The text was updated successfully, but these errors were encountered: