Re: [ontolog-forum] Formatting posts [was - Scheduling a Discussion [was

[Duane Nickull <dnickull@xxxxxxxxx>]

                       _   _       _       
  _   _    ___   ___    (_) | |_    (_)  ___ 
 | | | |  / _ \ / __|   | | | __|   | | / __|
 | |_| | |  __/ \__ \   | | | |_    | | \__ \
  \__, |  \___| |___/   |_|  \__|   |_| |___/
  |___/                                      
                                          _                 
   __ _   _ __    _ __     ___    _   _  (_)  _ __     __ _ 
  / _` | | '_ \  | '_ \   / _ \  | | | | | | | '_ \   / _` |
 | (_| | | | | | | | | | | (_) | | |_| | | | | | | | | (_| |
  \__,_| |_| |_| |_| |_|  \___/   \__, | |_| |_| |_|  \__, |
                                  |___/               |___/ 

Please just use plain text.

Thanks

duane

On 1/18/08 10:27 AM, "Pat Hayes" <phayes@xxxxxxx> wrote:

Randall R Schulz wrote:

On Friday 18 January 2008 09:19, Pat Hayes wrote:
  
 

At 7:27 AM -0800 1/18/08, Peter Yim wrote:
    
 

...

It is recommended that you set your mail client to send & receive in
plain text only, and to wrap the text with line length of 65
characters.
      
 

That is easier said than done. I am using Eudora, which is itself now
somewhat ancient, but still belongs to a generation of email handlers
which postdate Unix, and it uses flowed text conventions. It is
impossible to wrap such text with a line length: the very concept of
a line length does not apply,
    
 

I used Eudora for many years, and I don't recall having a problem
getting it to wrap message body text.

  

How did you do it?

  
 

...

All of us have a lot of email traffic to attend to, and to set one's
general preferences to plaintext-only would be suicide in the current
world of general email.
    
 

I don't understand this. Just because someone sends you HTML messages
does not require you to reply in kind.
  

Of course not, but I often (very often) wish to use html in email. I routinely embed images in email, for example.

  
 

The real problem is that either the defaults in MUAs such as Eudora and
Outlook are extremely poorly chosen, or people deliberately configure
them to produce heinous messages. If most people had even a little
sense of what constitutes good typographic design, everything would be
fine, but well chosen sizes, layouts and colors are the exception, not
the rule. The messages on this list are not an exception, either.
  

But to go from this to banning html altogether is like saying that because there are bad drivers, cars should be illegal.

But let us not start an email-format flame war. After Peter's last message I'm trying out Thunderbird, maybe I'll be able to get used to it. However, AFAIKS, it has no provision for making the composing format sensitive to the particular message. If anyone can explain to me how to do it (off-list), I'd be grateful.

Pat

Pat

---

_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/  
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/  
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx
 

-- 
**********************************************************************
"Speaking only for myself"
Senior Technical Evangelist - Adobe Systems, Inc.
Blog - http://technoracle.blogspot.com
Community Music - http://www.mix2r.com
My Band - http://www.myspace.com/22ndcentury
Adobe MAX 2008 - http://technoracle.blogspot.com/2007/08/adobe-max-2008.html
**********************************************************************



_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/  
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/  
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/ 
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx    (01)