[Dev-C++] HTML v. Plain Text

[Brian P. <br...@su...>]

O.k. Folks, and I mean everybody:
Have we got this out of our system yet?  This battle has been going on
for years and I doubt that it will be settled here, so back to
business...Dev-C++ business.  That is what this list is for, remember?  

If Colin, or whoever moderates the list, thinks HTML is an issue it will
be addressed, until then, every man/woman back to their stations.

b--

(P.s. I realize that I too responded to this issue not realizing how far
it would go.  I am sorry I said anything at all).


On Sat, 2002-05-18 at 19:07, Bob Wilson wrote:
> Well here goes,
>   Your message only contains a few lines of bold text. How does such a formatting "enhance" the understanding.
> To you nothing, but it is easier for a reader to distinguish the original from the response. Conversely, the ">" interferes with reading a paragraph. It is an unexpected character that slows down the eye and interrupts the flow of reading.
> 
>   Emails were designed to display well *everywhere*. Which email client I'm using should not matter. This is exactly the problem: you'll have to use Windows just to be able to read emails well.
> Considering that dev-c++ was developed for windows, it is not unreasonable to expect emails to be originated and received by the e-mail utilities integral to windows. 
>    
>   If MS [would] just ditch HTML and script support, invisible script viruses would not exist at all.
> Perhaps, but I am not willing to underestimate the ability of people to cause problems on either the Internet in general or on our respective computers. 
>   This is not "my" environment, I'm talking about the mailing list's email archive here! You're messing up the archive, so no matter which browser/OS/computer/whatever you're using, if you look at the HTML mails in the archive, you will only see HTML tags.
>    
> In regards to the archives on the server of the e-mail discussions, html based e-mails should not be a problem here either, but they are. The web archival system should be able to display an html message "htmlly" as well as one that is purely textual. Obviously that is not the case, but it should be. To me, the inconvenience posed by the html tags when you review an html based message archived  on the web site is more than offset by the enhanced communications formatting offers to those who receive the message directly. That all assumes that the message is formatted in a way which does not detract from the communications. Please do not think that this paragraph is a slam directed at you or anyone else. It's not. It is simply a commentary on the level of maturity and sophistication of the Internet. We all tolerate things on the internet that we cause us to return software to the maker if it had the same errors or limitations we experience daily with various web sites. 
> 
> Regards,
> 
> Bob
> 
>