[prev] [thread] [next] [lurker] [Date index for 2004/10/26]
On Oct 26, 2004, at 9:32, Ann Barcomb wrote: > On Mon, 25 Oct 2004, David King wrote: > >> One of my clients is a 100% >> Windows-Bill-Gates-Worshipping-buy-everything-he-sells shop. So the >> tools in front of me are all Microsoft tools. But, of course, they >> suck. Why does IE's FTP client assume that my starting directory >> (reported by pwd on logon) is the only one that I want to access? >> Just because my server puts me in /home/<tt>user</tt> to start > ... > > So why do people assume that my mail application displays HTML, or that > I want it to? I'd guess it's because 99% of people who can read email, can read HTML email. It's a perfectly reasonable assumption. Furthermore, that mail was sent as a multipart/alternative, with a text part and an HTML part, also a perfectly reasonable thing to do, and if your mail client can't deal with it and display the right part to you, this is your problem. Having said that, the _correct_ rant is that the plain text part of that email looks like this: . . Why does IE's FTP client assume that my starting directory (reported by = pwd on logon) is the only one that I want to access? Just because my = server puts me in /home/<tt>user</tt> to start doesn't mean that's the = only place I want to go, first of all. Second of all, if you're going to = do that, do it <em>all</em> of the time! If I type = ftp://<tt>host</tt>/<tt>path</tt>;, I want to go to ~/path within where I = . . and so is a nasty HTML-tag-containing single run-on line of nastiness. But that's not a fault of HTML email. I blame.. uh.. poke, poke. Oh. Outlook Express. Sigh. tomThere's stuff above here
Generated at 11:01 on 29 Oct 2004 by mariachi 0.52