4

The following link:

link

does not work. The code is:

[link][2]


[2]: http://www.google.com/imgres?hl=en&sa=X&rlz=1C1CHKZ_enKR434KR434&biw=1711&bih=968&tbm=isch&tbnid=f6FEHFZbuQzV6M:&imgrefurl=http://blogs.webex.com/webex_interactions/2010/08/bear_grylls_everest.html&docid=Z_wVDhYxhn3jvM&imgurl=http://blogs.webex.com/.a/6a00d83451c08e69e20133f2de805b970b-pi&w=4103&h=494&ei=B-pfUZOcOeioiAeMiYCADA&zoom=1&ved=1t:3588,r:5,s:0,i:96&iact=rc&dur=1647&page=1&tbnh=41&tbnw=310&start=0&ndsp=31&tx=87&ty=10

It works fine in the preview, and I have already tried encodeURI()ing it. Here's an example of where this link breaks: Why does the sky look black in pictures taken from the summit of everest?

3

1 Answer 1

5

Fixed in the next build. The problem here wasn't so much the link-within-the-link (it just made the problem very visible), but the underscore. Markdown escapes certain characters (like the underscore) in links, to prevent them from being treated as formatting characters. The two Markdown implementations use different escape characters for this: the client-side version uses a tilde, the server-side version uses U+001A. The former is a legal character for being auto-linked, but the latter was not. That's why the behaviors were differing.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .