feat: translate howto/logging.po by josix · Pull Request #1195 · python/python-docs-zh-tw

josix · 2026-01-23T08:10:53Z

Restore and fix f765f25

Add Traditional Chinese translations for the logging HOWTO documentation. This includes:

Header updates with new translator credit (CTHua)
Translation of main sections and headings
Translation of logging level descriptions
Translation of handler and formatter documentation
Translation of configuration examples

Add Traditional Chinese translations for the logging HOWTO documentation. This includes: - Header updates with new translator credit (CTHua) - Translation of main sections and headings - Translation of logging level descriptions - Translation of handler and formatter documentation - Translation of configuration examples https://claude.ai/code/session_01FubLSJSpQ2mNDuK2cjMebE

Copilot

Pull request overview

Adds/refreshes Traditional Chinese translations for the Logging HOWTO (howto/logging.po) and updates translation metadata.

Changes:

Updates header metadata (copyright year range, translator credit, generator).
Translates additional sections/paragraphs and many table entries in the Logging HOWTO.
Adds translations for advanced concepts (loggers/handlers/formatters/config options).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-01-23T08:17:21Z

howto/logging.po

+msgstr "進階日誌記錄教學"

 #: ../../howto/logging.rst:320
+#, fuzzy


This entry is marked as fuzzy but already has a translated msgstr. Fuzzy entries are typically excluded from the built docs/translation stats. If the translation is final, remove the #, fuzzy flag; otherwise clear the msgstr until it’s ready.

Suggested change

#, fuzzy

Copilot · 2026-01-23T08:17:21Z

howto/logging.po

+msgstr "如果未提供設定，會發生什麼"

 #: ../../howto/logging.rst:785
+#, fuzzy


This entry is marked as fuzzy but already has a translated msgstr. Fuzzy entries are typically excluded from the built docs/translation stats. If the translation is final, remove the #, fuzzy flag; otherwise clear the msgstr until it’s ready.

Suggested change

#, fuzzy

Copilot · 2026-01-23T08:17:21Z

howto/logging.po

 "the following example::"
 msgstr ""
+"要取得值以傳遞給 :func:`basicConfig` 的 *level* 引數，你可能會想檢查任何使用"
+"者輸入的值，如下面的示例所示： ::"


This msgstr uses ： :: (Chinese colon plus ::). In reST, :: already renders as a single trailing : while introducing a literal block; adding a separate colon can produce doubled punctuation. Consider ending the sentence with :: directly.

howto/logging.po

Copilot · 2026-01-23T08:17:22Z

howto/logging.po

+"格式化器對象（Formatter objects）設置記錄訊息的最終順序、結構和內容。和基礎"
+"的 :class:`logging.Handler` 類別不同，應用程式程式碼可以實例化格式化器類別，"
+"不過如果應用程式需要特殊行為，則可能需要子類別繼承格式化器。構造函式"
+"（condtructor）有三個可選引數 -- 訊息格式字串、日期格式字串和樣式指示器。"


Typo in the embedded English term: condtructor should be constructor.

Suggested change

"（condtructor）有三個可選引數 -- 訊息格式字串、日期格式字串和樣式指示器。"

"（constructor）有三個可選引數 -- 訊息格式字串、日期格式字串和樣式指示器。"

howto/logging.po

Copilot · 2026-01-23T08:17:25Z

howto/logging.po

 "time, provide a *datefmt* argument to ``basicConfig``, as in this example::"
 msgstr ""
+"預設的時間/日期格式遵照 ISO8601 或 :rfc:`3339`。如果你想要有更多的時間/日期自"
+"訂性，可以在 ``basicConfig`` 傳入 *datefmt* 的引數，如以下範例： ::"


This msgstr uses ： :: (Chinese colon plus ::). In reST, :: already renders as a single trailing : while introducing a literal block; adding a separate colon can produce doubled punctuation. Consider ending the sentence with :: directly.

Suggested change

"訂性，可以在 ``basicConfig`` 傳入 *datefmt* 的引數，如以下範例： ::"

"訂性，可以在 ``basicConfig`` 傳入 *datefmt* 的引數，如以下範例::"

Copilot · 2026-01-23T08:17:25Z

howto/logging.po

 "being the names of the objects::"
 msgstr ""
+"以下Python模組建立了一個幾乎與上面列表中相同的記錄器(logger)、處理器"
+"(handler)，和格式化器(formatter)，唯一不同之處在於對象名稱的改變： ::"


