Alex Esplin wrote: > Nope. I'd actually rather see it in text. > > 1. I use email for conveying information in words. > 2. All kinds of fancy formatting in my list is just a waste of bandwidth. > 3. I have a custom-built rocking chair/shooting bench with a clear > field of fire covering my lawn. > > Yeah, it's a little hard to convey a picture of a map in text, but > that's what image viewers were invented for in the first place. When I > see all kinds of colored text, flashing pictures, and crazy formatting > in an email, I assume the sender cares more about getting my attention > than actually conveying information.
I'll agree with you there. If the user is using blinking words, colored text, and other unnecessary and annoying text formatting, I want to puke as well. Who doesn't? Need we recall the web of the '90s? But tell me why the sender can't create a nicely formatted email with bold, underline, font size, and other formatting, maybe including inline images to create a well-structured, well-formatted email, to place emphasis where he wants it, and to help convey the message he's after. It doesn't have to look like http://timecube.com, but it can look clean and tight. After all, isn't the sender composing a document? Isn't email documentation? What I fail to understand is why Unix nerds are so hardcore on plain text formatted email. I used to be that way, but I couldn't make sense of it. I understand top posting and trimming, but plain text? -- . O . O . O . . O O . . . O . . . O . O O O . O . O O . . O O O O . O . . O O O O . O O O
signature.asc
Description: OpenPGP digital signature
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
