Barry Warsaw | 40ef006 | 2006-03-18 15:41:53 +0000 | [diff] [blame] | 1 | \declaremodule{standard}{email.encoders} |
Barry Warsaw | 5e63463 | 2001-09-26 05:23:47 +0000 | [diff] [blame] | 2 | \modulesynopsis{Encoders for email message payloads.} |
Barry Warsaw | 5e63463 | 2001-09-26 05:23:47 +0000 | [diff] [blame] | 3 | |
| 4 | When creating \class{Message} objects from scratch, you often need to |
| 5 | encode the payloads for transport through compliant mail servers. |
Barry Warsaw | c5f8fe3 | 2001-09-26 22:21:52 +0000 | [diff] [blame] | 6 | This is especially true for \mimetype{image/*} and \mimetype{text/*} |
| 7 | type messages containing binary data. |
Barry Warsaw | 5e63463 | 2001-09-26 05:23:47 +0000 | [diff] [blame] | 8 | |
| 9 | The \module{email} package provides some convenient encodings in its |
Barry Warsaw | 40ef006 | 2006-03-18 15:41:53 +0000 | [diff] [blame] | 10 | \module{encoders} module. These encoders are actually used by the |
Barry Warsaw | bb11386 | 2004-10-03 03:16:19 +0000 | [diff] [blame] | 11 | \class{MIMEAudio} and \class{MIMEImage} class constructors to provide default |
| 12 | encodings. All encoder functions take exactly one argument, the message |
| 13 | object to encode. They usually extract the payload, encode it, and reset the |
| 14 | payload to this newly encoded value. They should also set the |
| 15 | \mailheader{Content-Transfer-Encoding} header as appropriate. |
Barry Warsaw | 5e63463 | 2001-09-26 05:23:47 +0000 | [diff] [blame] | 16 | |
| 17 | Here are the encoding functions provided: |
| 18 | |
| 19 | \begin{funcdesc}{encode_quopri}{msg} |
Barry Warsaw | 5db478f | 2002-10-01 04:33:16 +0000 | [diff] [blame] | 20 | Encodes the payload into quoted-printable form and sets the |
Barry Warsaw | 5b9da89 | 2002-10-01 01:05:52 +0000 | [diff] [blame] | 21 | \mailheader{Content-Transfer-Encoding} header to |
Barry Warsaw | 5e63463 | 2001-09-26 05:23:47 +0000 | [diff] [blame] | 22 | \code{quoted-printable}\footnote{Note that encoding with |
| 23 | \method{encode_quopri()} also encodes all tabs and space characters in |
| 24 | the data.}. |
| 25 | This is a good encoding to use when most of your payload is normal |
| 26 | printable data, but contains a few unprintable characters. |
| 27 | \end{funcdesc} |
| 28 | |
| 29 | \begin{funcdesc}{encode_base64}{msg} |
Barry Warsaw | 5b9da89 | 2002-10-01 01:05:52 +0000 | [diff] [blame] | 30 | Encodes the payload into base64 form and sets the |
Barry Warsaw | c5f8fe3 | 2001-09-26 22:21:52 +0000 | [diff] [blame] | 31 | \mailheader{Content-Transfer-Encoding} header to |
Barry Warsaw | 5e63463 | 2001-09-26 05:23:47 +0000 | [diff] [blame] | 32 | \code{base64}. This is a good encoding to use when most of your payload |
| 33 | is unprintable data since it is a more compact form than |
Barry Warsaw | 5b9da89 | 2002-10-01 01:05:52 +0000 | [diff] [blame] | 34 | quoted-printable. The drawback of base64 encoding is that it |
Barry Warsaw | 5e63463 | 2001-09-26 05:23:47 +0000 | [diff] [blame] | 35 | renders the text non-human readable. |
| 36 | \end{funcdesc} |
| 37 | |
| 38 | \begin{funcdesc}{encode_7or8bit}{msg} |
| 39 | This doesn't actually modify the message's payload, but it does set |
Barry Warsaw | c5f8fe3 | 2001-09-26 22:21:52 +0000 | [diff] [blame] | 40 | the \mailheader{Content-Transfer-Encoding} header to either \code{7bit} or |
Barry Warsaw | 5e63463 | 2001-09-26 05:23:47 +0000 | [diff] [blame] | 41 | \code{8bit} as appropriate, based on the payload data. |
| 42 | \end{funcdesc} |
| 43 | |
| 44 | \begin{funcdesc}{encode_noop}{msg} |
| 45 | This does nothing; it doesn't even set the |
Barry Warsaw | c5f8fe3 | 2001-09-26 22:21:52 +0000 | [diff] [blame] | 46 | \mailheader{Content-Transfer-Encoding} header. |
Barry Warsaw | 5e63463 | 2001-09-26 05:23:47 +0000 | [diff] [blame] | 47 | \end{funcdesc} |