views:

406

answers:

8

I'm wondering if word wrapping should be applied in text emails? And what about HTML emails? If so, what character would you normally wrap at?

+7  A: 

RFC 2646 says:

The Text/Plain media type is the lowest common denominator of Internet email, with lines of no more than 997 characters (by convention usually no more than 80)

Another popular standard is to wrap at 72 characters. This dates back to many console applications (like EDIT and many BBS interfaces) that displayed text within an ASCII "window" including a border and scrollbar, allowing slightly less than 80 characters to be displayed.

Sparr
Agreed. I always wrap at 80, and if that would break a word, I'd wrap at less than 80, wherever the first space or line break is prior to that eightieth character.
hmcclungiii
A: 

Generally you should wrap at 80, or a little less to allow dim clients to quote without wrapping.

Douglas Leeder
A: 

Didn't use linewrap, until I had switched to mutt/xterm (never looking back).

Zsolt Botykai
A: 

Wrap at the first whitespace character before the 72nd position, or at the 72nd position if there isn't one. In Eudora when I used to use it, the convention was to leave a space at the end of the line indicating that it was wrapped, so it would signal the receiving client to re-flow the paragraph wherever it needed based on the width of the client's window. I'm not sure that this is the case in current email clients.

FryGuy
I think the trailing character (be it a space, hyphen, or other wrap-breakable punctuation) should always be left.
Sparr
+4  A: 

It is common to wrap lines at 72 (80 is also common but that means that it will go over 80 when quoted) to handle at least one or two levels of quotation. There is the "text/flowed" MIME type which means that the client will wrap text itself at window's boundaries but not that many clients support it. Just setup your editor to wrap at 72 and you will be safe and readable by the most people.

EDIT: the exact type is text/plain with the addition of format=flowed like this:

Content-Type: text/plain; format=flowed

See rfc2646 for explanations.

HTML mail should be avoided IMNSHO, not everybody reads mail in a browser or have HTML-enabled mail clients. Most reasons to use HTML (enriching mail with underline, bold and such) can be emulated. HTML doesn't need to be wrapped as the client will adapt to the window size.

An alternative to HTML is the "text/enriched" MIME type which gives you most of the advantages of HTML mails w/o the hassle but again, may not be supported everywhere.

See here for text/enriched.

Keltia
A: 

Google says Results 1 - 10 of about ...

3,160 for +word +wrap +email +"80 characters"
2,820 for +word +wrap +email +"50 characters"
1,790 for +word +wrap +email +"60 characters"
1,720 for +word +wrap +email +"70 characters"
1,540 for +word +wrap +email +"100 characters"
1,250 for +word +wrap +email +"65 characters"
1,120 for +word +wrap +email +"40 characters"
  962 for +word +wrap +email +"75 characters"
  836 for +word +wrap +email +"72 characters"
Sparr
Google can only tell you where is the crowd going... not if it's going in the right direction :-)
siukurnin
Sure, but the gist of this question was mostly where the crowd is going :)
Sparr
+1  A: 

I often find myself starting e-mail replies with:

[Format recovered--see http://www.lemis.com/email/email-format.html]

which I got from Greg Lehey. Part of that page says:

Clearly, there must be some way of specifying that the message text should not be wrapped. That's text/plain. There are special MIME attachment types which allow wrapping, although I still think that this is a bad idea. If you specify that your message may be wrapped, you're making an assumption about what the receiver's screen looks like. Even if you're right some of the time, you can't be right all of the time. For example, one person may have a screen 200 characters wide in order to be able to display long log file entries, but he won't want to see his text that long.

Dave C
+1  A: 

A good mail API like JavaMail will do this for you. Ideally, you would not have to think about this issue explicitly.

Chase Seibert
Agreed, and on all newer sites I do use a library. On this site unfortunately, it's so old I did not and it would be a paid to add one.
Darryl Hein