well unsafe characters should be encoded in the url
i guess every browser WILL encode them when you go browse the address
easiest example is \" \" no, urls with spaces are not valid still if you type them into firefox he will go to the url, replacing \" \" with the encoded \"%20\"
still i can\'t go and say \"http://whateveraddress.com/bla bla.htm\" is a valid url when writing an identifier for it
if i type \"google.com\" in my browser it infact WILL connect me to the site and not say this is no valid url
but then you would have to display almost everything with just a \".\" in it as an url in mirc...
whatever the RFC says there are no special characters allowed (like whatever) but you CAN go and get yourself a domain that includes such characters and will redirect to another url...
i can even type a plain \"blah\" in my firefox addressbar and when i hit enter it will direct me to the first search result for \"blah\", still \"blah\" is no url
my mirc is no browser, it can\'t care about all that when trying to find an url in a text...
i could just go and make a hotlink for \"*\" that would perform \"/url -an $1\" i\'m using firefox so 95% of the times i click a word i would come to a homepage... but that\'s not really reasonable, is it?
i had to set priorities and so this snippet was created
and for the registered protocols... it\'s hard to say what\'s registered and what not... of course ftp http gopher mailto https are registered... but as soon as you install mirc \"irc\" will be a registered protocol for you to, same with ATC or teamspeak or whatever... that\'s why i see every protocol that could exist as a protocol that\'s worth highlighting it