Continue tutorial/modules.po#72
Merged
Merged
Conversation
Contributor
Author
|
The tutorial/modules.po was completed. Reference: https://terms.naer.edu.tw/ |
Fix missed time data and small bug.
adrianliaw
reviewed
Jun 3, 2021
| "This does not introduce the module name from which the imports are taken in " | ||
| "the local symbol table (so in the example, ``fibo`` is not defined)." | ||
| msgstr "" | ||
| "在 import 之後的名稱會被導入，但定義該函式的整個模組名稱並不會被引入在本地符" |
| msgid "" | ||
| "It can also be used when utilising :keyword:`from` with similar effects::" | ||
| msgstr "" | ||
| "在使用時也可用 :keyword:`from` 獲得類似的效果：\n" |
Collaborator
There was a problem hiding this comment.
在使用 from 時也可以用同樣的方式獲得類似的效果
| "because the code that parses the command line only runs if the module is " | ||
| "executed as the \"main\" file:" | ||
| msgstr "" | ||
| "你可以將檔案作為腳本也同時可以作為被 import 的模組，因為解析 (parse) 指令行的" |
| "executed as the \"main\" file:" | ||
| msgstr "" | ||
| "你可以將檔案作為腳本也同時可以作為被 import 的模組，因為解析 (parse) 指令行的" | ||
| "程式碼只會在當模組是 “main “ 檔案時，才會執行：" |
Collaborator
There was a problem hiding this comment.
這邊我覺得可以把 main 翻譯過來，例如 「主」檔案。原文的 main 也只是要說明「主要」的這個概念而不是真的 Python 術語，__main__ 才是不能翻譯的部分。
| #: ../../tutorial/modules.rst:169 | ||
| msgid "If the module is imported, the code is not run::" | ||
| msgstr "" | ||
| "如果 import 模組，則不會執行程式碼：\n" |
Collaborator
There was a problem hiding this comment.
如果此模組是被 import 的，則該段程式碼不會被執行
| "Python 附帶了一個標準模組庫，詳細的介紹在另一份文件，稱為「Python 程式庫參考" | ||
| "手冊」（簡稱為「程式庫參考手冊」）。有些模組被內嵌在直譯器中；它們使一些不屬" | ||
| "於語言核心但依然內建的運算得以存取，其目的是為了提高效率，或提供作業系統基本" | ||
| "操作（例如系統呼叫）的存取。這些模組的集合是一個組態選項，它們取決於底層平" |
| "於語言核心但依然內建的運算得以存取，其目的是為了提高效率，或提供作業系統基本" | ||
| "操作（例如系統呼叫）的存取。這些模組的集合是一個組態選項，它們取決於底層平" | ||
| "台。例如：\\ :mod:`winreg` 模組僅供 Windows 使用。值得注意的模組是 :mod:`sys`" | ||
| "\\ ，它被內嵌到每個 Python 直譯器中。變數 ``sys.ps1`` 和 ``sys.ps2`` 則用來定" |
| "default if :envvar:`PYTHONPATH` is not set. You can modify it using " | ||
| "standard list operations::" | ||
| msgstr "" | ||
| "變數 ``sys.path`` 是一個字串 list，它決定直譯器的模組搜尋路徑。它的初始化為環" |
| msgstr "" | ||
| "變數 ``sys.path`` 是一個字串 list，它決定直譯器的模組搜尋路徑。它的初始化為環" | ||
| "境變數 :envvar:`PYTHONPATH` 中提取的預設路徑，或是當 :envvar:`PYTHONPATH` 未" | ||
| "設定時，從內建預設值提取。你可以用標準的 list 運算修改該變數：\n" |
| "you want a list of those, they are defined in the standard module :mod:" | ||
| "`builtins`::" | ||
| msgstr "" | ||
| ":func:`dir` 不會列出內建函式和變數的名稱。如果你想要上述內容的 list，它們被定" |
Collaborator
There was a problem hiding this comment.
這邊的 list 指的不是 Python 的 list，「如果你想要列出它們」我覺得就可以了
All above suggestion fixed. Thanks!
cache: "快取"
adrianliaw
reviewed
Jun 6, 2021
| "authors of multi-module packages like NumPy or Pillow from having to worry " | ||
| "about each other's module names." | ||
| msgstr "" | ||
| "套件是一種使用「點分隔模組名稱」建構 Python 模組命名空間的方法。例如，模組名" |
| "terms of a hierarchical filesystem):" | ||
| msgstr "" | ||
| "假設你想設計一個能統一處理音訊檔案及音訊數據的模組集合（「套件」）。因為音訊" | ||
| "檔案有很多的不同的格式（通常以它們的擴充來辨識，例如：\\ :file:`.wav`" |
| "operations. Here's a possible structure for your package (expressed in " | ||
| "terms of a hierarchical filesystem):" | ||
| msgstr "" | ||
| "假設你想設計一個能統一處理音訊檔案及音訊數據的模組集合（「套件」）。因為音訊" |
| "檔案有很多的不同的格式（通常以它們的擴充來辨識，例如：\\ :file:`.wav`" | ||
| "\\ ，\\ :file:`.aiff`\\ ，\\ :file:`.au`\\ ），因此，為了不同檔案格式之間的轉" | ||
| "換，你會需要建立和維護一個不斷增長的模組集合。為了要達成對音訊數據的許多不同" | ||
| "作業（例如，音訊混合、增加迴聲、套用等化器功能、創造人工立體音效），你將編寫" |
| "\\ ，\\ :file:`.aiff`\\ ，\\ :file:`.au`\\ ），因此，為了不同檔案格式之間的轉" | ||
| "換，你會需要建立和維護一個不斷增長的模組集合。為了要達成對音訊數據的許多不同" | ||
| "作業（例如，音訊混合、增加迴聲、套用等化器功能、創造人工立體音效），你將編寫" | ||
| "一個無止盡的模組流來執行這些作業。以下是你的套件可能的架構（以階層式檔案系統" |
| "`surround` module for example, you might use::" | ||
| msgstr "" | ||
| "你也可以用 ``from module import name`` 的 import 陳述式，編寫「相對 " | ||
| "import」。這些 import 使用前導句號 (leading dot) 指示相對 import 中的當前套件" |
Collaborator
There was a problem hiding this comment.
leading dot 應該不需要註釋原文，不是一個專業術語，只是說模組名稱前面要加句點而已
| "and subpackages contained in the package." | ||
| msgstr "" | ||
| "套件也支援一個特殊屬性 :attr:`__path__`\\ 。在初始化時，它是一個包含該套件檔" | ||
| "案 :file:`__init__.py` 的目錄名稱 list，初始化時機是在這個檔案的程式碼被執行" |
Collaborator
There was a problem hiding this comment.
它在初始化時是一個 list，包含該套件的 __init__.py 檔案所在的目錄名稱
（也就是說 __path__ 一開始只有一個元素而已）
| msgstr "" | ||
| "套件也支援一個特殊屬性 :attr:`__path__`\\ 。在初始化時，它是一個包含該套件檔" | ||
| "案 :file:`__init__.py` 的目錄名稱 list，初始化時機是在這個檔案的程式碼被執行" | ||
| "之前。這個變數可以被修改，但這樣做會影響將來對套件內含模組和子套件的搜尋。" |
| "While this feature is not often needed, it can be used to extend the set of " | ||
| "modules found in a package." | ||
| msgstr "" | ||
| msgstr "雖然這個特色不太常用，但它可用於擴充套件中的模組集合。" |
| "execution of a module-level function definition enters the function name in " | ||
| "the module's global symbol table." | ||
| msgstr "" | ||
| "實際上，函式定義也是「被執行」的「陳述式」；在執行模組層次的函式定義時，會輸" |
All suggestions were applied. Thanks!
Contributor
Author
|
All suggestions were applied. |
This was referenced Oct 26, 2021
beccalzh
pushed a commit
to beccalzh/python-docs-zh-tw
that referenced
this pull request
Sep 4, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the work continued from PR #28.
The review comments were all fixed.
I will start from this point (rst:262).