@@ -323,10 +323,10 @@ msgid ""
323323"When *decode* is ``False`` (the default) the body is returned as a string "
324324"without decoding the :mailheader:`Content-Transfer-Encoding`. However, for "
325325"a :mailheader:`Content-Transfer-Encoding` of 8bit, an attempt is made to "
326- "decode the original bytes using the ``charset`` specified by the "
327- ":mailheader: `Content-Type` header, using the ``replace`` error handler. If "
328- "no ``charset`` is specified, or if the ``charset`` given is not recognized "
329- "by the email package, the body is decoded using the default ASCII charset."
326+ "decode the original bytes using the ``charset`` specified by the :mailheader "
327+ ":`Content-Type` header, using the ``replace`` error handler. If no "
328+ "``charset`` is specified, or if the ``charset`` given is not recognized by "
329+ "the email package, the body is decoded using the default ASCII charset."
330330msgstr ""
331331"当 *decode* 为 ``False`` (默认值) 时消息体会作为字符串返回而不解码 :mailheader:`Content-Transfer-"
332332"Encoding`。 但是,对于 :mailheader:`Content-Transfer-Encoding` 为 8bit 的情况,会尝试使用 "
@@ -369,9 +369,9 @@ msgid ""
369369":class:`~email.charset.Charset` instance (see :mod:`email.charset`), a "
370370"string naming a character set, or ``None``. If it is a string, it will be "
371371"converted to a :class:`~email.charset.Charset` instance. If *charset* is "
372- "``None``, the ``charset`` parameter will be removed from the "
373- ":mailheader: `Content-Type` header (the message will not be otherwise "
374- "modified). Anything else will generate a :exc:`TypeError`."
372+ "``None``, the ``charset`` parameter will be removed from the :mailheader "
373+ ":`Content-Type` header (the message will not be otherwise modified). "
374+ "Anything else will generate a :exc:`TypeError`."
375375msgstr ""
376376"将载荷的字符集设为 *charset*,它可以是 :class:`~email.charset.Charset` 实例 (参见 "
377377":mod:`email.charset`)、字符集名称字符串或 ``None``。 如果是字符串,它将被转换为一个 "
@@ -382,26 +382,26 @@ msgstr ""
382382msgid ""
383383"If there is no existing :mailheader:`MIME-Version` header one will be added."
384384" If there is no existing :mailheader:`Content-Type` header, one will be "
385- "added with a value of :mimetype:`text/plain`. Whether the "
386- ":mailheader: `Content-Type` header already exists or not, its ``charset`` "
387- "parameter will be set to *charset.output_charset*. If "
388- "*charset.input_charset* and *charset. output_charset* differ, the payload "
389- "will be re-encoded to the *output_charset*. If there is no existing "
390- ":mailheader:`Content-Transfer- Encoding` header, then the payload will be "
391- "transfer-encoded, if needed, using the specified "
392- ":class:`~email.charset.Charset`, and a header with the appropriate value "
393- "will be added. If a :mailheader:`Content-Transfer-Encoding` header already "
394- "exists, the payload is assumed to already be correctly encoded using that "
395- ":mailheader:`Content-Transfer-Encoding` and is not modified."
385+ "added with a value of :mimetype:`text/plain`. Whether the :mailheader "
386+ ":`Content-Type` header already exists or not, its ``charset`` parameter will "
387+ " be set to *charset.output_charset*. If *charset.input_charset* and "
388+ "*charset.output_charset* differ, the payload will be re-encoded to the "
389+ "*output_charset*. If there is no existing :mailheader:`Content-Transfer- "
390+ "Encoding` header, then the payload will be transfer-encoded, if needed, "
391+ "using the specified :class:`~email.charset.Charset`, and a header with the "
392+ "appropriate value will be added. If a :mailheader:`Content-Transfer- "
393+ "Encoding` header already exists, the payload is assumed to already be "
394+ "correctly encoded using that :mailheader:`Content-Transfer-Encoding` and is "
395+ "not modified."
396396msgstr ""
397397"如果 :mailheader:`MIME-Version` 标头不存在则将被添加。 如果 :mailheader:`Content-Type` "
398398"标头不存在,则将添加一个值为 :mimetype:`text/plain` 的该标头。 无论 :mailheader:`Content-Type` "
399399"标头是否已存在,其 ``charset`` 形参都将被设为 *charset.output_charset*。 如果 "
400400"*charset.input_charset* 和 *charset.output_charset* 不同,则载荷将被重编码为 "
401401"*output_charset*。 如果 :mailheader:`Content-Transfer-Encoding` "
402402"标头不存在,则载荷将在必要时使用指定的 :class:`~email.charset.Charset` 来转换编码,并将添加一个具有相应值的标头。 如果"
403- " :mailheader:`Content-Transfer-Encoding` 标头已存在,则会假定载荷已使用该 "
404- ":mailheader: `Content-Transfer-Encoding` 进行正确编码并不会再被修改。"
403+ " :mailheader:`Content-Transfer-Encoding` 标头已存在,则会假定载荷已使用该 :mailheader "
404+ ":`Content-Transfer-Encoding` 进行正确编码并不会再被修改。"
405405
406406#: ../../library/email.compat32-message.rst:266
407407msgid ""
@@ -613,11 +613,11 @@ msgstr ""
613613#: ../../library/email.compat32-message.rst:431
614614msgid ""
615615"Return the message's content type. The returned string is coerced to lower "
616- "case of the form :mimetype:`maintype/subtype`. If there was no "
617- ":mailheader: `Content-Type` header in the message the default type as given "
618- "by :meth:`get_default_type` will be returned. Since according to "
619- ":rfc:`2045`, messages always have a default type, :meth:`get_content_type` "
620- "will always return a value."
616+ "case of the form :mimetype:`maintype/subtype`. If there was no :mailheader "
617+ ":`Content-Type` header in the message the default type as given by "
618+ ":meth:`get_default_type` will be returned. Since according to :rfc:`2045`, "
619+ "messages always have a default type, :meth:`get_content_type` will always "
620+ "return a value."
621621msgstr ""
622622"返回消息的内容类型。 返回的字符串会强制转换为 :mimetype:`maintype/subtype` 的全小写形式。 如果消息中没有 "
623623":mailheader:`Content-Type` 标头则将返回由 :meth:`get_default_type` 给出的默认类型。 因为根据 "
@@ -667,8 +667,8 @@ msgstr ""
667667msgid ""
668668"Set the default content type. *ctype* should either be "
669669":mimetype:`text/plain` or :mimetype:`message/rfc822`, although this is not "
670- "enforced. The default content type is not stored in the "
671- ":mailheader: `Content-Type` header."
670+ "enforced. The default content type is not stored in the :mailheader "
671+ ":`Content-Type` header."
672672msgstr ""
673673"设置默认的内容类型。 *ctype* 应当为 :mimetype:`text/plain` 或者 "
674674":mimetype:`message/rfc822`,尽管这并非强制。 默认的内容类型不会存储在 :mailheader:`Content-Type` "
@@ -690,9 +690,9 @@ msgstr ""
690690
691691#: ../../library/email.compat32-message.rst:483
692692msgid ""
693- "Optional *failobj* is the object to return if there is no "
694- ":mailheader: `Content-Type` header. Optional *header* is the header to "
695- "search instead of :mailheader:`Content-Type`."
693+ "Optional *failobj* is the object to return if there is no :mailheader "
694+ ":`Content-Type` header. Optional *header* is the header to search instead "
695+ "of :mailheader:`Content-Type`."
696696msgstr ""
697697"可选的 *failobj* 是在没有 :mailheader:`Content-Type` 标头时要返回的对象。 可选的 *header* 是要替代 "
698698":mailheader:`Content-Type` 被搜索的标头。"
@@ -714,8 +714,8 @@ msgid ""
714714"header or if there is no such parameter, then *failobj* is returned "
715715"(defaults to ``None``)."
716716msgstr ""
717- "将 :mailheader:`Content-Type` 标头的形参 *param* 作为字符串返回。 如果消息没有 "
718- ":mailheader: `Content-Type` 标头或者没有这样的形参,则返回 *failobj* (默认为 ``None``)。"
717+ "将 :mailheader:`Content-Type` 标头的形参 *param* 作为字符串返回。 如果消息没有 :mailheader "
718+ ":`Content-Type` 标头或者没有这样的形参,则返回 *failobj* (默认为 ``None``)。"
719719
720720#: ../../library/email.compat32-message.rst:500
721721msgid ""
@@ -884,8 +884,8 @@ msgid ""
884884"has no :mailheader:`Content-Type` header."
885885msgstr ""
886886"将 :mailheader:`Content-Type` 头字段的 ``boundary`` 参数设置为 *boundary* 。 "
887- ":meth:`set_boundary` 方法永远都会在必要的时候为 *boundary* 添加引号。如果信息对象中没有 "
888- ":mailheader: `Content-Type` 头字段,抛出 :exc:`~email.errors.HeaderParseError` 异常。"
887+ ":meth:`set_boundary` 方法永远都会在必要的时候为 *boundary* 添加引号。如果信息对象中没有 :mailheader "
888+ ":`Content-Type` 头字段,抛出 :exc:`~email.errors.HeaderParseError` 异常。"
889889
890890#: ../../library/email.compat32-message.rst:611
891891msgid ""
0 commit comments