This msgstr uses ： :: (Chinese colon plus ::). In reST, :: already renders as a single trailing : while introducing a literal block; adding a separate colon can produce doubled punctuation. Consider ending the sentence with :: directly.

Suggested change

"(handler)，和格式化器(formatter)，唯一不同之處在於對象名稱的改變： ::"

"(handler)，和格式化器(formatter)，唯一不同之處在於對象名稱的改變::"

howto/logging.po

Run powrap to fix line wrapping issues in the PO file. https://claude.ai/code/session_01FubLSJSpQ2mNDuK2cjMebE

Fix inconsistent term references at line 195 where :meth:`~Logger.debug` and :meth:`~Logger.info` were incorrectly translated as :func:`debug` and :func:`info`. https://claude.ai/code/session_01FubLSJSpQ2mNDuK2cjMebE

ken71301

some fix

ken71301 · 2026-01-31T03:16:10Z

howto/logging.po

 "and a logging cookbook, please see :ref:`tutorial-ref-links`."
 msgstr ""
+"此頁面包含教學資訊。有關參考資訊和日誌記錄手冊的鏈接，請參閱 :ref:`tutorial-"
+"ref-links`。"


linter again? seems itr should be contain more bytes in a line

ken71301 · 2026-01-31T03:20:00Z

howto/logging.po

 msgstr ""
+"日誌（Logging）提供方便使用的一組簡單紀錄函式。這些函式包括：:func:`debug`、:"
+"func:`info`、:func:`warning`、:func:`error` 和 :func:`critical`。如需確定何時"
+"使用紀錄，請參見以下表格，其中列出每個常見工作的最佳工具。"


這段怪怪的耶好像沒翻到一些字

ken71301 · 2026-01-31T03:23:38Z

howto/logging.po

 msgid ""
 "Display console output for ordinary usage of a command line script or program"
-msgstr ""
+msgstr "對於命令行或程式的普通用法，結果會顯示在控制台"


Suggested change

msgstr "對於命令行或程式的普通用法，結果會顯示在控制台"

msgstr "對於命令行或程式的一般用法，結果會顯示在控制台"

我覺得一般比較順

ken71301 · 2026-01-31T03:30:41Z

howto/logging.po

 "A logger's :meth:`~Logger.info` (or :meth:`~Logger.debug` method for very "
 "detailed output for diagnostic purposes)"
 msgstr ""
+":func:`logging.info` （或者在需要診斷用的詳細輸出時使用 :func:`logging."


loggers 還是要翻？

ken71301 · 2026-01-31T03:36:25Z

howto/logging.po

 ":func:`warnings.warn` in library code if the issue is avoidable and the "
 "client application should be modified to eliminate the warning"
 msgstr ""
+"如果問題是可以避免的，那麼客戶端應該修改以消除警告，請在庫程式碼中使用 :func:"


Suggested change

"如果問題是可以避免的，那麼客戶端應該修改以消除警告，請在庫程式碼中使用 :func:"

"如果問題是可以避免的，那麼客戶端應該修改以消除警告，請在函式庫程式碼中使用 :func:"

ken71301 · 2026-01-31T05:30:04Z

howto/logging.po

+"debug``，而不是建立一個記錄器並在其上呼叫函式。這些函式在根記錄器上運作，但它"
+"們很有用，因為它們會在尚未呼叫 :func:`~logging.basicConfig` 時（如此範例）為"
+"你呼叫它。然而，在較大的程式中，你通常會希望明確控制日誌配置——因此基於這個原"
+"因以及其他原因，最好建立記錄器並呼叫它們的方法。"


nit

Suggested change

"因以及其他原因，最好建立記錄器並呼叫它們的方法。"

"因以及其他狀況，最好建立記錄器並呼叫它們的方法。"

ken71301 · 2026-01-31T05:35:27Z

howto/logging.po

 "passed, which determines how encoding errors are handled. For available "
 "values and the default, see the documentation for :func:`open`."
 msgstr ""
+"新增了 *encoding* 引數。在早期的 Python 版本中，如果未指定，將使用 :func:"


Suggested change

"新增了 *encoding* 引數。在早期的 Python 版本中，如果未指定，將使用 :func:"

"新增了 *encoding* 引數。在早期的 Python 版本中，或未指定此引數，將使用 :func:"

ken71301 · 2026-01-31T05:37:29Z

howto/logging.po

 msgstr ""
+"新增了 *encoding* 引數。在早期的 Python 版本中，如果未指定，將使用 :func:"
+"`open` 的預設編碼。儘管在上面的範例中沒有顯示，現在也可以傳遞 *errors* 引數，"
+"以決定如何處理編碼錯誤。可用的值與其預設值，請參閱 :func:`open` 的文件。"


