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

Wrong interpretation escaping (non-markdown) characters inside link. #54

Closed
despotbg opened this issue Jul 23, 2014 · 5 comments
Closed
Milestone

Comments

@despotbg
Copy link

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?

@despotbg despotbg changed the title Wrong interpretation non-marktdown characters inside link. Wrong interpretation non-markdown characters inside link. Jul 23, 2014
@despotbg despotbg changed the title Wrong interpretation non-markdown characters inside link. Wrong interpretation escaping (non-markdown) characters inside link. Jul 23, 2014
@cebe
Copy link
Owner

cebe commented Jul 23, 2014

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.

@cebe
Copy link
Owner

cebe commented Jul 23, 2014

I still may consider adding support for this when there are no side effects.

@cebe cebe added this to the 1.0.1 milestone Jul 23, 2014
@cebe
Copy link
Owner

cebe commented Jul 23, 2014

@despotbg
Copy link
Author

sorry for this part.
"escaping (non-markdown) characters with two backslashes".
My bad. Actually neo4j add second backslash.

@cebe
Copy link
Owner

cebe commented Jul 29, 2014

Yeah, no problem, its all clear already.

@cebe cebe modified the milestones: 1.0.1, 1.0.2 Oct 25, 2014
@cebe cebe closed this as completed in f0412bb Mar 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants