I'm stumped. I'm not so sure what is the answer to that question. I'll do some investigation and get back to you if I bump into an good answer. You should email the people at iPage as they probably could answer your iPage question..
Hmmm...as far as I know IE opens txt docs in the browser window too. Will even treat a TXT document pretty much like any html document if you include HTML tags. Once you insert a body tag into a TXT document you will most likley lose the TXT formatting though..
At home, IE 5.5 opens Notepad to display .txt documents (on a msWin98 system). At work, IE 5.0 opens Textpad (on a msWin95 system). Textpad is a shareware app which I have set to my default text viewer. I have never configured IE to do anything special with .txt documents...
I'm getting different results than BOTH of you..
I open a linked txt document in IE in both win98 and win2k and I see a html page that shows the entire code as typed. The page itself doesn't render the HTML... but it also does not spawn notepad, wordpad, or textpad. I have notepad, word, and wordpad on both machines..
No special config as I just totally rebuilt this entire machine...
I'm also getting this. But isn't this the default?..
I thought it was default too. But Kevin reported that IE opened the text documents in a browser/word window and rendered the HTML... while mine just displayed all of it like text, HTML tags and all..
Rock reported that it would spawn one of various applications to view the text document... which also did not happen (to me)...
Mine does what Kevin's does (at least for .rtf files, haven't tried it with .txt lately) and opens in the browser/word window (kinda like the way acrobat reader works)..
Interesting and I can't recall ever changing the defaults so that IE 5.5 and MS Word would perform differently..
Do this Doc, take a text file and add a body tag to it but leave it as a page.txt document, upload it and watch what happens. Remove the body tag and try again..
OK...but are you talking about internet or local files?.
The browser does not render HTML, it just displays it. However, if you open txt files using Ctrl+L/O, it will use the default text-editing app to open it. If you follow a link, it will just display the text in the browser. eg.
Good catch. When displaying local .txt files, IE launches the default text viewer (eg notepad). But when displaying .txt documents from the Internet, it displays the text files within itself..
It had not occurred to me that it would care where the file came from...
Thats why I get paid the big bucks, or I'm supposed to anyway.
Actually it's easy to get them confused since Windows wraps everything up in an explorer shell, my guess is that the difference is the header sent from the server along with the document, be it an html file or a txt file. If you drop a local txt file into a browser window (even one with all the html tags needed for a webpage as Doc noted) since there is no http header (or any other internet header) it's treated as what it is, a plain old text file. Same file recieved from a webserver though will display as an html document as long as it is an ASCII file regardless of the extension. You can name a file named index.rock and it will still display as a webpage if recieved from a server via a browser..
Netscape is a different story, if it sees any extension beside htm or html, and the file is an ASCII file, it will display the file as plaintext..
To me there is a big difference between the mind set of the Netscape devs (if there is such a thing anymore) and the MS devs that make IE. Netscape treats stuff literally like it's coming from another machine which will not make mistakes. IE treats stuff like what it is, it comes from another machine but the underlying source is a human, which we all know is quite prone to making mistakes and likes to mess around and have fun, not sit in classrooms or open reference materials and learn code...