Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit b82102f

Browse files
github-actions[bot]github-actions[bot]
committed
[po] auto sync
1 parent ab0f519 commit b82102f

16 files changed

Lines changed: 108 additions & 110 deletions

‎c-api/typeobj.po‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -591,9 +591,9 @@ msgstr ""
591591
msgid ""
592592
"This bit is set when the object supports garbage collection. If this bit is"
593593
" set, instances must be created using :c:func:`PyObject_GC_New` and "
594-
"destroyed using :c:func:`PyObject_GC_Del`. More information in section "
595-
":ref:`supporting-cycle-detection`. This bit also implies that the GC-"
596-
"related fields :c:member:`~PyTypeObject.tp_traverse` and "
594+
"destroyed using :c:func:`PyObject_GC_Del`. More information in section :ref"
595+
":`supporting-cycle-detection`. This bit also implies that the GC-related "
596+
"fields :c:member:`~PyTypeObject.tp_traverse` and "
597597
":c:member:`~PyTypeObject.tp_clear` are present in the type object."
598598
msgstr ""
599599

‎howto/logging.po‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -334,8 +334,8 @@ msgid ""
334334
"simple usage pattern, you won't know, by looking in the log file, *where* in"
335335
" your application your messages came from, apart from looking at the event "
336336
"description. If you want to track the location of your messages, you'll need"
337-
" to refer to the documentation beyond the tutorial level -- see "
338-
":ref:`logging-advanced-tutorial`."
337+
" to refer to the documentation beyond the tutorial level -- see :ref"
338+
":`logging-advanced-tutorial`."
339339
msgstr ""
340340
"这是你期待看到的。 你可以使用 *mylib.py* 中的模式将此概括为多个模块。 "
341341
"请注意，对于这种简单的使用模式，除了查看事件描述之外，你不能通过查看日志文件来了解应用程序中消息的 *来源* 。 "
@@ -853,8 +853,8 @@ msgid ""
853853
"arguments), while if the style is '$' then the message format string should "
854854
"conform to what is expected by :meth:`string.Template.substitute`."
855855
msgstr ""
856-
"如果 ``style`` 是 '％'，则消息格式字符串使用 ``%(<dictionary key>)s`` 样式字符串替换；可能的键值在 "
857-
":ref:`logrecord-attributes` 中。 如果样式为 '{'，则假定消息格式字符串与 :meth:`str.format` "
856+
"如果 ``style`` 是 '％'，则消息格式字符串使用 ``%(<dictionary key>)s`` 样式字符串替换；可能的键值在 :ref"
857+
":`logrecord-attributes` 中。 如果样式为 '{'，则假定消息格式字符串与 :meth:`str.format` "
858858
"（使用关键字参数）兼容，而如果样式为 '$' ，则消息格式字符串应符合 :meth:`string.Template.substitute` 。"
859859

860860
#: ../../howto/logging.rst:555

‎howto/unicode.po‎

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -402,8 +402,8 @@ msgid ""
402402
"names; for example, ``'latin-1'``, ``'iso_8859_1'`` and ``'8859``' are all "
403403
"synonyms for the same encoding."
404404
msgstr ""
405-
"编码格式以包含编码格式名称的字符串来指明。 Python 有大约 100 种不同的编码格式；清单详见 Python 库参考文档 "
406-
":ref:`standard-encodings`。 一些编码格式有多个名称，比如 ``'latin-1'``、``'iso_8859_1'`` 和 "
405+
"编码格式以包含编码格式名称的字符串来指明。 Python 有大约 100 种不同的编码格式；清单详见 Python 库参考文档 :ref"
406+
":`standard-encodings`。 一些编码格式有多个名称，比如 ``'latin-1'``、``'iso_8859_1'`` 和 "
407407
"``'8859`` 都是指同一种编码。"
408408

409409
#: ../../howto/unicode.rst:253
@@ -1013,11 +1013,10 @@ msgstr ""
10131013
#: ../../howto/unicode.rst:740
10141014
msgid ""
10151015
"The `PDF slides for Marc-André Lemburg's presentation \"Writing Unicode-"
1016-
"aware Applications in Python\" "
1017-
"<https://downloads.egenix.com/python/LSM2005-Developing-Unicode-aware-"
1018-
"applications-in-Python.pdf>`_ discuss questions of character encodings as "
1019-
"well as how to internationalize and localize an application. These slides "
1020-
"cover Python 2.x only."
1016+
"aware Applications in Python\" <https://downloads.egenix.com/python/LSM2005"
1017+
"-Developing-Unicode-aware-applications-in-Python.pdf>`_ discuss questions of"
1018+
" character encodings as well as how to internationalize and localize an "
1019+
"application. These slides cover Python 2.x only."
10211020
msgstr ""
10221021
"`Marc-André Lemburg 演示的PDF 幻灯片“在 Python 中编写支持 Unicode 的应用程序” "
10231022
"<https://downloads.egenix.com/python/LSM2005-Developing-Unicode-aware-"

‎library/email.compat32-message.po‎

