-
Notifications
You must be signed in to change notification settings - Fork 140
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
Wrong interpretation escaping (non-markdown) characters inside link. #54
Comments
escaping of special characters is only needed in places where the meaning is ambigous. inside of an URL there is no need to escape markdown characters as it is clear that there can not be the beginning of the list inside of that link. |
I still may consider adding support for this when there are no side effects. |
Looks like most of the parsers remove the backslash... http://johnmacfarlane.net/babelmark2/?normalize=1&text=nice+[video]%28http%3A%2F%2Fwww.youtube.com%2Fvideo\-one%29.+Nice\-video+star+\* |
sorry for this part. |
Yeah, no problem, its all clear already. |
Hi. My text editor make markdown for escaping (non-markdown) characters with two backslashes. I know rule for escaping characters is one backslash but still cebe/markdown work OK with two backslash rule.
Example:
nice [video](http://www.youtube.com/video\\-one). Nice\\-video star \\*
after proceeding with cebe/markdown I get:
nice video. Nice-video star *
But problem is inside link:
http://www.youtube.com/video\-one
Why don't remove " \ " from link?The text was updated successfully, but these errors were encountered: