Finished reference/introduction.po

Author: JunliXiao

reference/introduction.po

@@ -7,7 +7,7 @@ msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2025-09-08 15:25+0800\n"
-"PO-Revision-Date: 2025-11-20 07:11+0800\n"
+"PO-Revision-Date: 2025-11-23 21:07+0800\n"
 "Last-Translator: Junli Xiao <https://github.com/JunliXiao>\n"
 "Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"
 "tw)\n"
@@ -180,8 +180,8 @@ msgid ""
 "know about the specific implementation you're using."
 msgstr ""
 "上述每一個實作都和這份手冊裡所描述的 Python 語言有些許不同，可能需要特定的、"
-"在標準 Python 文件涵蓋內容以外的資訊才能掌握。請參閱特定實作的相關文件來取得"
-"你使用此實作的須知。"
+"在標準 Python 文件涵蓋內容以外的資訊才能掌握。如果在使用它們時有需要瞭解更"
+"多，請參閱特定實作的相關文件。"
 
 #: ../../reference/introduction.rst:89
 msgid "Notation"
@@ -268,7 +268,7 @@ msgid ""
 "``e1 e2``: Items separated only by whitespace denote a sequence. Here, "
 "``e1`` must be followed by ``e2``."
 msgstr ""
-"``e1 e2``：僅由空白所分隔的多個項目代表一個序列。這裡，``e1`` 之後必須以 "
+"``e1 e2``：僅由空白所開的多個項目代表一個序列。這裡，``e1`` 之後必須以 "
 "``e2`` 接續。"
 
 #: ../../reference/introduction.rst:135
@@ -278,8 +278,8 @@ msgid ""
 "traditional PEG grammars, this is written as a slash, ``/``, rather than a "
 "vertical bar. See :pep:`617` for more background and details."
 msgstr ""
-"``e1 | e2``：垂直槓符號用來分隔可能的項目。它代表 PEG 的「有序選擇」——如果 "
-"``e1`` 已符合，那麼 ``e2`` 便不考慮。在傳統的 PEG 文法裡，使用的是斜線 ``/`` "
+"``e1 | e2``：垂直槓符號用來隔開可匹配的項目。它代表 PEG 的「有序選擇」——如果 "
+"``e1`` 已匹配，那麼 ``e2`` 便不考慮。在傳統的 PEG 文法裡，使用的是斜線 ``/`` "
 "而非垂直槓。如需更多背景細節，可參考 :pep:`617`。"
 
 #: ../../reference/introduction.rst:141
@@ -295,8 +295,8 @@ msgid ""
 "``[e]``: A phrase enclosed in square brackets means zero or one occurrences. "
 "In other words, the enclosed phrase is optional."
 msgstr ""
-"``[e]``：以方括號包圍的元素意謂出現零次或一次。換句話說，方括號裡的元素為選擇"
-"性的。"
+"``[e]``：以方括號包圍的元素意謂零次或一次。換句話說，方括號裡的元素為選擇性"
+"的。"
 
 #: ../../reference/introduction.rst:145
 msgid ""
@@ -321,6 +321,8 @@ msgid ""
 "choice of any single character in the given (inclusive) range of ASCII "
 "characters."
 msgstr ""
+"``”a”…”z”``：兩個字面值字元由三個點隔開，表示在此界定範圍內（含）任一個 "
+"ASCII 字元皆合文法。"
 
 #: ../../reference/introduction.rst:154
 msgid ""
@@ -329,48 +331,56 @@ msgid ""
 "\">``), or an abbreviation that is defined in nearby text (for example, "
 "``<Lu>``)."
 msgstr ""
+"``<…>``：角括號內的文字片語是對匹配符號（例如，``<除了 “\\” 以外的任何 ASCII "
+"字元>``）的非正式說明，或是在附近段落有解釋的縮寫（例如 ``<Lu>``）。"
 
 #: ../../reference/introduction.rst:160
 msgid ""
 "Some definitions also use *lookaheads*, which indicate that an element must "
 "(or must not) match at a given position, but without consuming any input:"
 msgstr ""
+"有些定義會採用\\ *預看*\\作法，也就是指定位置的元素必須（或必須不）匹配，但不"
+"消耗任何輸入："
 
 #: ../../reference/introduction.rst:163
 msgid "``&e``: a positive lookahead (that is, ``e`` is required to match)"
-msgstr ""
+msgstr "``&e``：正向預看，也就是 ``e`` 必須匹配"
 
 #: ../../reference/introduction.rst:164
 msgid ""
 "``!e``: a negative lookahead (that is, ``e`` is required *not* to match)"
-msgstr ""
+msgstr "``!e``：負向預看，也就是 ``e`` 必須\\ *不匹配*"
 
 #: ../../reference/introduction.rst:166
 msgid ""
 "The unary operators (``*``, ``+``, ``?``) bind as tightly as possible; the "
 "vertical bar (``|``) binds most loosely."
 msgstr ""
+"一元運算子（``*``、``+``、``?``）跟元素的繫結關係最緊密；垂直槓 (``|``) 的則"
+"最鬆散。"
 
 #: ../../reference/introduction.rst:169
 msgid "White space is only meaningful to separate tokens."
-msgstr ""
+msgstr "空格的用途只在於隔開 token。"
 
 #: ../../reference/introduction.rst:171
 msgid ""
 "Rules are normally contained on a single line, but rules that are too long "
 "may be wrapped:"
-msgstr ""
+msgstr "通常而言，規則長度都在一行以內，但太長的規則也可以換行表示："
 
 #: ../../reference/introduction.rst:180
 msgid ""
 "Alternatively, rules may be formatted with the first line ending at the "
 "colon, and each alternative beginning with a vertical bar on a new line. For "
 "example:"
 msgstr ""
+"或者，規則可以呈現為第一行以分號結束，而每一種可匹配選項皆在新一行以垂直槓開"
+"頭表示。例如："
 
 #: ../../reference/introduction.rst:195
 msgid "This does *not* mean that there is an empty first alternative."
-msgstr ""
+msgstr "這\\ *不代表*\\一開始有一個空白匹配選項。"
 
 #: ../../reference/introduction.rst:202
 msgid "Lexical and Syntactic definitions"
@@ -385,6 +395,10 @@ msgid ""
 "some cases the exact boundary between the two phases is a CPython "
 "implementation detail."
 msgstr ""
+"\\ *詞法* (lexical) 和\\ *語法* (syntactic) 分析是有一些差異"
+"的：:term:`lexical analyzer` 處理的對象是輸入來源的各個字元，而\\ *剖析器* "
+"（語法分析器）處理的則是詞法分析產生的 :term:`tokens <token>` 流。然而在某些"
+"時候，這兩個階段的確切分界會是 CPython 實作細節的問題。"
 
 #: ../../reference/introduction.rst:211
 msgid ""
@@ -394,13 +408,20 @@ msgid ""
 "like :data:`token.INDENT` or :data:`~token.NEWLINE`. *Syntactic* definitions "
 "then use these tokens, rather than source characters."
 msgstr ""
+"實務上，這兩個的差異在於：在\\ *詞法*\\定義裡，任何空格都是有影響的。詞法分析"
+"器\\ :ref:`捨棄<whitespace>`\\了那些無法轉換成 token（例"
+"如 :data:`token.INDENT` 或 :data:`~token.NEWLINE`）的空白。\\ *語法*\\定義才"
+"接著處理這些 tokens，而非來源字元。"
 
 #: ../../reference/introduction.rst:217
 msgid ""
 "This documentation uses the same BNF grammar for both styles of definitions. "
 "All uses of BNF in the next chapter (:ref:`lexical`) are lexical "
 "definitions; uses in subsequent chapters are syntactic definitions."
 msgstr ""
+"這份手冊裡不管是為了定義還是風格表現，都使用了同樣的 BNF 文法。在下一個章節"
+"（:ref:`lexical`）裡所有 BNF 的使用都是詞法定義；在那之後的章節裡則是語法定"
+"義。"
 
 #: ../../reference/introduction.rst:91
 msgid "BNF"