Lines changed: 34 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -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."
330330
msgstr ""
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`."
375375
msgstr ""
376376
"将载荷的字符集设为 *charset*，它可以是 :class:`~email.charset.Charset` 实例 (参见 "
377377
":mod:`email.charset`)、字符集名称字符串或 ``None``。 如果是字符串，它将被转换为一个 "
@@ -382,26 +382,26 @@ msgstr ""
382382
msgid ""
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."
396396
msgstr ""
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
407407
msgid ""
@@ -613,11 +613,11 @@ msgstr ""
613613
#: ../../library/email.compat32-message.rst:431
614614
msgid ""
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."
621621
msgstr ""
622622
"返回消息的内容类型。 返回的字符串会强制转换为 :mimetype:`maintype/subtype` 的全小写形式。 如果消息中没有 "
623623
":mailheader:`Content-Type` 标头则将返回由 :meth:`get_default_type` 给出的默认类型。 因为根据 "
@@ -667,8 +667,8 @@ msgstr ""
667667
msgid ""
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."
672672
msgstr ""
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
692692
msgid ""
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`."
696696
msgstr ""
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``)."
716716
msgstr ""
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
721721
msgid ""
@@ -884,8 +884,8 @@ msgid ""
884884
"has no :mailheader:`Content-Type` header."
885885
msgstr ""
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
891891
msgid ""

‎library/email.headerregistry.po‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -407,8 +407,8 @@ msgstr "一个将形参名映射到形参值的字典。"
407407

408408
#: ../../library/email.headerregistry.rst:275
409409
msgid ""
410-
"A :class:`ParameterizedMIMEHeader` class that handles the "
411-
":mailheader:`Content-Type` header."
410+
"A :class:`ParameterizedMIMEHeader` class that handles the :mailheader"
411+
":`Content-Type` header."
412412
msgstr ""
413413
"处理 :mailheader:`Content-Type` 标头的 :class:`ParameterizedMIMEHeader` 类。"
414414

@@ -418,8 +418,8 @@ msgstr "``maintype/subtype`` 形式的内容类型字符串。"
418418

419419
#: ../../library/email.headerregistry.rst:289
420420
msgid ""
421-
"A :class:`ParameterizedMIMEHeader` class that handles the "
422-
":mailheader:`Content-Disposition` header."
421+
"A :class:`ParameterizedMIMEHeader` class that handles the :mailheader"
422+
":`Content-Disposition` header."
423423
msgstr ""
424424
"处理 :mailheader:`Content-Disposition` 标头的 :class:`ParameterizedMIMEHeader` 类。"
425425

‎library/email.message.po‎

Lines changed: 20 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -451,9 +451,9 @@ msgid ""
451451
" If the :mailheader:`Content-Type` header is invalid, return "
452452
"``text/plain``."
453453
msgstr ""
454-
"返回信息的内容类型，其形如 :mimetype:`maintype/subtype` ，强制全小写。如果信息的 "
455-
":mailheader:`Content-Type` 头字段不存在则返回 :meth:`get_default_type` 的返回值；如果信息的 "
456-
":mailheader:`Content-Type` 头字段无效则返回 ``text/plain`` 。"
454+
"返回信息的内容类型，其形如 :mimetype:`maintype/subtype` ，强制全小写。如果信息的 :mailheader"
455+
":`Content-Type` 头字段不存在则返回 :meth:`get_default_type` 的返回值；如果信息的 :mailheader"
456+
":`Content-Type` 头字段无效则返回 ``text/plain`` 。"
457457

458458
#: ../../library/email.message.rst:317
459459
msgid ""
@@ -467,9 +467,8 @@ msgid ""
467467
msgstr ""
468468
"（根据 :rfc:`2045` 所述，信息永远都有一个默认类型，所以 :meth:`get_content_type` 一定会返回一个值。 "
469469
":rfc:`2045` 定义信息的默认类型为 :mimetype:`text/plain` 或 :mimetype:`message/rfc822` "
470-
"，其中后者仅出现在消息头位于一个 :mimetype:`multipart/digest` 容器中的场合中。如果消息头的 "
471-
":mailheader:`Content-Type` 字段所指定的类型是无效的， :rfc:`2045` 令其默认类型为 "
472-
":mimetype:`text/plain` 。）"
470+
"，其中后者仅出现在消息头位于一个 :mimetype:`multipart/digest` 容器中的场合中。如果消息头的 :mailheader"
471+
":`Content-Type` 字段所指定的类型是无效的， :rfc:`2045` 令其默认类型为 :mimetype:`text/plain` 。）"
473472

