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

Skip to content

Commit 6c36411

Browse files
github-actions[bot]github-actions[bot]
committed
[po] auto sync
1 parent 777f7b8 commit 6c36411

32 files changed

Lines changed: 144 additions & 136 deletions

‎c-api/index.po‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,9 +29,9 @@ msgstr "Python/C API 参考手册"
2929
#: ../../c-api/index.rst:7
3030
msgid ""
3131
"This manual documents the API used by C and C++ programmers who want to "
32-
"write extension modules or embed Python. It is a companion to :ref"
33-
":`extending-index`, which describes the general principles of extension "
32+
"write extension modules or embed Python. It is a companion to "
33+
":ref:`extending-index`, which describes the general principles of extension "
3434
"writing but does not document the API functions in detail."
3535
msgstr ""
36-
"本手册描述了希望编写扩展模块并将 Python 解释器嵌入其应用程序中的 C 和 C++ 程序员可用的 API。同时可以参阅 :ref"
37-
":`extending-index` ，其中描述了扩展编写的一般原则，但没有详细描述 API 函数。"
36+
"本手册描述了希望编写扩展模块并将 Python 解释器嵌入其应用程序中的 C 和 C++ 程序员可用的 API。同时可以参阅 "
37+
":ref:`extending-index` ，其中描述了扩展编写的一般原则，但没有详细描述 API 函数。"

‎faq/library.po‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -292,12 +292,12 @@ msgstr "怎样用 docstring 创建文档？"
292292
msgid ""
293293
"The :mod:`pydoc` module can create HTML from the doc strings in your Python "
294294
"source code. An alternative for creating API documentation purely from "
295-
"docstrings is `epydoc <http://epydoc.sourceforge.net/>`_. `Sphinx <http"
296-
"://sphinx-doc.org>`_ can also include docstring content."
295+
"docstrings is `epydoc <http://epydoc.sourceforge.net/>`_. `Sphinx "
296+
"<http://sphinx-doc.org>`_ can also include docstring content."
297297
msgstr ""
298298
":mod:`pydoc` 模块可以用 Python 源码中的 docstring 创建 HTML 文件。也可以使用 `epydoc "
299-
"<http://epydoc.sourceforge.net/>`_ 来只通过 docstring 创建 API 文档。`Sphinx <http"
300-
"://sphinx-doc.org>`_ 也可以引入 docstring 的内容。"
299+
"<http://epydoc.sourceforge.net/>`_ 来只通过 docstring 创建 API 文档。`Sphinx "
300+
"<http://sphinx-doc.org>`_ 也可以引入 docstring 的内容。"
301301

302302
#: ../../faq/library.rst:191
303303
msgid "How do I get a single keypress at a time?"

‎glossary.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2072,8 +2072,8 @@ msgstr ""
20722072

20732073
#: ../../glossary.rst:1053
20742074
msgid ""
2075-
"See also :term:`binary file` for a file object able to read and write :term"
2076-
":`bytes-like objects <bytes-like object>`."
2075+
"See also :term:`binary file` for a file object able to read and write "
2076+
":term:`bytes-like objects <bytes-like object>`."
20772077
msgstr ""
20782078
"另请参看 :term:`binary file` 了解能够读写 :term:`字节类对象 <bytes-like object>` 的文件对象。"
20792079

‎howto/sockets.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -144,8 +144,8 @@ msgid ""
144144
msgstr ""
145145
"有几件事需要注意：我们使用了 ``socket.gethostname()``，所以套接字将外网可见。如果我们使用的是 "
146146
"``s.bind(('localhost', 80))`` 或者 ``s.bind(('127.0.0.1', "
147-
"80))``，也会得到一个「服务端」套接字，但是后者只在同一机器上可见。``s.bind(('', 80))`` "
148-
"则指定套接字可以被机器上的任何地址碰巧连接"
147+
"80))``，也会得到一个「服务端」套接字，但是后者只在同一机器上可见。``s.bind(('', "
148+
"80))`` 则指定套接字可以被机器上的任何地址碰巧连接"
149149

150150
#: ../../howto/sockets.rst:87
151151
msgid ""

‎howto/unicode.po‎

Lines changed: 7 additions & 6 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 库参考文档 :ref"
406-
":`standard-encodings`。 一些编码格式有多个名称，比如 ``'latin-1'``、``'iso_8859_1'`` 和 "
405+
"编码格式以包含编码格式名称的字符串来指明。 Python 有大约 100 种不同的编码格式；清单详见 Python 库参考文档 "
406+
":ref:`standard-encodings`。 一些编码格式有多个名称，比如 ``'latin-1'``、``'iso_8859_1'`` 和 "
407407
"``'8859`` 都是指同一种编码。"
408408

