[po] auto sync

github-actions[bot] · github-actions[bot] · commit e7969278a831 · 2021-09-12T14:04:32.000Z
diff --git a/c-api/buffer.po b/c-api/buffer.po
@@ -439,6 +439,8 @@ msgid ""
 "exporter MAY provide either a read-only or writable buffer, but the choice "
 "MUST be consistent for all consumers."
 msgstr ""
+"控制 :c:member:`~Py_buffer.readonly` 字段。如果设置了，输出程序 *必须* "
+"提供一个可写的缓冲区，否则报告失败。若未设置，输出程序 *可以* 提供只读或可写的缓冲区，但对所有消费者程序 *必须* 保持一致。"
 
 #: ../../c-api/buffer.rst:250
 msgid ""
@@ -454,6 +456,8 @@ msgid ""
 ":c:macro:`PyBUF_WRITABLE` can be used as a stand-alone flag to request a "
 "simple writable buffer."
 msgstr ""
+":c:macro:`PyBUF_WRITABLE` 可以和下一节的所有标志联用。由于 :c:macro:`PyBUF_SIMPLE` 定义为 0，所以 "
+":c:macro:`PyBUF_WRITABLE` 可以作为一个独立的标志，用于请求一个简单的可写缓冲区。"
 
 #: ../../c-api/buffer.rst:258
 msgid ""
@@ -577,7 +581,7 @@ msgstr "所有可能的请求都由上一节中某些标志的组合完全定义
 msgid ""
 "In the following table *U* stands for undefined contiguity. The consumer "
 "would have to call :c:func:`PyBuffer_IsContiguous` to determine contiguity."
-msgstr ""
+msgstr "在下表中，*U* 代表连续性未定义。消费者程序必须调用  :c:func:`PyBuffer_IsContiguous` 以确定连续性。"
 
 #: ../../c-api/buffer.rst:321
 msgid "readonly"
@@ -617,6 +621,9 @@ msgid ""
 ":c:member:`~Py_buffer.itemsize`, :c:member:`~Py_buffer.ndim`, "
 ":c:member:`~Py_buffer.shape` and :c:member:`~Py_buffer.strides`."
 msgstr ""
+"NumPy 风格数组的逻辑结构由 :c:member:`~Py_buffer.itemsize` 、 "
+":c:member:`~Py_buffer.ndim` 、 :c:member:`~Py_buffer.shape` 和 "
+":c:member:`~Py_buffer.strides` 定义。"
 
 #: ../../c-api/buffer.rst:350
 msgid ""
@@ -626,20 +633,25 @@ msgid ""
 ":c:member:`~Py_buffer.shape` and :c:member:`~Py_buffer.strides` are "
 "``NULL``."
 msgstr ""
+"如果 ``ndim == 0`` ， :c:member:`~Py_buffer.buf` 指向的内存位置被解释为大小为 "
+":c:member:`~Py_buffer.itemsize` 的标量。这时， :c:member:`~Py_buffer.shape` 和 "
+":c:member:`~Py_buffer.strides` 都为 ``NULL``。"
 
 #: ../../c-api/buffer.rst:354
 msgid ""
 "If :c:member:`~Py_buffer.strides` is ``NULL``, the array is interpreted as a"
 " standard n-dimensional C-array. Otherwise, the consumer must access an "
 "n-dimensional array as follows:"
 msgstr ""
+"如果 :c:member:`~Py_buffer.strides` 为 ``NULL``，则数组将被解释为一个标准的 n 维 C "
+"语言数组。否则，消费者程序必须按如下方式访问 n 维数组："
 
 #: ../../c-api/buffer.rst:364
 msgid ""
 "As noted above, :c:member:`~Py_buffer.buf` can point to any location within "
 "the actual memory block. An exporter can check the validity of a buffer with"
 " this function:"
-msgstr ""
+msgstr "如上所述，:c:member:`~Py_buffer.buf` 可以指向实际内存块中的任意位置。输出者程序可以用该函数检查缓冲区的有效性。"
 
 #: ../../c-api/buffer.rst:398
 msgid "PIL-style: shape, strides and suboffsets"
@@ -680,6 +692,8 @@ msgid ""
 "``1`` is returned, it doesn't guarantee that :c:func:`PyObject_GetBuffer` "
 "will succeed.  This function always succeeds."
 msgstr ""
+"如果 *obj* 支持缓冲区接口，则返回 ``1``，否则返回 ``0``。 返回 ``1`` 时不保证 "
+":c:func:`PyObject_GetBuffer` 一定成功。本函数一定调用成功。"
 
 #: ../../c-api/buffer.rst:439
 msgid ""
@@ -705,6 +719,9 @@ msgid ""
 ":c:func:`free`. Thus, after the consumer is done with the buffer, "
 ":c:func:`PyBuffer_Release` must be called exactly once."
 msgstr ""
+":c:func:`PyObject_GetBuffer` 必须与 :c:func:`PyBuffer_Release` 同时调用成功，类似于 "
+":c:func:`malloc` 和 :c:func:`free`。因此，消费者程序用完缓冲区后， :c:func:`PyBuffer_Release`"
+" 必须保证被调用一次。"
 
 #: ../../c-api/buffer.rst:457
 msgid ""
