Then you won't mind explaining why Wikipedia's own pages include ones
with URLs like this:
http://en.wikipedia.org/wiki/The_Lost_(book)
(Paste that line into Firefox's address bar if you don't believe me.)
In
http://en.wikipedia.org/wiki/Uniform_resource_locator
Wikipedia says this about which characters are reserved:
<QUOTE>
Reserved
Have to be encoded sometimes
! * ' ( ) ; : @ & = + $ , / ? % # [ ]
</QUOTE>
What's fun is that clicking on your URL works in both Dialog and
MesNews, but MesNews throws away "(book)", and FF or somebody throws
away the trailing underscore.
Maybe all that is needed is to avoid any balanced parentheses.
No, it's not that simple. For example,
http://en.wikipedia.org/wiki/The_Lost_(bo
gets me to the page, but if I copy and paste from the address bar, this
is what I get:
http://en.wikipedia.org/wiki/The_Lost_(bo
even though I see a parenthesis in the address bar even after I get to
the site.
Someone is looking over my shoulder and fixing the errors as I go along.
And that made me copy the good URL (with parens) from the address bar.
Look at this:
http://en.wikipedia.org/wiki/The_Lost_(book)
Someone (apparently not you) seems to think that parens are illegal.
And this seems to be what Dialog sends to FF from mechanic's post - or
maybe FF converts it before trying to connect:
http://neosmart.net/EasyBCD/)
This much is clear: the neosmart link includes the ')' when Dialog sends
it, but not when MesNews sends it (I can see that by the way the links
are highlighted in those two programs), thus the 404 from Dialog.
I'm guessing that Wikipedia has some code to parse the shortened links
that I tried.
And it still looks like parentheses aren't legal. I don't know where
they get replaced by the hex encoding, but I bet it's FF.
But again, it's not all that clear. I tried IE; it gets to your link,
and it doesn't show the hex codes when I copy and paste from the address
bar. My guess: it also sends the encoded parens, but unlike FF, it keeps
it a secret from me.
While I was at it, I tried Chrome and Safari. They act like IE.
What is really needed is a URL where the parentheses are in the
higher-level part of the address, between the '//' and the first '/',
since AIUI the remaining parts of the URL are parsed by the site, not by
the DNS. This would be consistent with one link producing a 404 and the
other working fine.
Since I'm no expert[1], I'll now quit speculating on this issue.
[1] This claim provided courtesy of the Department of Extreme
Understatement