HTML email: Difference between revisions

Content deleted Content added
Drawbacks: «"ASCII" → "ASCII
that goes in the multi section
Line 8:
 
== Drawbacks ==
A few recipients have [[e-mail client]]s that cannot display HTML. This may be mitigated by the inclusion of an automatically generated plain text version, which may be missing important formatting information (e.g. an equation may lose a superscript and take on an entirely new meaning).
 
Some senders may excessively rely upon large, colorful, or distracting fonts making all but the shortest messages more difficult to read.
 
Line 18 ⟶ 16:
== Multi-part formats ==
Many email clients are configured to send a plain text version of a message along with the HTML version, to ensure that it can be read even by text-only clients, using the <code>[[MIME#Content-Type|Content-Type]]: [[MIME#Alternative|multipart/alternative]]</code>, as specified in RFC 1521.<ref>[http://www.freesoft.org/CIE/RFC/1521/18.htm RFC 1521 7.2.3. The Multipart/alternative subtype]</ref><ref>[http://www.codestone.ltd.uk/software/docs/csmail/tn1010-11-2.pdf TN1010-11-2: Multipart/Alternative – Gracefully handling HTML-phobic email clients.]</ref><ref>[http://www.wilsonweb.com/wmt5/html-email-multi.htm Sending HTML and Plain Text E-Mail Simultaneously]</ref> The message itself is of type multipart/alternative, and contains two parts, the first of type text/plain, which is read by text-only clients, and the second with text/html, which is read by HTML-capable clients.
 
A few recipients have [[e-mail client]]s that cannot display HTML. This may be mitigated by the inclusion of an automatically generated plain text version, whichbut this may be missing important formatting information (e.g. an equation may lose a superscript and take on an entirely new meaning).
 
== Message size ==