Sync with cpython and translate new/fuzzy entries from upstream sync

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 #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>

Author: claude

c-api/exceptions.po

@@ -539,6 +539,8 @@ msgid ""
 "exception if one is set.  If *exc* is ``NULL``, just clear the existing "
 "exception."
 msgstr ""
+"將 *exc* 設定為目前正在引發的例外，如果已經設定了現有例外，則將其清除。如果 "
+"*exc* 為 ``NULL``，則只清除現有的例外。"
 
 #: ../../c-api/exceptions.rst:505
 msgid "*exc* must be a valid exception or ``NULL``."

c-api/frame.po

@@ -269,45 +269,48 @@ msgstr ""
 msgid ""
 "An array of executable kinds (executor types) for frames, used for internal "
 "debugging and tracing."
-msgstr ""
+msgstr "一個 frame 可執行種類（執行器類型）的陣列，用於內部除錯與追蹤。"
 
 #: ../../c-api/frame.rst:253
 msgid ""
 "Tools like debuggers and profilers can use this to identify the type of "
 "execution context associated with a frame (such as to filter out internal "
 "frames). The entries are indexed by the following constants:"
 msgstr ""
+"除錯器和分析器（profiler）等工具可以用這個陣列來識別與某個 frame 相關聯的執行"
+"環境類型（例如用來過濾掉內部 frame）。陣列項目由下列常數索引："
 
 #: ../../c-api/frame.rst:261
 msgid "Constant"
-msgstr ""
+msgstr "常數"
 
 #: ../../c-api/frame.rst:262
 msgid "Description"
-msgstr ""
+msgstr "描述"
 
 #: ../../c-api/frame.rst:264
 msgid ""
 "The frame is internal (For example: inlined) and should be skipped by tools."
-msgstr ""
+msgstr "此 frame 是內部的（例如：被行內化），工具應該略過它。"
 
 #: ../../c-api/frame.rst:266
 msgid "The frame corresponds to a standard Python function."
-msgstr ""
+msgstr "此 frame 對應到一個標準的 Python 函式。"
 
 #: ../../c-api/frame.rst:268
 msgid "The frame corresponds to a function defined in native code."
-msgstr ""
+msgstr "此 frame 對應到一個以原生程式碼定義的函式。"
 
 #: ../../c-api/frame.rst:270
 msgid "The frame corresponds to a method on a class instance."
-msgstr ""
+msgstr "此 frame 對應到一個類別實例上的方法。"
 
 #: ../../c-api/frame.rst:272
 msgid ""
 "However, Python's C API lacks a function to read the executable kind from a "
 "frame. Instead, use this recipe:"
 msgstr ""
+"然而，Python 的 C API 缺少可以從 frame 讀取可執行種類的函式。請改用以下方法："
 
 #: ../../c-api/frame.rst:275
 msgid ""
@@ -330,7 +333,25 @@ msgid ""
 "   return PyUnstable_EXECUTABLE_KIND_SKIP;\n"
 "}"
 msgstr ""
+"int\n"
+"get_executable_kind(PyFrameObject *frame)\n"
+"{\n"
+"   _PyInterpreterFrame *f = frame->f_frame;\n"
+"   PyObject *exec = PyStackRef_AsPyObjectBorrow(f->f_executable);\n"
+"\n"
+"   if (PyCode_Check(exec)) {\n"
+"      return PyUnstable_EXECUTABLE_KIND_PY_FUNCTION;\n"
+"   }\n"
+"   if (PyMethod_Check(exec)) {\n"
+"      return PyUnstable_EXECUTABLE_KIND_BUILTIN_FUNCTION;\n"
+"   }\n"
+"   if (Py_IS_TYPE(exec, &PyMethodDescr_Type)) {\n"
+"      return PyUnstable_EXECUTABLE_KIND_METHOD_DESCRIPTOR;\n"
+"   }\n"
+"\n"
+"   return PyUnstable_EXECUTABLE_KIND_SKIP;\n"
+"}"
 
 #: ../../c-api/frame.rst:301
 msgid "The number of entries in :c:data:`PyUnstable_ExecutableKinds`."
-msgstr ""
+msgstr ":c:data:`PyUnstable_ExecutableKinds` 中的項目數量。"

c-api/perfmaps.po

@@ -119,66 +119,75 @@ msgid ""
 "Open the ``/tmp/perf-$pid.map`` file and append the content of "
 "*parent_filename* to it."
 msgstr ""
