Skip to content

Conversation

@ken71301
Copy link
Collaborator

開始試用 skill ,效果看起來還不錯

@ken71301 ken71301 self-assigned this Jan 17, 2026
@ken71301 ken71301 requested a review from mattwang44 January 17, 2026 10:37
"在 Python 從 ``.pyc`` 檔案載入被快取的位元組碼之前,會檢查該快取是否與來源的 "
"``.py`` 檔案保持同步。預設情況下,Python 透過在寫入快取檔案時儲存來源檔案的最"
"後修改時間戳和大小來完成此操作。在執行時,引入系統會透過將快取檔案中儲存的元"
"資料 (metadata) 與來源檔案的元資料進行比對來驗證快取檔案。"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alternative: metadata -> 詮釋資料、後設資料
https://w.wiki/6HyM

後面有一處翻譯是後設資料、應統一用詞

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +1169 to +1170
"中的雜湊進行比較來驗證快取檔案。如果發現需檢查的基於雜湊的快取檔案無效,"
"Python 會重新產生並寫入新的需檢查的基於雜湊的快取檔案。對於不需要檢查的基於雜"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: too many 的?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

我嘗試了這樣
Python 會重新產生並寫入新的需檢查(的)基於雜湊(的)快取檔案

老實說我念了幾次,少了哪個的都怪怪的...
倒是上下兩句想修一下

"Python 3.3. :pep:`420` also introduced the :meth:`!find_loader` protocol as "
"an alternative to :meth:`!find_module`."
msgstr ""
":pep:`420` 在 Python 3.3 中引入了 :term:`namespace packages <namespace "
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

displayed text 需翻譯

"Python 3.3. :pep:`420` also introduced the :meth:`!find_loader` protocol as "
"an alternative to :meth:`!find_module`."
msgstr ""
":pep:`420` 在 Python 3.3 中引入了 :term:`namespace packages <namespace "
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

希望這篇的 introduce 不要再翻成「引入」、和 import 做出區別,像是改為「採納」、「引進」

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

我先統一成 「引進」

"提醒一句:本節與前一節都使用了 *尋檢器* 這個術語,並透過使用術語 :term:`meta "
"path finder` 和 :term:`path entry finder` 來區分它們。這兩種類型的尋檢器非常"
"相似,支援類似的協定,並在引入過程中以類似的方式運作,但請記住,它們之間有些"
"微的差異。特別是,元路徑尋檢器在引入過程的一開始運作,並通"
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"微的差異。特別是,元路徑尋檢器在引入過程的一開始運作,並通"
"微的差異。尤其元路徑尋檢器會在引入過程開始時運作,並通"

ken71301 and others added 3 commits January 18, 2026 13:46
expensive > 代價高昂\高代價
introduce > 引進
specification 先統一成規格
@ken71301 ken71301 requested a review from mattwang44 January 18, 2026 07:05
@josix
Copy link
Collaborator

josix commented Jan 18, 2026

有機會一起將 skill 使用的 md commit 進來嗎?應該會有助於其他使用 LLM 工具翻譯的貢獻者,大家翻譯的一致性也會比較高一些

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants