You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
http://www.mysite.com/myfolder/file/ to read the report. Also
see: at http://www.mysite.com/test?q=xxyy to test.
This site shows the output from various processors, showing others also
exhibit this problem. http://babelmark.bobtfish.net/?markdown=%5Bhttp%3A%2F%2Fwww.mysite.com%2Fmy _folder%2Ffile%2F%5D%28http%3A%2F%2Fwww.mysite.com%2Fmy_folder%2Ffile%2F+%2
2My+File%22%29+to+read+the+report.+Also+see%3A+at+%5Bhttp%3A%2F%2Fwww.mysit
e.com%2Ftest%3Fq%3Dxx_yy%5D%28http%3A%2F%2Fwww.mysite.com%2Ftest%3Fg%3Dxx_y
y+%22A+test%22%29+to+test.&normalize=on&src=1&dest=2
The canonical Markdown.pl versions 1.0.1 / 1.0.2b8 also appear to exhibit this problem. As such, although this
issue is excepted, I've made it medium priority, pending a little more background reading / discussion on the
Markdown mailing list to establish what the correct behaviour should be across implementations.
From alex.coles on October 28, 2008 01:21:14
Underscores in links can generate undeeded em tags
As an example:
[ http://www.mysite.com/my_folder/file/](http://www.mysite.com/my_folder/fil e/) to read the report. Also see: at
http://www.mysite.com/test?q=xx_yy to test.
Generates
http://www.mysite.com/myfolder/file/ to read the report. Also see: at http://www.mysite.com/test?q=xxyy to test.
This site shows the output from various processors, showing others also
exhibit this problem. http://babelmark.bobtfish.net/?markdown=%5Bhttp%3A%2F%2Fwww.mysite.com%2Fmy _folder%2Ffile%2F%5D%28http%3A%2F%2Fwww.mysite.com%2Fmy_folder%2Ffile%2F+%2
2My+File%22%29+to+read+the+report.+Also+see%3A+at+%5Bhttp%3A%2F%2Fwww.mysit
e.com%2Ftest%3Fq%3Dxx_yy%5D%28http%3A%2F%2Fwww.mysite.com%2Ftest%3Fg%3Dxx_y
y+%22A+test%22%29+to+test.&normalize=on&src=1&dest=2
Mark Smithson
[email protected]
Original issue: http://code.google.com/p/markdownj/issues/detail?id=3
The text was updated successfully, but these errors were encountered: