Workaround is to URL-encode the parenthesis (%29) or use the remarkup style

[Back to the Future](https://en.wikipedia.org/wiki/Starship_Troopers_(film%29)
[[ https://en.wikipedia.org/wiki/Starship_Troopers_(film) | Jurassic Park ]]

Results in:
[Back to the Future](https://en.wikipedia.org/wiki/Starship_Troopers_(film%29)
Jurassic Park

The intent isn't unambiguous in the general case, consider: Blah blah (see also [x](y)).

The CommonMark spec describes balancing rules:

GitHub seems to implement something similar. For example, it does not render See the page at [Open Parenthesis](wiki/open_parenthesis() for more details as a link.

Organically, I think this rule is actually "Wikipedia is the only site on the internet which uses parentheses in URLs, and parsers should implement behavior which gets most Wikipedia pages right."

I think we have to balance the parentheses as we parse the string to get the right result? Maybe I can fake it with very clever regular expressions.

GitHub behaves oddly on these inputs:

[x](x()   Not a link.
[x](x(y)  Not a link
[x](x( )  Link to `x(`? Huh?

D19111 doesn't fix this in the general case, but should produce the desired behavior for most inputs such that the input is in the form [x](y) and y is the URI of a Wikipedia article.

Notably, it does not make [x](y((()))) behave in a way that is similar to GitHub or CommonMark.