On 12/2/02 9:16 PM, "Peter C.S. Adams" <[EMAIL PROTECTED]> wrote: > I'm not saying that 80 columns is a bad place to break a line, I'm saying it > would be nice to be able to change it or override it. My message contained a > valid and somewhat common case where 100+ characters might be needed on a > line. Having an 80 character line hard coded into the program isn't a > showstopper, but it seems like an odd programming decision, since it isn't a > requirement, just a guideline.
Well, it's not just a guideline. Many (if not most) mail servers will break lines for you, even if your mail client doesn't. Breaking lines at the client end at least gives you some amount of control over the process. That's one thing "format=flowed" gets around; it assumes that your lines are going to be broken, but indicates where the original lines began/ended. The receiving client then re-joins them (assuming it supports "flowed"). On 12/5/02 1:28 PM, "Bryan Harris" <[EMAIL PROTECTED]> wrote: >> Yes, it's a remote hope. And, yes, it's difficult to implement if you want >> to do it right because you have to move from simple > delimiting of quoted >> text to something better. > > So why not just hard wrap the quoted text before quoting? What does Eudora > do about this? That's the big (and I mean BIG, IMO) drawback to format=flowed. The receiving client has to understand format=flowed, and then has to use some client-specific approach to designating quotes and quote levels. Eudora uses horrible (IMO) vertical bars for this. I think these bars are very confusing and make discerning multiple levels of quoting very difficult to read. -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