+"打開 ``/tmp/perf-$pid.map`` 檔案，並將 *parent_filename* 的內容附加到其中。"
 
 #: ../../c-api/perfmaps.rst:57
 msgid ""
 "This function is available on all platforms but only generates output on "
 "platforms that support perf maps (currently only Linux). On other platforms, "
 "it does nothing."
 msgstr ""
+"此函式在所有平台上都可用，但只有在支援 perf map 的平台（目前僅限 Linux）上才"
+"會產生輸出。在其他平台上，它不會執行任何操作。"
 
 #: ../../c-api/perfmaps.rst:64
 msgid "Compile the given code object using the current perf trampoline."
-msgstr ""
+msgstr "使用目前的 perf trampoline 編譯給定的程式碼物件。"
 
 #: ../../c-api/perfmaps.rst:66
 msgid ""
 "The \"current\" trampoline is the one set by the runtime or the most recent :"
 "c:func:`PyUnstable_PerfTrampoline_SetPersistAfterFork` call."
 msgstr ""
+"「目前」的 trampoline，是指由 runtime 或最近一次呼叫\\ :c:func:"
+"`PyUnstable_PerfTrampoline_SetPersistAfterFork` 所設定的那一個。"
 
 #: ../../c-api/perfmaps.rst:69
 msgid ""
 "If no trampoline is set, falls back to normal compilation (no perf map "
 "entry)."
-msgstr ""
+msgstr "如果沒有設定 trampoline，則退回正常編譯（不產生 perf map 條目）。"
 
 #: ../../c-api/perfmaps.rst:0
 msgid "Parameters"
-msgstr ""
+msgstr "參數"
 
 #: ../../c-api/perfmaps.rst:71
 msgid "The code object to compile."
-msgstr ""
+msgstr "要編譯的程式碼物件。"
 
 #: ../../c-api/perfmaps.rst:0
 msgid "Returns"
-msgstr ""
+msgstr "回傳值"
 
 #: ../../c-api/perfmaps.rst:72 ../../c-api/perfmaps.rst:88
 msgid "0 on success, -1 on failure."
-msgstr ""
+msgstr "成功時回傳 0，失敗時回傳 -1。"
 
 #: ../../c-api/perfmaps.rst:78
 msgid "Set whether the perf trampoline should persist after a fork."
-msgstr ""
+msgstr "設定 perf trampoline 在 fork 之後是否應該持續存在。"
 
 #: ../../c-api/perfmaps.rst:80
 msgid ""
 "If ``enable`` is true (non-zero): perf map file remains open/valid post-"
 "fork. Child process inherits all existing perf map entries."
 msgstr ""
+"如果 ``enable`` 為 true（非零）：perf map 檔案在 fork 後仍保持開啟／有效，子"
+"行程會繼承所有既有的 perf map 條目。"
 
 #: ../../c-api/perfmaps.rst:82
 msgid ""
 "If ``enable`` is false (zero): perf map closes post-fork. Child process gets "
 "empty perf map."
 msgstr ""
+"如果 ``enable`` 為 false（零）：perf map 會在 fork 後關閉，子行程會得到空的 "
+"perf map。"
 
 #: ../../c-api/perfmaps.rst:85
 msgid "Default: false (clears on fork)."
-msgstr ""
+msgstr "預設值：false（在 fork 時清除）。"
 
 #: ../../c-api/perfmaps.rst:87
 msgid "1 to enable, 0 to disable."
-msgstr ""
+msgstr "1 表示啟用，0 表示停用。"

c-api/typeobj.po

@@ -4429,6 +4429,8 @@ msgid ""
 "the final release may race with concurrent releases from other threads and "
 "deallocation must only happen once."
 msgstr ""
+"當計數器歸零時，資源的清理必須以原子化的方式完成，因為最後一次釋放可能會與其"
+"他執行緒的並行釋放產生競爭，且解除配置的動作只能發生一次。"
 
 #: ../../c-api/typeobj.rst:3133
 msgid ""

c-api/veryhigh.po

@@ -388,9 +388,8 @@ msgid ""
 msgstr ""
 
 #: ../../c-api/veryhigh.rst:347
-#, fuzzy
 msgid "Low-level flags"
-msgstr "編譯器旗標。"
+msgstr "低階旗標"
 
 #: ../../c-api/veryhigh.rst:348
 msgid ""
@@ -399,13 +398,17 @@ msgid ""
 "reason to use them.  They are considered implementation details and may "
 "change at any time."
 msgstr ""
+"以下的旗標和遮罩僅滿足標準函式庫和互動式直譯器的少數特定需求，標準函式庫以外"
+"的程式碼很少有理由使用它們。它們被視為實作細節，可能隨時變更。"
 
 #: ../../c-api/veryhigh.rst:355
 msgid ""
 "This flag is a private interface between the compiler and the :mod:`codeop` "
 "module.  Do not use it; its behavior is unsupported and may change without "
 "warning."
 msgstr ""
+"此旗標是編譯器與 :mod:`codeop` 模組之間的私有介面，請勿使用；其行為不受支援，"
+"且可能在沒有警告的情況下變更。"
 
 #: ../../c-api/veryhigh.rst:359
 msgid ""
@@ -418,6 +421,12 @@ msgid ""
 "with a real syntax error, so that interactive interpreters know when to "
 "prompt for another line instead of reporting an error."
 msgstr ""
+"設定此旗標後，當編譯因原始文字在預期需要更多輸入之處結束而失敗時（例如在縮排"
+"區塊中間或未結束的字串字面值中），所引發的錯誤會是未有文件記載的 "
+"``_IncompleteInputError``，它是 :exc:`SyntaxError` 的子類別。:mod:`codeop` 模"
+"組會設定此旗標，並搭配 :c:macro:`PyCF_DONT_IMPLY_DEDENT`，以區分不完整的輸入"
+"與帶有真正語法錯誤的輸入，讓互動式直譯器知道何時該提示輸入下一行，而不是回報"
+"錯誤。"
 
 #: ../../c-api/veryhigh.rst:373
 msgid ""
@@ -427,6 +436,9 @@ msgid ""
 "the source ends with a newline; otherwise, compilation fails with a :exc:"
 "`SyntaxError`:"
 msgstr ""
+"依預設，使用 :c:var:`Py_single_input` 起始符號進行編譯時，抵達原始文字結尾會"
+"隱式關閉所有開啟的縮排區塊。設定此旗標後，只有當原始碼的最後一行以換行符號結"
+"尾時，開啟的區塊才會被關閉；否則編譯會失敗並引發 :exc:`SyntaxError`："
 
 #: ../../c-api/veryhigh.rst:379
 msgid ""
@@ -445,6 +457,20 @@ msgid ""
 "flags.cf_flags = PyCF_DONT_IMPLY_DEDENT;\n"
 "Py_CompileStringFlags(source, \"<input>\", Py_single_input, &flags);"
 msgstr ""
+"PyCompilerFlags flags = {\n"
+"    .cf_flags = 0,\n"
+"    .cf_feature_version = PY_MINOR_VERSION,\n"
+"};\n"
+"const char *source = \"if a:\\n    pass\";\n"
+"\n"
+"/* 「if」區塊被隱式關閉；\n"
+"   這會回傳一個程式碼物件： */\n"
+"Py_CompileStringFlags(source, \"<input>\", Py_single_input, &flags);\n"
+"\n"
+"/* 加上此旗標後，這會因為 SyntaxError 而失敗，\n"
+"   因為最後一行沒有以換行符號結尾： */\n"
+"flags.cf_flags = PyCF_DONT_IMPLY_DEDENT;\n"
+"Py_CompileStringFlags(source, \"<input>\", Py_single_input, &flags);"
 
 #: ../../c-api/veryhigh.rst:396
 msgid ""
@@ -453,12 +479,16 @@ msgid ""
 "does not yet end with a newline, so it fails to compile and the user is "
 "prompted for another line."
 msgstr ""
+":mod:`codeop` 模組使用此旗標來偵測不完整的互動式輸入。當使用者仍在縮排區塊內"
+"輸入時，原始碼尚未以換行符號結尾，因此編譯會失敗，並提示使用者輸入下一行。"
 
 #: ../../c-api/veryhigh.rst:403
 msgid ""
 "Read the source text as UTF-8, ignoring its :pep:`263` encoding declaration "
 "(\"coding cookie\"), if any:"
 msgstr ""
+"將原始文字以 UTF-8 讀取，忽略其 :pep:`263` 編碼宣告（「coding cookie」，如果"
+"有的話）："
 
 #: ../../c-api/veryhigh.rst:406
 msgid ""
@@ -477,20 +507,38 @@ msgid ""
 "flags.cf_flags = PyCF_IGNORE_COOKIE;\n"
 "Py_CompileStringFlags(source, \"<input>\", Py_file_input, &flags);"
 msgstr ""