Suggested change

"以決定如何處理編碼錯誤。可用的值與其預設值，請參閱 :func:`open` 的文件。"

"以決定如何處理編碼錯誤。有關其可用的值與預設值，請參閱 :func:`open` 的文件。"

ken71301 · 2026-01-31T06:01:36Z

howto/logging.po

 "argument. You may want to error check any user input value, perhaps as in "
 "the following example::"
 msgstr ""
+"要取得值以傳遞給 :func:`basicConfig` 的 *level* 引數，你可能會想檢查任何使用"


Suggested change

"要取得值以傳遞給 :func:`basicConfig` 的 *level* 引數，你可能會想檢查任何使用"

"要取得以 *level* 引數傳遞給 :func:`basicConfig` 的值，你可能會想檢查任何使用"

ken71301 · 2026-01-31T06:02:33Z

howto/logging.po

 "the following example::"
 msgstr ""
+"要取得值以傳遞給 :func:`basicConfig` 的 *level* 引數，你可能會想檢查任何使用"
+"者輸入的值，如下面的示例所示： ::"


Suggested change

"者輸入的值，如下面的示例所示： ::"

"者輸入的值，如以下範例所示： ::"

josix requested a review from Copilot January 23, 2026 08:12

Copilot started reviewing on behalf of josix January 23, 2026 08:12 View session

Copilot AI reviewed Jan 23, 2026

View reviewed changes

claude added 2 commits January 23, 2026 08:39

style: fix line wrapping in howto/logging.po

0db7e79

Run powrap to fix line wrapping issues in the PO file. https://claude.ai/code/session_01FubLSJSpQ2mNDuK2cjMebE

fix: correct inconsistent RST references in logging.po

5477e56

Fix inconsistent term references at line 195 where :meth:`~Logger.debug` and :meth:`~Logger.info` were incorrectly translated as :func:`debug` and :func:`info`. https://claude.ai/code/session_01FubLSJSpQ2mNDuK2cjMebE

ken71301 reviewed Jan 31, 2026

View reviewed changes

josix added 3 commits February 2, 2026 23:54

fix translation according to review from agents

32ad9dc

Merge branch '3.14' into claude/create-translation-update-q7zox

cc1e267

docs: Fix spacing in Logger class references in logging documentation

e575104

josix requested a review from ken71301 February 4, 2026 12:45

	"（condtructor）有三個可選引數 -- 訊息格式字串、日期格式字串和樣式指示器。"
	"（constructor）有三個可選引數 -- 訊息格式字串、日期格式字串和樣式指示器。"

	"訂性，可以在 ``basicConfig`` 傳入 datefmt 的引數，如以下範例： ::"
	"訂性，可以在 ``basicConfig`` 傳入 datefmt 的引數，如以下範例::"

	"(handler)，和格式化器(formatter)，唯一不同之處在於對象名稱的改變： ::"
	"(handler)，和格式化器(formatter)，唯一不同之處在於對象名稱的改變::"

	msgstr "對於命令行或程式的普通用法，結果會顯示在控制台"
	msgstr "對於命令行或程式的一般用法，結果會顯示在控制台"

	"如果問題是可以避免的，那麼客戶端應該修改以消除警告，請在庫程式碼中使用 :func:"
	"如果問題是可以避免的，那麼客戶端應該修改以消除警告，請在函式庫程式碼中使用 :func:"

	"因以及其他原因，最好建立記錄器並呼叫它們的方法。"
	"因以及其他狀況，最好建立記錄器並呼叫它們的方法。"

	"新增了 encoding 引數。在早期的 Python 版本中，如果未指定，將使用 :func:"
	"新增了 encoding 引數。在早期的 Python 版本中，或未指定此引數，將使用 :func:"

	"以決定如何處理編碼錯誤。可用的值與其預設值，請參閱 :func:`open` 的文件。"
	"以決定如何處理編碼錯誤。有關其可用的值與預設值，請參閱 :func:`open` 的文件。"

	"要取得值以傳遞給 :func:`basicConfig` 的 level 引數，你可能會想檢查任何使用"
	"要取得以 level 引數傳遞給 :func:`basicConfig` 的值，你可能會想檢查任何使用"

	"者輸入的值，如下面的示例所示： ::"
	"者輸入的值，如以下範例所示： ::"

Uh oh!

Conversation

josix commented Jan 23, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

ken71301 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants