/Doc/library/email.charset.rst

http://unladen-swallow.googlecode.com/ · ReStructuredText · 253 lines · 157 code · 96 blank · 0 comment · 0 complexity · 4484a12c3fa3066227016d24781878b4 MD5 · raw file

  1. :mod:`email`: Representing character sets
  2. -----------------------------------------
  3. .. module:: email.charset
  4. :synopsis: Character Sets
  5. This module provides a class :class:`Charset` for representing character sets
  6. and character set conversions in email messages, as well as a character set
  7. registry and several convenience methods for manipulating this registry.
  8. Instances of :class:`Charset` are used in several other modules within the
  9. :mod:`email` package.
  10. Import this class from the :mod:`email.charset` module.
  11. .. versionadded:: 2.2.2
  12. .. class:: Charset([input_charset])
  13. Map character sets to their email properties.
  14. This class provides information about the requirements imposed on email for a
  15. specific character set. It also provides convenience routines for converting
  16. between character sets, given the availability of the applicable codecs. Given
  17. a character set, it will do its best to provide information on how to use that
  18. character set in an email message in an RFC-compliant way.
  19. Certain character sets must be encoded with quoted-printable or base64 when used
  20. in email headers or bodies. Certain character sets must be converted outright,
  21. and are not allowed in email.
  22. Optional *input_charset* is as described below; it is always coerced to lower
  23. case. After being alias normalized it is also used as a lookup into the
  24. registry of character sets to find out the header encoding, body encoding, and
  25. output conversion codec to be used for the character set. For example, if
  26. *input_charset* is ``iso-8859-1``, then headers and bodies will be encoded using
  27. quoted-printable and no output conversion codec is necessary. If
  28. *input_charset* is ``euc-jp``, then headers will be encoded with base64, bodies
  29. will not be encoded, but output text will be converted from the ``euc-jp``
  30. character set to the ``iso-2022-jp`` character set.
  31. :class:`Charset` instances have the following data attributes:
  32. .. attribute:: input_charset
  33. The initial character set specified. Common aliases are converted to
  34. their *official* email names (e.g. ``latin_1`` is converted to
  35. ``iso-8859-1``). Defaults to 7-bit ``us-ascii``.
  36. .. attribute:: header_encoding
  37. If the character set must be encoded before it can be used in an email
  38. header, this attribute will be set to ``Charset.QP`` (for
  39. quoted-printable), ``Charset.BASE64`` (for base64 encoding), or
  40. ``Charset.SHORTEST`` for the shortest of QP or BASE64 encoding. Otherwise,
  41. it will be ``None``.
  42. .. attribute:: body_encoding
  43. Same as *header_encoding*, but describes the encoding for the mail
  44. message's body, which indeed may be different than the header encoding.
  45. ``Charset.SHORTEST`` is not allowed for *body_encoding*.
  46. .. attribute:: output_charset
  47. Some character sets must be converted before they can be used in email headers
  48. or bodies. If the *input_charset* is one of them, this attribute will
  49. contain the name of the character set output will be converted to. Otherwise, it will
  50. be ``None``.
  51. .. attribute:: input_codec
  52. The name of the Python codec used to convert the *input_charset* to
  53. Unicode. If no conversion codec is necessary, this attribute will be
  54. ``None``.
  55. .. attribute:: output_codec
  56. The name of the Python codec used to convert Unicode to the
  57. *output_charset*. If no conversion codec is necessary, this attribute
  58. will have the same value as the *input_codec*.
  59. :class:`Charset` instances also have the following methods:
  60. .. method:: get_body_encoding()
  61. Return the content transfer encoding used for body encoding.
  62. This is either the string ``quoted-printable`` or ``base64`` depending on
  63. the encoding used, or it is a function, in which case you should call the
  64. function with a single argument, the Message object being encoded. The
  65. function should then set the :mailheader:`Content-Transfer-Encoding`
  66. header itself to whatever is appropriate.
  67. Returns the string ``quoted-printable`` if *body_encoding* is ``QP``,
  68. returns the string ``base64`` if *body_encoding* is ``BASE64``, and
  69. returns the string ``7bit`` otherwise.
  70. .. method:: convert(s)
  71. Convert the string *s* from the *input_codec* to the *output_codec*.
  72. .. method:: to_splittable(s)
  73. Convert a possibly multibyte string to a safely splittable format. *s* is
  74. the string to split.
  75. Uses the *input_codec* to try and convert the string to Unicode, so it can
  76. be safely split on character boundaries (even for multibyte characters).
  77. Returns the string as-is if it isn't known how to convert *s* to Unicode
  78. with the *input_charset*.
  79. Characters that could not be converted to Unicode will be replaced with
  80. the Unicode replacement character ``'U+FFFD'``.
  81. .. method:: from_splittable(ustr[, to_output])
  82. Convert a splittable string back into an encoded string. *ustr* is a
  83. Unicode string to "unsplit".
  84. This method uses the proper codec to try and convert the string from
  85. Unicode back into an encoded format. Return the string as-is if it is not
  86. Unicode, or if it could not be converted from Unicode.
  87. Characters that could not be converted from Unicode will be replaced with
  88. an appropriate character (usually ``'?'``).
  89. If *to_output* is ``True`` (the default), uses *output_codec* to convert
  90. to an encoded format. If *to_output* is ``False``, it uses *input_codec*.
  91. .. method:: get_output_charset()
  92. Return the output character set.
  93. This is the *output_charset* attribute if that is not ``None``, otherwise
  94. it is *input_charset*.
  95. .. method:: encoded_header_len()
  96. Return the length of the encoded header string, properly calculating for
  97. quoted-printable or base64 encoding.
  98. .. method:: header_encode(s[, convert])
  99. Header-encode the string *s*.
  100. If *convert* is ``True``, the string will be converted from the input
  101. charset to the output charset automatically. This is not useful for
  102. multibyte character sets, which have line length issues (multibyte
  103. characters must be split on a character, not a byte boundary); use the
  104. higher-level :class:`~email.header.Header` class to deal with these issues
  105. (see :mod:`email.header`). *convert* defaults to ``False``.
  106. The type of encoding (base64 or quoted-printable) will be based on the
  107. *header_encoding* attribute.
  108. .. method:: body_encode(s[, convert])
  109. Body-encode the string *s*.
  110. If *convert* is ``True`` (the default), the string will be converted from
  111. the input charset to output charset automatically. Unlike
  112. :meth:`header_encode`, there are no issues with byte boundaries and
  113. multibyte charsets in email bodies, so this is usually pretty safe.
  114. The type of encoding (base64 or quoted-printable) will be based on the
  115. *body_encoding* attribute.
  116. The :class:`Charset` class also provides a number of methods to support
  117. standard operations and built-in functions.
  118. .. method:: __str__()
  119. Returns *input_charset* as a string coerced to lower
  120. case. :meth:`__repr__` is an alias for :meth:`__str__`.
  121. .. method:: __eq__(other)
  122. This method allows you to compare two :class:`Charset` instances for
  123. equality.
  124. .. method:: __ne__(other)
  125. This method allows you to compare two :class:`Charset` instances for
  126. inequality.
  127. The :mod:`email.charset` module also provides the following functions for adding
  128. new entries to the global character set, alias, and codec registries:
  129. .. function:: add_charset(charset[, header_enc[, body_enc[, output_charset]]])
  130. Add character properties to the global registry.
  131. *charset* is the input character set, and must be the canonical name of a
  132. character set.
  133. Optional *header_enc* and *body_enc* is either ``Charset.QP`` for
  134. quoted-printable, ``Charset.BASE64`` for base64 encoding,
  135. ``Charset.SHORTEST`` for the shortest of quoted-printable or base64 encoding,
  136. or ``None`` for no encoding. ``SHORTEST`` is only valid for
  137. *header_enc*. The default is ``None`` for no encoding.
  138. Optional *output_charset* is the character set that the output should be in.
  139. Conversions will proceed from input charset, to Unicode, to the output charset
  140. when the method :meth:`Charset.convert` is called. The default is to output in
  141. the same character set as the input.
  142. Both *input_charset* and *output_charset* must have Unicode codec entries in the
  143. module's character set-to-codec mapping; use :func:`add_codec` to add codecs the
  144. module does not know about. See the :mod:`codecs` module's documentation for
  145. more information.
  146. The global character set registry is kept in the module global dictionary
  147. ``CHARSETS``.
  148. .. function:: add_alias(alias, canonical)
  149. Add a character set alias. *alias* is the alias name, e.g. ``latin-1``.
  150. *canonical* is the character set's canonical name, e.g. ``iso-8859-1``.
  151. The global charset alias registry is kept in the module global dictionary
  152. ``ALIASES``.
  153. .. function:: add_codec(charset, codecname)
  154. Add a codec that map characters in the given character set to and from Unicode.
  155. *charset* is the canonical name of a character set. *codecname* is the name of a
  156. Python codec, as appropriate for the second argument to the :func:`unicode`
  157. built-in, or to the :meth:`encode` method of a Unicode string.