+"PyCompilerFlags flags = {\n"
+"    .cf_flags = 0,\n"
+"    .cf_feature_version = PY_MINOR_VERSION,\n"
+"};\n"
+"const char *source = \"# coding: latin-1\\ns = '\\xe9'\\n\";\n"
+"\n"
+"/* coding cookie 被遵循：位元組 0xE9 被解碼為\n"
+"   Latin-1，這會回傳一個將 s 設為 \"é\" 的程式碼物件： */\n"
+"Py_CompileStringFlags(source, \"<input>\", Py_file_input, &flags);\n"
+"\n"
+"/* 加上此旗標後，cookie 會被忽略，導致編譯失敗\n"
+"   並出現 SyntaxError，因為 0xE9 不是有效的 UTF-8： */\n"
+"flags.cf_flags = PyCF_IGNORE_COOKIE;\n"
+"Py_CompileStringFlags(source, \"<input>\", Py_file_input, &flags);"
 
 #: ../../c-api/veryhigh.rst:423
 msgid ""
 "The :func:`compile`, :func:`eval` and :func:`exec` built-in functions set "
 "this flag when the source is a :class:`str` object, because they pass the "
 "text to the parser encoded as UTF-8."
 msgstr ""
+":func:`compile`、:func:`eval` 和 :func:`exec` 這幾個內建函式，會在原始碼是 :"
+"class:`str` 物件時設定此旗標，因為它們會將文字以 UTF-8 編碼傳遞給剖析器。"
 
 #: ../../c-api/veryhigh.rst:429
 msgid ""
 "Mark the source text as known to be UTF-8 encoded. The :func:`compile`, :"
 "func:`eval` and :func:`exec` built-in functions set this flag, but it "
 "currently has no effect."
 msgstr ""
+"將原始文字標記為已知採用 UTF-8 編碼。:func:`compile`、:func:`eval` 和 :func:"
+"`exec` 這幾個內建函式會設定此旗標，但目前沒有任何效果。"
 
 #: ../../c-api/veryhigh.rst:433
 msgid ""
@@ -502,7 +550,7 @@ msgstr ""
 
 #: ../../c-api/veryhigh.rst:438
 msgid "The following masks combine several flags:"
-msgstr ""
+msgstr "以下的遮罩結合了數個旗標："
 
 #: ../../c-api/veryhigh.rst:442
 msgid ""
@@ -512,24 +560,34 @@ msgid ""
 "__future__ import`` statement, the flag for the imported feature is added to "
 "*flags*, so that code executed later in the same context inherits it."
 msgstr ""
+"所有 ``CO_FUTURE`` 旗標的位元遮罩（請參閱 :ref:`c_codeobject_flags`），這些旗"
+"標用來選擇通常由 :ref:`future 陳述式 <future>`\\ 啟用的功能。當使用 "
+"``PyCompilerFlags *flags`` 引數編譯的程式碼包含 ``from __future__ import`` 陳"
+"述式時，該匯入功能所對應的旗標會被加入 *flags* 中，讓稍後在同一情境中執行的程"
+"式碼繼承它。"
 
 #: ../../c-api/veryhigh.rst:452
 msgid ""
 "Do not use this mask in new code.  It is kept only so that old code passing "
 "its flags to :func:`compile` keeps working."
 msgstr ""
+"請勿在新程式碼中使用此遮罩，保留它只是為了讓傳遞其旗標給 :func:`compile` 的舊"
+"有程式碼能繼續運作。"
 
 #: ../../c-api/veryhigh.rst:455
 msgid ""
 "Bitmask of flags for obsolete future features that no longer have any effect."
-msgstr ""
+msgstr "已過時且不再有任何作用的 future 功能旗標之位元遮罩。"
 
 #: ../../c-api/veryhigh.rst:460
 msgid ""
 "Bitmask of all ``PyCF`` flags that change how the source is compiled, such "
 "as :c:macro:`PyCF_ONLY_AST`. The :func:`compile` built-in function uses this "
 "mask to validate its *flags* argument."
 msgstr ""
+"所有會改變原始碼編譯方式的 ``PyCF`` 旗標之位元遮罩，例如 :c:macro:"
+"`PyCF_ONLY_AST`。:func:`compile` 這個內建函式使用此遮罩來驗證其 *flags* 引"
+"數。"
 
 #: ../../c-api/veryhigh.rst:469
 msgid "Available start symbols"