object to your assertion that MLA is the only standard for scholarly publications when, in fact, that statement is not true. APA is more widely used in non-English/non-Journalism scholarly
publications than MLA is; Kate Turabian still has her proponents out there too. Each of those styles are basically
the same, but they do differ in very important ways.
You seem to be upset that mIRC
is not anticipating every possible occurance of a web page address because it does not strip out some characters, to whit, < and > (commonly refered to as angle brackets
) . You have not mentioned mIRC
automatically stripping control codes yet, but I'm assuming that will be forthcoming shortly. While we're talking about modifying what mIRC
should and should not tamper with, exactly how do you suggest dealing with those malformed URLs that are commonplace in almost all media now?
Everyone (intentional hasty generalization) knows that if you are told to go to amazon.com, you open your browser and type in http://www.amazon.com
and then click the "Go" button or depress the Enter key and off you go, ordering nifty media over the Internet. Should mIRC
recognize such things as amazon.com or ebay.com as URLs and allow you to double-click them? Common usage indicates that it should; strictest adherence to some RFC written ages ago, however, may preclude such an adherence for the purists. (That
argument continues that those purists should go back to using Telnet as their IRC client.)
How about other forms of puntuation that are commonly concatenated with a valid URL? I frequently see someone say something like:<Someone> That's on http://www.thissite.com/thispage...but I haven't been there in a while.
(Note how this .php page messes up the URL as well and that
is its business!) Now obviously, a human can look at that URL and tell that it stops at the first period (full stop) and that you might have to add .html or .htm or something similar to make the page show up in your browser...these days, .php is a new popular extension, though you will also see extensions over 3 or 4 letters with regularity. So, obviously we cannot use the space character.
You advocate using < and > as delimiters and this will solve the problem. Yeah right!
Good luck training the general public to ALWAYS, ALWAYS, ALWAYS enclose their URLs in angle brackets. Complaining about something like this is petty; it's exactly like the time I emailed Eudora because their email client cannot correctly handle a validly-formed mailto string (while even Outlook Express can!).What was the problem?
Eudora (and a few other email clients) cannot correctly handle %0D%0A in the body section of a mailto string.Did it get changed?
No. Why not?
Because in the long run, it doesn't matter. There are more important bugs to fix. Is it an anomaly or does it "break" a protocol that some folks agreed on and wrote down?
Perhaps. I didn't agree to
it, though I did agree with
it.Is it high on the list of things to fix?
I wouldn't think so.Will it ever get fixed to your satisfaction?
But whether you like the style or not is really of no importance. Since they are invalid characters, any correctly functioning URL parsing algorithm MUST stop scanning when it reaches one.
Speaking as a programmer and systems analyst, I believe you are confusing functions here. The browser
of your choice should be the process figuring out what is and what is not a valid URL for it to try to access. True, perhaps it would help if the process feeding the URL to the browser could get it close, but I should think that a well-written browser should be able to parse a URL; wouldn't you think so, too? That is
, after all, a major part of what a browser does
; conversely, mIRC
a browser, though it can launch a browser when it sees what it thinks might
be a URL. mIRC
even provides a way (since 23/09/99 - mIRC v5.61) for the end user to customize, through script, exactly what hotlinks are and what are not. This thread
even shows how to strip those naughty angle brackets out, as well as a few other characters that seem to give folks fits when they double-click. I think that's pretty darned good, really. It has made it easier for us to get to web pages that our friends show us.
Don't forget. Hotlinks originally were intended to be used for nicks and channels. Khaled just expanded that idea to include web pages and came up with a way to let mIRC
launch a browser using that URL. mIRC
is not a URL parser, it was never intended to be; it is an Internet Relay Chat program that has, over the years, blossomed into a multimedia extravaganza. Your mIRC
can start up movies now, bring up web pages in a browser, play MP3s ... and STILL
let you chat with your friends from around the world.mIRC
is not forced to submit to MLA standards, nor APA, nor Kate L. Turabian's (may she rest in peace) nor even any (outdated?) RFCs you may have read. I find it rather amazing that mIRC
can access so many different IRC networks and work on them all, even though many of them break protocols all the time, or even write their own (re: IRCnet). mIRC
is the brainchild and play toy of one man, Khaled Mardam-Bey. It just so happens that many of us like his toy and ask to play with it too. It seems to me that this particular request is asking mIRC
's creator to alter his toy that he designed and built because you don't like one of the ways it works since it does not follow some ordinance written somewhere.
Mind you, I am objecting to your tone and your legalistic approach, not the fact that you are making a suggestion. Suggestions are quite welcome; I frequently make them myself. Some suggestions make it into mIRC
and some don't. In the end, those suggestions that Khaled likes and wants to add to his toy, he does. The rest are filled for future consideration.