7

In this question, several workarounds are shown for inserting links containing parentheses (()). However, they don't work for comments, because you cannot insert the extra line break needed for the

[SomeLinkText][1]
[1]:http://example.com

syntax to work. It just seems like an arbitrary limitation; I know that this prevents one from using Regex to match the URL expressions, but we know what happens when one uses regex. :)

Improve this question
6

The #2 work-around on that page (urlencoding the parens) works in comments. Firefox will do it for you if you copy the URL directly from the address bar.

Note that certain sites actually work better if you just strip the parenthetical portions out before posting anyway...

Improve this answer
2
5

I'm assuming your regex hint is supposed to suggest that correctly nested parentheses could be handled. It's certainly true that parens are legal characters in URLs. But no specification says that parentheses in URLs have to be correctly opened and closed. So this:

http://example.com/somewhere)XYZ/42

is a perfectly valid URL. But are you seriously suggesting that this comment:

For more information, see [this page](http://example.com/somewhere)XYZ/42).

should work?

Edit: Okay, the usual case (see here for examples) will be supported in comments after the next build.

Improve this answer
1
  • 2
    It's impossible with the current system to get them all to work, but nevertheless I think it would be beneficial to support URLs with matching parens, which are the vast majority of them. – Thomas Bonini Sep 4 '10 at 19:08

You must log in to answer this question.

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