474473
#: ../../library/email.message.rst:328
475474
msgid ""
@@ -502,10 +501,10 @@ msgstr ""
502501
msgid ""
503502
"Set the default content type. *ctype* should either be "
504503
":mimetype:`text/plain` or :mimetype:`message/rfc822`, although this is not "
505-
"enforced. The default content type is not stored in the "
506-
":mailheader:`Content-Type` header, so it only affects the return value of "
507-
"the ``get_content_type`` methods when no :mailheader:`Content-Type` header "
508-
"is present in the message."
504+
"enforced. The default content type is not stored in the :mailheader"
505+
":`Content-Type` header, so it only affects the return value of the "
506+
"``get_content_type`` methods when no :mailheader:`Content-Type` header is "
507+
"present in the message."
509508
msgstr ""
510509
"设置默认的内容类型。 尽管并非强制，但是 *ctype* 仍应当是 :mimetype:`text/plain` 或 "
511510
":mimetype:`message/rfc822` 二者取一。默认内容类型并不存储在 :mailheader:`Content-Type` "
@@ -609,8 +608,8 @@ msgid ""
609608
"has no :mailheader:`Content-Type` header."
610609
msgstr ""
611610
"将 :mailheader:`Content-Type` 头字段的 ``boundary`` 参数设置为 *boundary* 。 "
612-
":meth:`set_boundary` 方法永远都会在必要的时候为 *boundary* 添加引号。如果信息对象中没有 "
613-
":mailheader:`Content-Type` 头字段，抛出 :exc:`~email.errors.HeaderParseError` 异常。"
611+
":meth:`set_boundary` 方法永远都会在必要的时候为 *boundary* 添加引号。如果信息对象中没有 :mailheader"
612+
":`Content-Type` 头字段，抛出 :exc:`~email.errors.HeaderParseError` 异常。"
614613

615614
#: ../../library/email.message.rst:424
616615
msgid ""
@@ -759,8 +758,8 @@ msgid ""
759758
"it when looking for candidate matches. Otherwise consider only the first "
760759
"(default root) part of the ``multipart/related``."
761760
msgstr ""
762-
"当遇到一个 ``multipart/related`` 时，将检查 ``start`` 形参并且如果找到了一个匹配 "
763-
":mailheader:`Content-ID` 的部分，在查找候选匹配时只考虑它。 在其他情况下则只考虑 ``multipart/related`` "
761+
"当遇到一个 ``multipart/related`` 时，将检查 ``start`` 形参并且如果找到了一个匹配 :mailheader"
762+
":`Content-ID` 的部分，在查找候选匹配时只考虑它。 在其他情况下则只考虑 ``multipart/related`` "
764763
"的第一个（默认的根）部分。"
765764

766765
#: ../../library/email.message.rst:557
@@ -792,9 +791,9 @@ msgstr ""
792791
"注: (1) 对于大多数应用来说有意义的 *preferencelist* 组合仅有 ``('plain',)``, ``('html', "
793792
"'plain')`` 以及默认的 ``('related', 'html', 'plain')``。 (2) 由于匹配是从调用 ``get_body``"
794793
" 的对象开始的，因此在 ``multipart/related`` 上调用 ``get_body`` 将返回对象本身，除非 "
795-
"*preferencelist* 具有非默认值。 (3) 未指定 :mailheader:`Content-Type` 或者 "
796-
":mailheader:`Content-Type` 标头无效的消息（或消息部分）将被当作具有 ``text/plain`` 类型来处理，这有时可能导致"
797-
" ``get_body`` 返回非预期的结果。"
794+
"*preferencelist* 具有非默认值。 (3) 未指定 :mailheader:`Content-Type` 或者 :mailheader"
795+
":`Content-Type` 标头无效的消息（或消息部分）将被当作具有 ``text/plain`` 类型来处理，这有时可能导致 "
796+
"``get_body`` 返回非预期的结果。"
798797

799798
#: ../../library/email.message.rst:577
800799
msgid ""
@@ -806,8 +805,8 @@ msgid ""
806805
" parts. When applied directly to a ``multipart/related``, return an "
807806
"iterator over the all the related parts except the root part (ie: the part "
808807
"pointed to by the ``start`` parameter, or the first part if there is no "
809-
"``start`` parameter or the ``start`` parameter doesn't match the "
810-
":mailheader:`Content-ID` of any of the parts). When applied directly to a "
808+
"``start`` parameter or the ``start`` parameter doesn't match the :mailheader"
809+
":`Content-ID` of any of the parts). When applied directly to a "
811810
"``multipart/alternative`` or a non-``multipart``, return an empty iterator."
812811
msgstr ""
813812
"返回包含所有不是候选 \"body\" 部分的消息的直接子部分的迭代器。 也就是说，跳过首次出现的每个 ``text/plain``, "
@@ -909,8 +908,8 @@ msgstr ""
909908
":meth:`~email.message.Message.attach` 到 ``multipart``。 如果消息为非 "
910909
"``multipart``，则先调用 :meth:`make_related` 然后再继续上述步骤。 如果消息为任何其他类型的 "
911910
"``multipart``，则会引发 :exc:`TypeError`。 如果未指定 *content_manager*，则使用当前 "
912-
":mod:`~email.policy` 所指定的 ``content_manager``。 如果添加的部分没有 "
913-
":mailheader:`Content-Disposition` 标头，则会添加一个值为 ``inline`` 的标头。"
911+
":mod:`~email.policy` 所指定的 ``content_manager``。 如果添加的部分没有 :mailheader"
912+
":`Content-Disposition` 标头，则会添加一个值为 ``inline`` 的标头。"
914913

915914
#: ../../library/email.message.rst:661
916915
msgid ""

0 commit comments

Comments
 (0)