Sync with cpython and translate new/fuzzy entries from upstream sync by mattwang44 · Pull Request #1239 · python/python-docs-zh-tw

mattwang44 · 2026-07-05T14:05:07Z

No description provided.

mattwang44 · 2026-07-05T14:11:32Z

 #: ../../library/curses.panel.rst:51
 msgid "Panel objects"
-msgstr ""
+msgstr "面板物件"


因為真的是有 Panel object 所以不翻譯 Panel 會不會比較好？

不翻一票

Addresses review feedback on PR python#1239: several c-api/*.po translations rendered the "steals a reference" idiom as plain-text 「竊取」 instead of linking it to the glossary via :term:`竊取 <steal>`, and one entry had stray spacing around the markup. Applies the same fix to every remaining occurrence across c-api/bytes.po, dict.po, exceptions.po, gen.po, list.po, module.po, sequence.po, tuple.po, and threads.po. Co-authored-by: Claude <noreply@anthropic.com>

CI builds with sphinx-build --fail-on-warning, so the 56 warnings from the previous push were hard failures. Root cause: two escaping bugs introduced across the large tkinter.po translation batch. 1. A role/literal close (`` ` `` or ``` `` ```) directly followed by a full-width （ with no `\ ` separator confuses docutils' inline markup boundary detection, which can silently swallow or merge adjacent role references in the same paragraph -- surfacing as Sphinx's i18n.inconsistent_references warnings (dropped or merged :class:/ :meth:/:attr:/:term: references) in tkinter.po, tkinter.ttk.po, http.cookiejar.po, and c-api/unicode.po. 2. The same applies to *emphasis*（ with no space/separator before the parenthesis, which docutils reports as "Inline emphasis start-string without end-string" since the closing `*` isn't followed by a recognized boundary character. Fixed by adding the space that's already the established convention elsewhere in this file. Also fixes a review comment on PR python#1239: removes a stray literal space that rendered as a visible gap between adjacent Chinese text and a role's Chinese display text in c-api/dict.po. Co-authored-by: Claude <noreply@anthropic.com>

mattwang44 · 2026-07-05T16:35:59Z

+"在執行期，產生器運算式會被求值為一個 :term:`generator iterator`\\ （產生器疊"
+"代器），它會產生和對應的 list comprehension 相同的值： ::"


Suggested change

"在執行期，產生器運算式會被求值為一個 :term:`generator iterator`\\ （產生器疊"

"代器），它會產生和對應的 list comprehension 相同的值： ::"

"在 runtime，產生器運算式會被求值為一個 :term:`產生器疊代器 "

"<generator iterator>`，它會產生和對應的串列綜合運算相同的值： ::"

mattwang44 · 2026-07-05T16:36:19Z

 "arguments. See the :ref:`Calls section <calls>` for details. For example::"
 msgstr ""
+"當產生器運算式是唯一的位置引數，且沒有關鍵字引數時，呼叫中可以省略外層的括"
+"號。詳情請參閱\\ :ref:`Calls 章節 <calls>`。舉例來說： ::"


Suggested change

"號。詳情請參閱\\ :ref:`Calls 章節 <calls>`。舉例來說： ::"

"號。詳情請參閱 :ref:`Calls 章節 <calls>`。舉例來說： ::"

mattwang44 · 2026-07-05T16:40:45Z

 "`3501`, section 7.4.2), so production code should inspect the whole response "
 "rather than rely on ``data[0][1]``."
 msgstr ""
+"一個 ``FETCH`` 回應可能會包含額外或未經請求的資料（參閱\\ :rfc:`3501`\\ 第 "


Suggested change

"一個 ``FETCH`` 回應可能會包含額外或未經請求的資料（參閱\\ :rfc:`3501`\\ 第 "

"一個 ``FETCH`` 回應可能會包含額外或未經請求的資料（參閱 :rfc:`3501` 第 "

mattwang44 · 2026-07-05T16:43:54Z

+"非同步地在執行緒中引發例外。*id* 引數為目標執行緒的執行緒 id；*exc* 為要引發"
+"的例外物件。此函式不會\\ :term:`竊取 <steal>`\\ 任何對 *exc* 的參照。為了防止"
+"不當誤用，你必須自行編寫 C 擴充來呼叫此函式。呼叫時必須具有\\ :term:`已附加的"
+"執行緒狀態 <attached thread state>`\\ 。回傳被修改的執行緒狀態數量；通常為"


Suggested change

"執行緒狀態 <attached thread state>`\\ 。回傳被修改的執行緒狀態數量；通常為"

"執行緒狀態 <attached thread state>`。回傳被修改的執行緒狀態數量；通常為"

mattwang44 · 2026-07-07T01:36:12Z

 "define ``__hash__ = Set._hash``."
 msgstr ""
+":class:`Set` mixin 提供了 :meth:`!_hash` 方法來計算集合的雜湊值；然而，由於並"
+"非所有集合都是 :term:`hashable` 或不可變的，因此並未定義 :meth:`~object."


Suggested change

"非所有集合都是 :term:`hashable` 或不可變的，因此並未定義 :meth:`~object."

"非所有集合都是\\ :term:`可雜湊的 <hashable>`\\ 或不可變的，因此並未定義 :meth:`~object."

mattwang44 · 2026-07-07T01:38:58Z

make :term:`term` to be :term:`中文翻譯 <term>`

Addresses review feedback on PR python#1239: several c-api/*.po translations rendered the "steals a reference" idiom as plain-text 「竊取」 instead of linking it to the glossary via :term:`竊取 <steal>`, and one entry had stray spacing around the markup. Applies the same fix to every remaining occurrence across c-api/bytes.po, dict.po, exceptions.po, gen.po, list.po, module.po, sequence.po, tuple.po, and threads.po. Co-authored-by: Claude <noreply@anthropic.com>

CI builds with sphinx-build --fail-on-warning, so the 56 warnings from the previous push were hard failures. Root cause: two escaping bugs introduced across the large tkinter.po translation batch. 1. A role/literal close (`` ` `` or ``` `` ```) directly followed by a full-width （ with no `\ ` separator confuses docutils' inline markup boundary detection, which can silently swallow or merge adjacent role references in the same paragraph -- surfacing as Sphinx's i18n.inconsistent_references warnings (dropped or merged :class:/ :meth:/:attr:/:term: references) in tkinter.po, tkinter.ttk.po, http.cookiejar.po, and c-api/unicode.po. 2. The same applies to *emphasis*（ with no space/separator before the parenthesis, which docutils reports as "Inline emphasis start-string without end-string" since the closing `*` isn't followed by a recognized boundary character. Fixed by adding the space that's already the established convention elsewhere in this file. Also fixes a review comment on PR python#1239: removes a stray literal space that rendered as a visible gap between adjacent Chinese text and a role's Chinese display text in c-api/dict.po. Co-authored-by: Claude <noreply@anthropic.com>

Addresses review feedback on PR python#1239: several c-api/*.po translations rendered the "steals a reference" idiom as plain-text 「竊取」 instead of linking it to the glossary via :term:`竊取 <steal>`, and one entry had stray spacing around the markup. Applies the same fix to every remaining occurrence across c-api/bytes.po, dict.po, exceptions.po, gen.po, list.po, module.po, sequence.po, tuple.po, and threads.po. Co-authored-by: Claude <noreply@anthropic.com>

CI builds with sphinx-build --fail-on-warning, so the 56 warnings from the previous push were hard failures. Root cause: two escaping bugs introduced across the large tkinter.po translation batch. 1. A role/literal close (`` ` `` or ``` `` ```) directly followed by a full-width （ with no `\ ` separator confuses docutils' inline markup boundary detection, which can silently swallow or merge adjacent role references in the same paragraph -- surfacing as Sphinx's i18n.inconsistent_references warnings (dropped or merged :class:/ :meth:/:attr:/:term: references) in tkinter.po, tkinter.ttk.po, http.cookiejar.po, and c-api/unicode.po. 2. The same applies to *emphasis*（ with no space/separator before the parenthesis, which docutils reports as "Inline emphasis start-string without end-string" since the closing `*` isn't followed by a recognized boundary character. Fixed by adding the space that's already the established convention elsewhere in this file. Also fixes a review comment on PR python#1239: removes a stray literal space that rendered as a visible gap between adjacent Chinese text and a role's Chinese display text in c-api/dict.po. Co-authored-by: Claude <noreply@anthropic.com>

Addresses review feedback on PR python#1239: several c-api/*.po translations rendered the "steals a reference" idiom as plain-text 「竊取」 instead of linking it to the glossary via :term:`竊取 <steal>`, and one entry had stray spacing around the markup. Applies the same fix to every remaining occurrence across c-api/bytes.po, dict.po, exceptions.po, gen.po, list.po, module.po, sequence.po, tuple.po, and threads.po. Co-authored-by: Claude <noreply@anthropic.com>

CI builds with sphinx-build --fail-on-warning, so the 56 warnings from the previous push were hard failures. Root cause: two escaping bugs introduced across the large tkinter.po translation batch. 1. A role/literal close (`` ` `` or ``` `` ```) directly followed by a full-width （ with no `\ ` separator confuses docutils' inline markup boundary detection, which can silently swallow or merge adjacent role references in the same paragraph -- surfacing as Sphinx's i18n.inconsistent_references warnings (dropped or merged :class:/ :meth:/:attr:/:term: references) in tkinter.po, tkinter.ttk.po, http.cookiejar.po, and c-api/unicode.po. 2. The same applies to *emphasis*（ with no space/separator before the parenthesis, which docutils reports as "Inline emphasis start-string without end-string" since the closing `*` isn't followed by a recognized boundary character. Fixed by adding the space that's already the established convention elsewhere in this file. Also fixes a review comment on PR python#1239: removes a stray literal space that rendered as a visible gap between adjacent Chinese text and a role's Chinese display text in c-api/dict.po. Co-authored-by: Claude <noreply@anthropic.com>

Rebased onto upstream's new sync commits (cpython 6337bfd4..37a5c690) and translated the resulting new/fuzzy backlog: 96 entries across 22 files (c-api/{exceptions,frame,perfmaps,typeobj,veryhigh}.po, library/{ast, calendar,compression.zstd,concurrent.interpreters,difflib,filecmp, functions,getopt,inspect,lzma,mimetypes,secrets,sys,uu}.po, howto/logging-cookbook.po, using/windows.po, whatsnew/3.14.po). Also addressed outstanding review feedback on PR python#1239: - reference/expressions.po: reworded the generator-iterator/list- comprehension sentence per reviewer suggestion, and dropped unneeded backslash escaping before the Calls-section role reference. - library/imaplib.po: dropped unneeded backslash escaping around the :rfc:`3501` reference. - library/collections.abc.po: use :term:`可雜湊的 <hashable>` instead of the bare English :term:`hashable` role, per reviewer guidance to give glossary terms a Chinese display form. - whatsnew/3.14.po: fixed a role-directly-touching-full-width-paren RST escaping bug introduced by today's translation. - reference/expressions.po: fixed a stray single-backtick (default-role) lint warning in a pre-existing code comment. Co-authored-by: Claude <noreply@anthropic.com>