Possible Duplicate:
Autogenerated links truncate a final closing bracket

Clicking on the following will go to the wrong location in the page (some escaped and some not): http://developer.android.com/reference/android/content/Intent.html#addCategory(java.lang.String) - Escaped http://developer.android.com/reference/android/content/Intent.html#addCategory(java.lang.String) - Not escaped

  • 3
    Using proper markdown might be an answer to this. – Time Traveling Bobby Apr 4 '12 at 10:56
  • 1
    To me, both the links take to http://developer.android.com/reference/android/content/Intent.html#addCategory(java.lang.String. – kiamlaluno Apr 4 '12 at 11:01
  • @kiamlaluno and it's the wrong one - without the closing right parenthesis. – AlikElzin-kilaka Apr 4 '12 at 12:23
  • @TimStone you are right, but it's not related to auto-generated links. I didn't find it when I searched for similar posts. – AlikElzin-kilaka Apr 4 '12 at 12:27
  • Anyhow, it seems a bug. How do we escalate it to a bug. – AlikElzin-kilaka Apr 4 '12 at 12:27

Interesting. In your question as it currently stands, both links go the the same URL (your escape failed).

However, in the editing view the the first link as shown in the preview is properly escaped.

So, the issue here seems to be "why is the preview parsing links differently from the actual post?". More specifically, using a backslash to escape the trailing parenthesis works in the preview (!) but not in the actual post.

That aside, you can avoid having to manually escape the chars if use the appropriate markdown for linking. See Would it be possible to fix links containing parentheses in comments?

Also note the Bare URLs section in the editing help page which states that you should enclose the bare URLs with angle brackets if they contain unusual chars, or use the proper markdown syntax for linking.

Example: Raw link enclosed in angle brackets - http://developer.android.com/reference/android/content/Intent.html#addCategory(java.lang.String)

  • 2
    To answer your bolded question, see this comment of mine. – Tim Stone Apr 4 '12 at 12:24
  • @TimStone ah... thanks. Was looking for a post on that and was close to posting a Q of my own. – Shawn Chin Apr 4 '12 at 12:27
  • This is correct, so how can we escalate it to a bug? – AlikElzin-kilaka Apr 4 '12 at 12:29
  • @kilaka You've already done so (posting on MSO and tagging it with [bug]). However, do note that what you've posted has already been discussed several times in the past (see links in other comments). – Shawn Chin Apr 4 '12 at 12:35

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