409409
#: ../../howto/unicode.rst:253
@@ -1013,10 +1013,11 @@ 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\" <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."
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."
10201021
msgstr ""
10211022
"`Marc-André Lemburg 演示的PDF 幻灯片“在 Python 中编写支持 Unicode 的应用程序” "
10221023
"<https://downloads.egenix.com/python/LSM2005-Developing-Unicode-aware-"

‎installing/index.po‎

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -157,8 +157,8 @@ msgid ""
157157
"`Python Packaging User Guide: Creating and using virtual environments "
158158
"<https://packaging.python.org/installing/#creating-virtual-environments>`__"
159159
msgstr ""
160-
"`Python 软件包用户指南：创建和使用虚拟环境 <https://packaging.python.org/installing"
161-
"/#creating-virtual-environments>`__"
160+
"`Python 软件包用户指南：创建和使用虚拟环境 "
161+
"<https://packaging.python.org/installing/#creating-virtual-environments>`__"
162162

163163
#: ../../installing/index.rst:80
164164
msgid "Basic usage"
@@ -257,8 +257,9 @@ msgid ""
257257
"<https://packaging.python.org/installing/#requirements-for-installing-"
258258
"packages>`__"
259259
msgstr ""
260-
"`Python 软件包用户指南：安装软件包的前提要求 <https://packaging.python.org/installing"
261-
"/#requirements-for-installing-packages>`__"
260+
"`Python 软件包用户指南：安装软件包的前提要求 "
261+
"<https://packaging.python.org/installing/#requirements-for-installing-"
262+
"packages>`__"
262263

263264
#: ../../installing/index.rst:147
264265
msgid "... install packages just for the current user?"

‎library/codecs.po‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -68,8 +68,8 @@ msgid ""
6868
"information on codec error handling."
6969
msgstr ""
7070
"可以给定 *Errors* 以设置所需要的错误处理方案。 默认的错误处理方案 ``'strict'`` 表示编码错误将引发 "
71-
":exc:`ValueError` (或更特定编解码器相关的子类，例如 :exc:`UnicodeEncodeError`)。 请参阅 :ref"
72-
":`codec-base-classes` 了解有关编解码器错误处理的更多信息。"
71+
":exc:`ValueError` (或更特定编解码器相关的子类，例如 :exc:`UnicodeEncodeError`)。 请参阅 "
72+
":ref:`codec-base-classes` 了解有关编解码器错误处理的更多信息。"
7373

7474
#: ../../library/codecs.rst:48
7575
msgid "Decodes *obj* using the codec registered for *encoding*."
@@ -84,8 +84,8 @@ msgid ""
8484
"information on codec error handling."
8585
msgstr ""
8686
"可以给定 *Errors* 以设置所需要的错误处理方案。 默认的错误处理方案 ``'strict'`` 表示编码错误将引发 "
87-
":exc:`ValueError` (或更特定编解码器相关的子类，例如 :exc:`UnicodeDecodeError`)。 请参阅 :ref"
88-
":`codec-base-classes` 了解有关编解码器错误处理的更多信息。"
87+
":exc:`ValueError` (或更特定编解码器相关的子类，例如 :exc:`UnicodeDecodeError`)。 请参阅 "
88+
":ref:`codec-base-classes` 了解有关编解码器错误处理的更多信息。"
8989

9090
#: ../../library/codecs.rst:56
9191
msgid "The full details for each codec can also be looked up directly:"
@@ -792,8 +792,8 @@ msgid ""
792792
"schemes by providing the *errors* keyword argument. See :ref:`error-"
793793
"handlers` for possible values."
794794
msgstr ""
795-
":class:`IncrementalEncoder` 可以通过提供 *errors* 关键字参数来实现不同的错误处理方案。 可用的值请参阅 :ref"
796-
":`error-handlers`。"
795+
":class:`IncrementalEncoder` 可以通过提供 *errors* 关键字参数来实现不同的错误处理方案。 可用的值请参阅 "
796+
":ref:`error-handlers`。"
797797

798798
#: ../../library/codecs.rst:545
799799
msgid ""
@@ -872,8 +872,8 @@ msgid ""
872872
"schemes by providing the *errors* keyword argument. See :ref:`error-"
873873
"handlers` for possible values."
874874
msgstr ""
875-
":class:`IncrementalDecoder` 可以通过提供 *errors* 关键字参数来实现不同的错误处理方案。 可用的值请参阅 :ref"
876-
":`error-handlers`。"
875+
":class:`IncrementalDecoder` 可以通过提供 *errors* 关键字参数来实现不同的错误处理方案。 可用的值请参阅 "
876+
":ref:`error-handlers`。"
877877

878878
#: ../../library/codecs.rst:602
879879
msgid ""
@@ -2788,8 +2788,8 @@ msgid ""
27882788
"Unicode before presenting them to the user."
27892789
msgstr ""
27902790
"这些 RFC 共同定义了一个在域名中支持非 ASCII 字符的协议。 一个包含非 ASCII 字符的域名 (例如 "
2791-
"``www.Alliancefrançaise.nu``) 会被转换为兼容 ASCII 的编码格式 (简称 ACE，例如 ``www.xn"
2792-
"--alliancefranaise-npb.nu``)。 随后此域名的 ACE 形式可以用于所有由于特定协议而不允许使用任意字符的场合，例如 DNS "
2791+
"``www.Alliancefrançaise.nu``) 会被转换为兼容 ASCII 的编码格式 (简称 ACE，例如 ``www.xn--"
2792+
"alliancefranaise-npb.nu``)。 随后此域名的 ACE 形式可以用于所有由于特定协议而不允许使用任意字符的场合，例如 DNS "
27932793
"查询，HTTP :mailheader:`Host` 字段等等。 此转换是在应用中进行的；如有可能将对用户可见：应用应当透明地将 Unicode "
27942794
"域名标签转换为线上的 IDNA，并在 ACE 标签被呈现给用户之前将其转换回 Unicode。"
27952795

‎library/csv.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -466,8 +466,8 @@ msgid ""
466466
" reader. It can take on any of the :const:`QUOTE_\\*` constants (see "
467467
"section :ref:`csv-contents`) and defaults to :const:`QUOTE_MINIMAL`."
468468
msgstr ""
469-
"控制 writer 何时生成引号，以及 reader 何时识别引号。该属性可以等于任何 :const:`QUOTE_\\*` 常量（参见 :ref"
470-
":`csv-contents` 段落），默认为 :const:`QUOTE_MINIMAL`。"
469+
"控制 writer 何时生成引号，以及 reader 何时识别引号。该属性可以等于任何 :const:`QUOTE_\\*` 常量（参见 "
470+
":ref:`csv-contents` 段落），默认为 :const:`QUOTE_MINIMAL`。"
471471

472472
#: ../../library/csv.rst:386
473473
msgid ""

‎library/email.contentmanager.po‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -317,11 +317,11 @@ msgstr "如果设置了 *cid*，则添加一个 :mailheader:`Content-ID` 标头
317317
#: ../../library/email.contentmanager.rst:185
318318
msgid ""
319319
"If *params* is specified, iterate its ``items`` method and use the resulting"
320-
" ``(key, value)`` pairs to set additional parameters on the :mailheader"
321-
":`Content-Type` header."
320+
" ``(key, value)`` pairs to set additional parameters on the "
321+
":mailheader:`Content-Type` header."
322322
msgstr ""
323-
"如果设置了 *params*，则迭代其 ``items`` 方法并使用输出的 ``(key, value)`` 结果对在 :mailheader"
324-
":`Content-Type` 标头上设置附加参数。"
323+
"如果设置了 *params*，则迭代其 ``items`` 方法并使用输出的 ``(key, value)`` 结果对在 "
324+
":mailheader:`Content-Type` 标头上设置附加参数。"
325325

326326
#: ../../library/email.contentmanager.rst:189
327327
msgid ""

‎library/email.generator.po‎

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -158,11 +158,11 @@ msgid ""
158158
"If the :mod:`~email.policy` option :attr:`~email.policy.Policy.cte_type` is "
159159
"``8bit`` (the default), copy any headers in the original parsed message that"
160160
" have not been modified to the output with any bytes with the high bit set "
161-
"reproduced as in the original, and preserve the non-ASCII :mailheader"
162-
":`Content-Transfer-Encoding` of any body parts that have them. If "
163-
"``cte_type`` is ``7bit``, convert the bytes with the high bit set as needed "
164-
"using an ASCII-compatible :mailheader:`Content-Transfer-Encoding`. That is, "
165-
"transform parts with non-ASCII :mailheader:`Content-Transfer-Encoding` "
161+
"reproduced as in the original, and preserve the non-ASCII "
162+
":mailheader:`Content-Transfer-Encoding` of any body parts that have them. If"
163+
" ``cte_type`` is ``7bit``, convert the bytes with the high bit set as needed"
164+
" using an ASCII-compatible :mailheader:`Content-Transfer-Encoding`. That is,"
165+
" transform parts with non-ASCII :mailheader:`Content-Transfer-Encoding` "
166166
"(:mailheader:`Content-Transfer-Encoding: 8bit`) to an ASCII compatible "
167167
":mailheader:`Content-Transfer-Encoding`, and encode RFC-invalid non-ASCII "
168168
"bytes in headers using the MIME ``unknown-8bit`` character set, thus "
@@ -173,9 +173,9 @@ msgstr ""
173173
"ASCII :mailheader:`Content-Transfer-Encoding`。 如果 ``cte_type`` 为 "
174174
"``7bit``，则会根据需要使用兼容 ASCII 的 :mailheader:`Content-Transfer-Encoding` "
175175
"来转换高比特位组字节数据。 也就是说，将具有非 ASCII :mailheader:`Content-Transfer-Encoding` "
176-
"(:mailheader:`Content-Transfer-Encoding: 8bit`) 的部分转换为兼容 ASCII 的 :mailheader"
177-
":`Content-Transfer-Encoding`，并使用 MIME ``unknown-8bit`` 字符集来编码标头中不符合 RFC 的非 "
178-
"ASCII 字节数据，以使其符合 RFC。"
176+
"(:mailheader:`Content-Transfer-Encoding: 8bit`) 的部分转换为兼容 ASCII 的 "
177+
":mailheader:`Content-Transfer-Encoding`，并使用 MIME ``unknown-8bit`` "
178+
"字符集来编码标头中不符合 RFC 的非 ASCII 字节数据，以使其符合 RFC。"
179179

180180
#: ../../library/email.generator.rst:100 ../../library/email.generator.rst:193
181181
msgid ""
@@ -232,11 +232,11 @@ msgstr ""
232232
msgid ""
233233
"Because strings cannot represent binary data, the :class:`Generator` class "
234234
"must convert any binary data in any message it flattens to an ASCII "
235-
"compatible format, by converting them to an ASCII compatible :mailheader"
236-
":`Content-Transfer_Encoding`. Using the terminology of the email RFCs, you "
237-
"can think of this as :class:`Generator` serializing to an I/O stream that is"
238-
" not \"8 bit clean\". In other words, most applications will want to be "
239-
"using :class:`BytesGenerator`, and not :class:`Generator`."
235+
"compatible format, by converting them to an ASCII compatible "
236+
":mailheader:`Content-Transfer_Encoding`. Using the terminology of the email"
237+
" RFCs, you can think of this as :class:`Generator` serializing to an I/O "
238+
"stream that is not \"8 bit clean\". In other words, most applications will "
239+
"want to be using :class:`BytesGenerator`, and not :class:`Generator`."
240240
msgstr ""
241241
"因为字符串无法表示二进制数据，:class:`Generator` 类必须将任何消息中扁平化的任何二进制数据转换为兼容 ASCII "
242242
"的格式，具体将其转换为兼容 ASCII 的 :mailheader:`Content-Transfer_Encoding`。 使用电子邮件 RFC "
@@ -266,12 +266,12 @@ msgid ""
266266
"If the :mod:`~email.policy` option :attr:`~email.policy.Policy.cte_type` is "
267267
"``8bit``, generate the message as if the option were set to ``7bit``. (This "
268268
"is required because strings cannot represent non-ASCII bytes.) Convert any "
269-
"bytes with the high bit set as needed using an ASCII-compatible :mailheader"
270-
":`Content-Transfer-Encoding`. That is, transform parts with non-ASCII "
271-
":mailheader:`Content-Transfer-Encoding` (:mailheader:`Content-Transfer-"
272-
"Encoding: 8bit`) to an ASCII compatible :mailheader:`Content-Transfer-"
273-
"Encoding`, and encode RFC-invalid non-ASCII bytes in headers using the MIME "
274-
"``unknown-8bit`` character set, thus rendering them RFC-compliant."
269+
"bytes with the high bit set as needed using an ASCII-compatible "
270+
":mailheader:`Content-Transfer-Encoding`. That is, transform parts with non-"
271+
"ASCII :mailheader:`Content-Transfer-Encoding` (:mailheader:`Content-"
272+
"Transfer-Encoding: 8bit`) to an ASCII compatible :mailheader:`Content-"
273+
"Transfer-Encoding`, and encode RFC-invalid non-ASCII bytes in headers using "
274+
"the MIME ``unknown-8bit`` character set, thus rendering them RFC-compliant."
275275
msgstr ""
276276
"如果 :mod:`~email.policy` 选项 :attr:`~email.policy.Policy.cte_type` 为 "
277277
"``8bit``，则视同选项被设为 ``7bit`` 来生成消息。 （这是必需的，因为字符串无法表示非 ASCII 字节数据。） 将使用兼容 ASCII"

0 commit comments

Comments
 (0)