In brief: There's a problem with the <c>Card Name</c> parser and special characters - most notably slashes and quotes. I think it wouldn't be difficult to correct; wrapping the output in urlencode() should do it. I've also made a change to monobook.js (see link in above talk page) but that wouldn't be necessary if the PHP translated slash into %2F (which urlencode would do).
I have some (small) experience with writing MediaWiki extensions, and would be happy to do this / assist with this, if someone (Hannes??) could provide the current PHP code. http://wiki.mtgsalvation.com/article/Special:Version isn't helpful in pinpointing it, but I assume a look at LocalSettings.php would give the file name (if it's been done in the standard way, there'd be a require_once near the bottom that references something from extensions/somewhere).
http://wiki.mtgsalvation.com/article/Help_talk:Card_tags#Formatting_oddities.2Fissues
In brief: There's a problem with the <c>Card Name</c> parser and special characters - most notably slashes and quotes. I think it wouldn't be difficult to correct; wrapping the output in urlencode() should do it. I've also made a change to monobook.js (see link in above talk page) but that wouldn't be necessary if the PHP translated slash into %2F (which urlencode would do).
See http://wiki.mtgsalvation.com/index.php?title=Unhinged&diff=64231&oldid=62297 for some examples of before and after. The "before" entries are much cleaner in the wiki source than the "after" ones (especially the Life/Death example), but don't work. What I'm proposing would make them work.
I have some (small) experience with writing MediaWiki extensions, and would be happy to do this / assist with this, if someone (Hannes??) could provide the current PHP code. http://wiki.mtgsalvation.com/article/Special:Version isn't helpful in pinpointing it, but I assume a look at LocalSettings.php would give the file name (if it's been done in the standard way, there'd be a require_once near the bottom that references something from extensions/somewhere).
Hope that's enough information to pinpoint it!
We'll definitely look into the issue.