# Copyright (C) 2001-2024, Python Software Foundation

# This file is distributed under the same license as the Python package.

#

# Translators:

msgid ""

msgstr ""

"Project-Id-Version: Python 3.13\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2025-05-09 00:15+0000\n"

"PO-Revision-Date: 2018-05-23 16:17+0000\n"

"Last-Translator: Adrian Liaw <[email protected]>\n"

"Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"

"tw)\n"

"Language: zh_TW\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Plural-Forms: nplurals=1; plural=0;\n"

#: ../../reference/lexical_analysis.rst:6

msgid "Lexical analysis"

msgstr "詞法分析"

#: ../../reference/lexical_analysis.rst:10

msgid ""

"A Python program is read by a *parser*. Input to the parser is a stream of :"

"term:`tokens <token>`, generated by the *lexical analyzer* (also known as "

"the *tokenizer*). This chapter describes how the lexical analyzer breaks a "

"file into tokens."

msgstr ""

#: ../../reference/lexical_analysis.rst:15

msgid ""

"Python reads program text as Unicode code points; the encoding of a source "

"file can be given by an encoding declaration and defaults to UTF-8, see :pep:"

"`3120` for details. If the source file cannot be decoded, a :exc:"

"`SyntaxError` is raised."

msgstr ""

#: ../../reference/lexical_analysis.rst:24

msgid "Line structure"

msgstr ""

#: ../../reference/lexical_analysis.rst:28

msgid "A Python program is divided into a number of *logical lines*."

msgstr ""

#: ../../reference/lexical_analysis.rst:34

msgid "Logical lines"

msgstr ""

#: ../../reference/lexical_analysis.rst:38

msgid ""

"The end of a logical line is represented by the token NEWLINE. Statements "

"cannot cross logical line boundaries except where NEWLINE is allowed by the "

"syntax (e.g., between statements in compound statements). A logical line is "

"constructed from one or more *physical lines* by following the explicit or "

"implicit *line joining* rules."

msgstr ""

#: ../../reference/lexical_analysis.rst:48

msgid "Physical lines"

msgstr ""

#: ../../reference/lexical_analysis.rst:50

msgid ""

"A physical line is a sequence of characters terminated by an end-of-line "

"sequence. In source files and strings, any of the standard platform line "

"termination sequences can be used - the Unix form using ASCII LF (linefeed), "

"the Windows form using the ASCII sequence CR LF (return followed by "

"linefeed), or the old Macintosh form using the ASCII CR (return) character. "

"All of these forms can be used equally, regardless of platform. The end of "

"input also serves as an implicit terminator for the final physical line."

msgstr ""

#: ../../reference/lexical_analysis.rst:58

msgid ""

"When embedding Python, source code strings should be passed to Python APIs "

"using the standard C conventions for newline characters (the ``\\n`` "

"character, representing ASCII LF, is the line terminator)."

msgstr ""

#: ../../reference/lexical_analysis.rst:66

msgid "Comments"

msgstr ""

#: ../../reference/lexical_analysis.rst:71

msgid ""

"A comment starts with a hash character (``#``) that is not part of a string "

"literal, and ends at the end of the physical line. A comment signifies the "

"end of the logical line unless the implicit line joining rules are invoked. "

"Comments are ignored by the syntax."

msgstr ""

#: ../../reference/lexical_analysis.rst:80

msgid "Encoding declarations"

msgstr ""

#: ../../reference/lexical_analysis.rst:85

msgid ""

"If a comment in the first or second line of the Python script matches the "

"regular expression ``coding[=:]\\s*([-\\w.]+)``, this comment is processed "

"as an encoding declaration; the first group of this expression names the "

"encoding of the source code file. The encoding declaration must appear on a "

"line of its own. If it is the second line, the first line must also be a "

"comment-only line. The recommended forms of an encoding expression are ::"

msgstr ""

#: ../../reference/lexical_analysis.rst:92

msgid "# -*- coding: <encoding-name> -*-"

msgstr "# -*- coding: <encoding-name> -*-"

#: ../../reference/lexical_analysis.rst:94

msgid "which is recognized also by GNU Emacs, and ::"

msgstr ""

#: ../../reference/lexical_analysis.rst:96

msgid "# vim:fileencoding=<encoding-name>"

msgstr "# vim:fileencoding=<encoding-name>"

#: ../../reference/lexical_analysis.rst:98

msgid "which is recognized by Bram Moolenaar's VIM."

msgstr ""

#: ../../reference/lexical_analysis.rst:100

msgid ""

"If no encoding declaration is found, the default encoding is UTF-8. If the "

"implicit or explicit encoding of a file is UTF-8, an initial UTF-8 byte-"

"order mark (``b'\\xef\\xbb\\xbf'``) is ignored rather than being a syntax "

"error."

msgstr ""

#: ../../reference/lexical_analysis.rst:104

msgid ""

"If an encoding is declared, the encoding name must be recognized by Python "

"(see :ref:`standard-encodings`). The encoding is used for all lexical "

"analysis, including string literals, comments and identifiers."

msgstr ""

#: ../../reference/lexical_analysis.rst:113

msgid "Explicit line joining"

msgstr ""

#: ../../reference/lexical_analysis.rst:117

msgid ""

"Two or more physical lines may be joined into logical lines using backslash "

"characters (``\\``), as follows: when a physical line ends in a backslash "

"that is not part of a string literal or comment, it is joined with the "

"following forming a single logical line, deleting the backslash and the "

"following end-of-line character. For example::"

msgstr ""

#: ../../reference/lexical_analysis.rst:123

msgid ""

"if 1900 < year < 2100 and 1 <= month <= 12 \\\n"

" and 1 <= day <= 31 and 0 <= hour < 24 \\\n"

" and 0 <= minute < 60 and 0 <= second < 60: # Looks like a valid date\n"

" return 1"

msgstr ""

"if 1900 < year < 2100 and 1 <= month <= 12 \\\n"

" and 1 <= day <= 31 and 0 <= hour < 24 \\\n"

" and 0 <= minute < 60 and 0 <= second < 60: # 看起來像個有效日期\n"

" return 1"

#: ../../reference/lexical_analysis.rst:128

msgid ""

"A line ending in a backslash cannot carry a comment. A backslash does not "

"continue a comment. A backslash does not continue a token except for string "

"literals (i.e., tokens other than string literals cannot be split across "

"physical lines using a backslash). A backslash is illegal elsewhere on a "

"line outside a string literal."

msgstr ""

#: ../../reference/lexical_analysis.rst:138

msgid "Implicit line joining"

msgstr ""

#: ../../reference/lexical_analysis.rst:140

msgid ""

"Expressions in parentheses, square brackets or curly braces can be split "

"over more than one physical line without using backslashes. For example::"

msgstr ""

#: ../../reference/lexical_analysis.rst:143

msgid ""

"month_names = ['Januari', 'Februari', 'Maart', # These are the\n"

" 'April', 'Mei', 'Juni', # Dutch names\n"

" 'Juli', 'Augustus', 'September', # for the months\n"

" 'Oktober', 'November', 'December'] # of the year"

msgstr ""

#: ../../reference/lexical_analysis.rst:148

msgid ""

"Implicitly continued lines can carry comments. The indentation of the "

"continuation lines is not important. Blank continuation lines are allowed. "

"There is no NEWLINE token between implicit continuation lines. Implicitly "

"continued lines can also occur within triple-quoted strings (see below); in "

"that case they cannot carry comments."

msgstr ""

#: ../../reference/lexical_analysis.rst:158

msgid "Blank lines"

msgstr ""

#: ../../reference/lexical_analysis.rst:162

msgid ""

"A logical line that contains only spaces, tabs, formfeeds and possibly a "

"comment, is ignored (i.e., no NEWLINE token is generated). During "

"interactive input of statements, handling of a blank line may differ "

"depending on the implementation of the read-eval-print loop. In the "

"standard interactive interpreter, an entirely blank logical line (i.e. one "

"containing not even whitespace or a comment) terminates a multi-line "

"statement."

msgstr ""

#: ../../reference/lexical_analysis.rst:173

msgid "Indentation"

msgstr ""

#: ../../reference/lexical_analysis.rst:177

msgid ""

"Leading whitespace (spaces and tabs) at the beginning of a logical line is "

"used to compute the indentation level of the line, which in turn is used to "

"determine the grouping of statements."

msgstr ""

#: ../../reference/lexical_analysis.rst:181

msgid ""

"Tabs are replaced (from left to right) by one to eight spaces such that the "

"total number of characters up to and including the replacement is a multiple "

"of eight (this is intended to be the same rule as used by Unix). The total "

"number of spaces preceding the first non-blank character then determines the "

"line's indentation. Indentation cannot be split over multiple physical "

"lines using backslashes; the whitespace up to the first backslash determines "

"the indentation."

msgstr ""

#: ../../reference/lexical_analysis.rst:189

msgid ""

"Indentation is rejected as inconsistent if a source file mixes tabs and "

"spaces in a way that makes the meaning dependent on the worth of a tab in "

"spaces; a :exc:`TabError` is raised in that case."

msgstr ""

#: ../../reference/lexical_analysis.rst:193

msgid ""

"**Cross-platform compatibility note:** because of the nature of text editors "

"on non-UNIX platforms, it is unwise to use a mixture of spaces and tabs for "

"the indentation in a single source file. It should also be noted that "

"different platforms may explicitly limit the maximum indentation level."

msgstr ""

#: ../../reference/lexical_analysis.rst:198

msgid ""

"A formfeed character may be present at the start of the line; it will be "

"ignored for the indentation calculations above. Formfeed characters "

"occurring elsewhere in the leading whitespace have an undefined effect (for "

"instance, they may reset the space count to zero)."

msgstr ""

#: ../../reference/lexical_analysis.rst:205

msgid ""

"The indentation levels of consecutive lines are used to generate INDENT and "

"DEDENT tokens, using a stack, as follows."

msgstr ""

#: ../../reference/lexical_analysis.rst:208

msgid ""

"Before the first line of the file is read, a single zero is pushed on the "

"stack; this will never be popped off again. The numbers pushed on the stack "

"will always be strictly increasing from bottom to top. At the beginning of "

"each logical line, the line's indentation level is compared to the top of "

"the stack. If it is equal, nothing happens. If it is larger, it is pushed on "

"the stack, and one INDENT token is generated. If it is smaller, it *must* "

"be one of the numbers occurring on the stack; all numbers on the stack that "

"are larger are popped off, and for each number popped off a DEDENT token is "

"generated. At the end of the file, a DEDENT token is generated for each "

"number remaining on the stack that is larger than zero."

msgstr ""

#: ../../reference/lexical_analysis.rst:219

msgid ""

"Here is an example of a correctly (though confusingly) indented piece of "

"Python code::"

msgstr ""

#: ../../reference/lexical_analysis.rst:222

msgid ""

"def perm(l):\n"

" # Compute the list of all permutations of l\n"

" if len(l) <= 1:\n"

" return [l]\n"

" r = []\n"

" for i in range(len(l)):\n"

" s = l[:i] + l[i+1:]\n"

" p = perm(s)\n"

" for x in p:\n"

" r.append(l[i:i+1] + x)\n"

" return r"

msgstr ""

#: ../../reference/lexical_analysis.rst:234

msgid "The following example shows various indentation errors::"

msgstr ""

#: ../../reference/lexical_analysis.rst:236

msgid ""

" def perm(l): # error: first line indented\n"

"for i in range(len(l)): # error: not indented\n"

" s = l[:i] + l[i+1:]\n"

" p = perm(l[:i] + l[i+1:]) # error: unexpected indent\n"

" for x in p:\n"

" r.append(l[i:i+1] + x)\n"

" return r # error: inconsistent dedent"

msgstr ""

#: ../../reference/lexical_analysis.rst:244

msgid ""

"(Actually, the first three errors are detected by the parser; only the last "

"error is found by the lexical analyzer --- the indentation of ``return r`` "

"does not match a level popped off the stack.)"

msgstr ""

#: ../../reference/lexical_analysis.rst:252

msgid "Whitespace between tokens"

msgstr ""

#: ../../reference/lexical_analysis.rst:254

msgid ""

"Except at the beginning of a logical line or in string literals, the "

"whitespace characters space, tab and formfeed can be used interchangeably to "

"separate tokens. Whitespace is needed between two tokens only if their "

"concatenation could otherwise be interpreted as a different token (e.g., ab "

"is one token, but a b is two tokens)."

msgstr ""

#: ../../reference/lexical_analysis.rst:264

msgid "Other tokens"

msgstr ""

#: ../../reference/lexical_analysis.rst:266

msgid ""

"Besides NEWLINE, INDENT and DEDENT, the following categories of tokens "

"exist: *identifiers*, *keywords*, *literals*, *operators*, and *delimiters*. "

"Whitespace characters (other than line terminators, discussed earlier) are "

"not tokens, but serve to delimit tokens. Where ambiguity exists, a token "

"comprises the longest possible string that forms a legal token, when read "

"from left to right."

msgstr ""

#: ../../reference/lexical_analysis.rst:276

msgid "Identifiers and keywords"

msgstr ""

#: ../../reference/lexical_analysis.rst:280

msgid ""

"Identifiers (also referred to as *names*) are described by the following "

"lexical definitions."

msgstr ""

#: ../../reference/lexical_analysis.rst:283

msgid ""

"The syntax of identifiers in Python is based on the Unicode standard annex "

"UAX-31, with elaboration and changes as defined below; see also :pep:`3131` "

"for further details."

msgstr ""

#: ../../reference/lexical_analysis.rst:287

msgid ""

"Within the ASCII range (U+0001..U+007F), the valid characters for "

"identifiers include the uppercase and lowercase letters ``A`` through ``Z``, "

"the underscore ``_`` and, except for the first character, the digits ``0`` "

"through ``9``. Python 3.0 introduced additional characters from outside the "

"ASCII range (see :pep:`3131`). For these characters, the classification "

"uses the version of the Unicode Character Database as included in the :mod:"

"`unicodedata` module."

msgstr ""

#: ../../reference/lexical_analysis.rst:295

msgid "Identifiers are unlimited in length. Case is significant."

msgstr ""

#: ../../reference/lexical_analysis.rst:304

msgid "The Unicode category codes mentioned above stand for:"

msgstr ""

#: ../../reference/lexical_analysis.rst:306

msgid "*Lu* - uppercase letters"

msgstr "*Lu* - 大寫字母"

#: ../../reference/lexical_analysis.rst:307

msgid "*Ll* - lowercase letters"

msgstr "*Ll* - 小寫字母"

#: ../../reference/lexical_analysis.rst:308

msgid "*Lt* - titlecase letters"

msgstr ""

#: ../../reference/lexical_analysis.rst:309

msgid "*Lm* - modifier letters"

msgstr ""

#: ../../reference/lexical_analysis.rst:310

msgid "*Lo* - other letters"

msgstr "*Lo* - 其他字母"

#: ../../reference/lexical_analysis.rst:311

msgid "*Nl* - letter numbers"

msgstr ""

#: ../../reference/lexical_analysis.rst:312

msgid "*Mn* - nonspacing marks"

msgstr ""

#: ../../reference/lexical_analysis.rst:313

msgid "*Mc* - spacing combining marks"

msgstr ""

#: ../../reference/lexical_analysis.rst:314

msgid "*Nd* - decimal numbers"

msgstr "*Nd* - 十進位數字"

#: ../../reference/lexical_analysis.rst:315

msgid "*Pc* - connector punctuations"

msgstr ""

#: ../../reference/lexical_analysis.rst:316

msgid ""

"*Other_ID_Start* - explicit list of characters in `PropList.txt <https://www."

"unicode.org/Public/15.1.0/ucd/PropList.txt>`_ to support backwards "

"compatibility"

msgstr ""

#: ../../reference/lexical_analysis.rst:319

msgid "*Other_ID_Continue* - likewise"

msgstr ""

#: ../../reference/lexical_analysis.rst:321

msgid ""

"All identifiers are converted into the normal form NFKC while parsing; "

"comparison of identifiers is based on NFKC."

msgstr ""

#: ../../reference/lexical_analysis.rst:324

msgid ""

"A non-normative HTML file listing all valid identifier characters for "

"Unicode 15.1.0 can be found at https://www.unicode.org/Public/15.1.0/ucd/"

"DerivedCoreProperties.txt"

msgstr ""

#: ../../reference/lexical_analysis.rst:332

msgid "Keywords"

msgstr "關鍵字"

#: ../../reference/lexical_analysis.rst:338

msgid ""

"The following identifiers are used as reserved words, or *keywords* of the "

"language, and cannot be used as ordinary identifiers. They must be spelled "

"exactly as written here:"

msgstr ""

#: ../../reference/lexical_analysis.rst:342

msgid ""

"False await else import pass\n"

"None break except in raise\n"

"True class finally is return\n"

"and continue for lambda try\n"

"as def from nonlocal while\n"

"assert del global not with\n"

"async elif if or yield"

msgstr ""

"False await else import pass\n"

"None break except in raise\n"

"True class finally is return\n"

"and continue for lambda try\n"

"as def from nonlocal while\n"

"assert del global not with\n"

"async elif if or yield"

#: ../../reference/lexical_analysis.rst:356

msgid "Soft Keywords"

msgstr "軟關鍵字"

#: ../../reference/lexical_analysis.rst:362

msgid ""

"Some identifiers are only reserved under specific contexts. These are known "

"as *soft keywords*. The identifiers ``match``, ``case``, ``type`` and ``_`` "

"can syntactically act as keywords in certain contexts, but this distinction "

"is done at the parser level, not when tokenizing."

msgstr ""

#: ../../reference/lexical_analysis.rst:367

msgid ""

"As soft keywords, their use in the grammar is possible while still "

"preserving compatibility with existing code that uses these names as "

"identifier names."

msgstr ""

#: ../../reference/lexical_analysis.rst:371

msgid ""

"``match``, ``case``, and ``_`` are used in the :keyword:`match` statement. "

"``type`` is used in the :keyword:`type` statement."

msgstr ""

#: ../../reference/lexical_analysis.rst:374

msgid "``type`` is now a soft keyword."

msgstr "``type`` 現在是軟關鍵字。"

#: ../../reference/lexical_analysis.rst:383

msgid "Reserved classes of identifiers"

msgstr ""

#: ../../reference/lexical_analysis.rst:385

msgid ""

"Certain classes of identifiers (besides keywords) have special meanings. "

"These classes are identified by the patterns of leading and trailing "

"underscore characters:"

msgstr ""

#: ../../reference/lexical_analysis.rst:389

msgid "``_*``"

msgstr "``_*``"

#: ../../reference/lexical_analysis.rst:390

msgid "Not imported by ``from module import *``."

msgstr ""

#: ../../reference/lexical_analysis.rst:392

msgid "``_``"

msgstr "``_``"

#: ../../reference/lexical_analysis.rst:393

msgid ""

"In a ``case`` pattern within a :keyword:`match` statement, ``_`` is a :ref:"

"`soft keyword <soft-keywords>` that denotes a :ref:`wildcard <wildcard-"

"patterns>`."

msgstr ""

#: ../../reference/lexical_analysis.rst:397

msgid ""

"Separately, the interactive interpreter makes the result of the last "

"evaluation available in the variable ``_``. (It is stored in the :mod:"

"`builtins` module, alongside built-in functions like ``print``.)"

msgstr ""

#: ../../reference/lexical_analysis.rst:402

msgid ""

"Elsewhere, ``_`` is a regular identifier. It is often used to name "

"\"special\" items, but it is not special to Python itself."

msgstr ""

#: ../../reference/lexical_analysis.rst:407

msgid ""

"The name ``_`` is often used in conjunction with internationalization; refer "

"to the documentation for the :mod:`gettext` module for more information on "

"this convention."

msgstr ""

#: ../../reference/lexical_analysis.rst:411

msgid "It is also commonly used for unused variables."

msgstr ""

#: ../../reference/lexical_analysis.rst:413

msgid "``__*__``"

msgstr "``__*__``"

#: ../../reference/lexical_analysis.rst:414

msgid ""

"System-defined names, informally known as \"dunder\" names. These names are "

"defined by the interpreter and its implementation (including the standard "

"library). Current system names are discussed in the :ref:`specialnames` "

"section and elsewhere. More will likely be defined in future versions of "

"Python. *Any* use of ``__*__`` names, in any context, that does not follow "

"explicitly documented use, is subject to breakage without warning."

msgstr ""

#: ../../reference/lexical_analysis.rst:421

msgid "``__*``"

msgstr "``__*``"

#: ../../reference/lexical_analysis.rst:422

msgid ""

"Class-private names. Names in this category, when used within the context "

"of a class definition, are re-written to use a mangled form to help avoid "

"name clashes between \"private\" attributes of base and derived classes. See "

"section :ref:`atom-identifiers`."

msgstr ""

#: ../../reference/lexical_analysis.rst:431

msgid "Literals"

msgstr ""

#: ../../reference/lexical_analysis.rst:435

msgid "Literals are notations for constant values of some built-in types."

msgstr ""

#: ../../reference/lexical_analysis.rst:446

msgid "String and Bytes literals"

msgstr ""

#: ../../reference/lexical_analysis.rst:448

msgid "String literals are described by the following lexical definitions:"

msgstr ""

#: ../../reference/lexical_analysis.rst:473

msgid ""

"One syntactic restriction not indicated by these productions is that "

"whitespace is not allowed between the :token:`~python-grammar:stringprefix` "

"or :token:`~python-grammar:bytesprefix` and the rest of the literal. The "

"source character set is defined by the encoding declaration; it is UTF-8 if "

"no encoding declaration is given in the source file; see section :ref:"

"`encodings`."

msgstr ""

#: ../../reference/lexical_analysis.rst:483

msgid ""

"In plain English: Both types of literals can be enclosed in matching single "

"quotes (``'``) or double quotes (``\"``). They can also be enclosed in "

"matching groups of three single or double quotes (these are generally "

"referred to as *triple-quoted strings*). The backslash (``\\``) character is "

"used to give special meaning to otherwise ordinary characters like ``n``, "

"which means 'newline' when escaped (``\\n``). It can also be used to escape "

"characters that otherwise have a special meaning, such as newline, backslash "

"itself, or the quote character. See :ref:`escape sequences <escape-"

"sequences>` below for examples."

msgstr ""

#: ../../reference/lexical_analysis.rst:496

msgid ""

"Bytes literals are always prefixed with ``'b'`` or ``'B'``; they produce an "

"instance of the :class:`bytes` type instead of the :class:`str` type. They "

"may only contain ASCII characters; bytes with a numeric value of 128 or "

"greater must be expressed with escapes."

msgstr ""

#: ../../reference/lexical_analysis.rst:505

msgid ""

"Both string and bytes literals may optionally be prefixed with a letter "

"``'r'`` or ``'R'``; such constructs are called :dfn:`raw string literals` "

"and :dfn:`raw bytes literals` respectively and treat backslashes as literal "

"characters. As a result, in raw string literals, ``'\\U'`` and ``'\\u'`` "

"escapes are not treated specially."

msgstr ""

#: ../../reference/lexical_analysis.rst:511

msgid ""

"The ``'rb'`` prefix of raw bytes literals has been added as a synonym of "

"``'br'``."

msgstr ""

#: ../../reference/lexical_analysis.rst:515

msgid ""

"Support for the unicode legacy literal (``u'value'``) was reintroduced to "

"simplify the maintenance of dual Python 2.x and 3.x codebases. See :pep:"

"`414` for more information."

msgstr ""

#: ../../reference/lexical_analysis.rst:523

msgid ""

"A string literal with ``'f'`` or ``'F'`` in its prefix is a :dfn:`formatted "

"string literal`; see :ref:`f-strings`. The ``'f'`` may be combined with "

"``'r'``, but not with ``'b'`` or ``'u'``, therefore raw formatted strings "

"are possible, but formatted bytes literals are not."

msgstr ""

#: ../../reference/lexical_analysis.rst:528

msgid ""

"In triple-quoted literals, unescaped newlines and quotes are allowed (and "

"are retained), except that three unescaped quotes in a row terminate the "

"literal. (A \"quote\" is the character used to open the literal, i.e. "

"either ``'`` or ``\"``.)"

msgstr ""

#: ../../reference/lexical_analysis.rst:551

msgid "Escape sequences"

msgstr "跳脫序列"

#: ../../reference/lexical_analysis.rst:553

msgid ""

"Unless an ``'r'`` or ``'R'`` prefix is present, escape sequences in string "

"and bytes literals are interpreted according to rules similar to those used "

"by Standard C. The recognized escape sequences are:"

msgstr ""

#: ../../reference/lexical_analysis.rst:558

#: ../../reference/lexical_analysis.rst:591

msgid "Escape Sequence"

msgstr ""

#: ../../reference/lexical_analysis.rst:558

#: ../../reference/lexical_analysis.rst:591

msgid "Meaning"

msgstr "含義"

#: ../../reference/lexical_analysis.rst:558

#: ../../reference/lexical_analysis.rst:591

msgid "Notes"

msgstr "註解"

#: ../../reference/lexical_analysis.rst:560

msgid "``\\``\\ <newline>"

msgstr "``\\``\\ <newline>"

#: ../../reference/lexical_analysis.rst:560

msgid "Backslash and newline ignored"

msgstr ""

#: ../../reference/lexical_analysis.rst:560

msgid "\\(1)"

msgstr "\\(1)"

#: ../../reference/lexical_analysis.rst:562

msgid "``\\\\``"

msgstr "``\\\\``"

#: ../../reference/lexical_analysis.rst:562

msgid "Backslash (``\\``)"

msgstr ""

#: ../../reference/lexical_analysis.rst:564

msgid "``\\'``"

msgstr "``\\'``"

#: ../../reference/lexical_analysis.rst:564

msgid "Single quote (``'``)"

msgstr "單引號 (``'``)"

#: ../../reference/lexical_analysis.rst:566

msgid "``\\\"``"

msgstr "``\\\"``"

#: ../../reference/lexical_analysis.rst:566

msgid "Double quote (``\"``)"

msgstr "雙引號 (``\"``)"

#: ../../reference/lexical_analysis.rst:568

msgid "``\\a``"

msgstr "``\\a``"

#: ../../reference/lexical_analysis.rst:568

msgid "ASCII Bell (BEL)"

msgstr ""

#: ../../reference/lexical_analysis.rst:570

msgid "``\\b``"

msgstr "``\\b``"

#: ../../reference/lexical_analysis.rst:570

msgid "ASCII Backspace (BS)"

msgstr ""

#: ../../reference/lexical_analysis.rst:572

msgid "``\\f``"

msgstr "``\\f``"

#: ../../reference/lexical_analysis.rst:572

msgid "ASCII Formfeed (FF)"

msgstr ""

#: ../../reference/lexical_analysis.rst:574

msgid "``\\n``"

msgstr "``\\n``"

#: ../../reference/lexical_analysis.rst:574

msgid "ASCII Linefeed (LF)"

msgstr ""

#: ../../reference/lexical_analysis.rst:576

msgid "``\\r``"

msgstr "``\\r``"

#: ../../reference/lexical_analysis.rst:576

msgid "ASCII Carriage Return (CR)"

msgstr ""

#: ../../reference/lexical_analysis.rst:578

msgid "``\\t``"

msgstr "``\\t``"

#: ../../reference/lexical_analysis.rst:578

msgid "ASCII Horizontal Tab (TAB)"

msgstr ""

#: ../../reference/lexical_analysis.rst:580

msgid "``\\v``"

msgstr "``\\v``"

#: ../../reference/lexical_analysis.rst:580

msgid "ASCII Vertical Tab (VT)"

msgstr ""

#: ../../reference/lexical_analysis.rst:582

msgid ":samp:`\\\\\\\\{ooo}`"

msgstr ":samp:`\\\\\\\\{ooo}`"

#: ../../reference/lexical_analysis.rst:582

msgid "Character with octal value *ooo*"

msgstr ""

#: ../../reference/lexical_analysis.rst:582

msgid "(2,4)"

msgstr "(2,4)"

#: ../../reference/lexical_analysis.rst:585

msgid ":samp:`\\\\x{hh}`"

msgstr ":samp:`\\\\x{hh}`"

#: ../../reference/lexical_analysis.rst:585

msgid "Character with hex value *hh*"

msgstr ""

#: ../../reference/lexical_analysis.rst:585

msgid "(3,4)"

msgstr "(3,4)"

#: ../../reference/lexical_analysis.rst:588

msgid "Escape sequences only recognized in string literals are:"

msgstr ""

#: ../../reference/lexical_analysis.rst:593

msgid ":samp:`\\\\N\\\\{{name}\\\\}`"

msgstr ":samp:`\\\\N\\\\{{name}\\\\}`"

#: ../../reference/lexical_analysis.rst:593

msgid "Character named *name* in the Unicode database"

msgstr ""

#: ../../reference/lexical_analysis.rst:593

msgid "\\(5)"

msgstr "\\(5)"

#: ../../reference/lexical_analysis.rst:596

msgid ":samp:`\\\\u{xxxx}`"

msgstr ":samp:`\\\\u{xxxx}`"

#: ../../reference/lexical_analysis.rst:596

msgid "Character with 16-bit hex value *xxxx*"

msgstr ""

#: ../../reference/lexical_analysis.rst:596

msgid "\\(6)"

msgstr "\\(6)"

#: ../../reference/lexical_analysis.rst:599

msgid ":samp:`\\\\U{xxxxxxxx}`"

msgstr ":samp:`\\\\U{xxxxxxxx}`"

#: ../../reference/lexical_analysis.rst:599

msgid "Character with 32-bit hex value *xxxxxxxx*"

msgstr ""

#: ../../reference/lexical_analysis.rst:599

msgid "\\(7)"

msgstr "\\(7)"

#: ../../reference/lexical_analysis.rst:603

msgid "Notes:"

msgstr "註解："

#: ../../reference/lexical_analysis.rst:606

msgid "A backslash can be added at the end of a line to ignore the newline::"

msgstr ""

#: ../../reference/lexical_analysis.rst:608

msgid ""

">>> 'This string will not include \\\n"

"... backslashes or newline characters.'\n"

"'This string will not include backslashes or newline characters.'"

msgstr ""

#: ../../reference/lexical_analysis.rst:612

msgid ""

"The same result can be achieved using :ref:`triple-quoted strings "

"<strings>`, or parentheses and :ref:`string literal concatenation <string-"

"concatenation>`."

msgstr ""

#: ../../reference/lexical_analysis.rst:617

msgid "As in Standard C, up to three octal digits are accepted."

msgstr ""

#: ../../reference/lexical_analysis.rst:619

msgid ""

"Octal escapes with value larger than ``0o377`` produce a :exc:"

"`DeprecationWarning`."

msgstr ""

#: ../../reference/lexical_analysis.rst:623

msgid ""

"Octal escapes with value larger than ``0o377`` produce a :exc:"

"`SyntaxWarning`. In a future Python version they will be eventually a :exc:"

"`SyntaxError`."

msgstr ""

#: ../../reference/lexical_analysis.rst:629

msgid "Unlike in Standard C, exactly two hex digits are required."

msgstr ""

#: ../../reference/lexical_analysis.rst:632

msgid ""

"In a bytes literal, hexadecimal and octal escapes denote the byte with the "

"given value. In a string literal, these escapes denote a Unicode character "

"with the given value."

msgstr ""

#: ../../reference/lexical_analysis.rst:637

msgid "Support for name aliases [#]_ has been added."

msgstr ""

#: ../../reference/lexical_analysis.rst:641

msgid "Exactly four hex digits are required."

msgstr ""

#: ../../reference/lexical_analysis.rst:644

msgid ""

"Any Unicode character can be encoded this way. Exactly eight hex digits are "

"required."

msgstr ""

#: ../../reference/lexical_analysis.rst:650

msgid ""

"Unlike Standard C, all unrecognized escape sequences are left in the string "

"unchanged, i.e., *the backslash is left in the result*. (This behavior is "

"useful when debugging: if an escape sequence is mistyped, the resulting "

"output is more easily recognized as broken.) It is also important to note "

"that the escape sequences only recognized in string literals fall into the "

"category of unrecognized escapes for bytes literals."

msgstr ""

#: ../../reference/lexical_analysis.rst:657

msgid "Unrecognized escape sequences produce a :exc:`DeprecationWarning`."

msgstr ""

#: ../../reference/lexical_analysis.rst:660

msgid ""

"Unrecognized escape sequences produce a :exc:`SyntaxWarning`. In a future "

"Python version they will be eventually a :exc:`SyntaxError`."

msgstr ""

#: ../../reference/lexical_analysis.rst:664

msgid ""

"Even in a raw literal, quotes can be escaped with a backslash, but the "

"backslash remains in the result; for example, ``r\"\\\"\"`` is a valid "

"string literal consisting of two characters: a backslash and a double quote; "

"``r\"\\\"`` is not a valid string literal (even a raw string cannot end in "

"an odd number of backslashes). Specifically, *a raw literal cannot end in a "

"single backslash* (since the backslash would escape the following quote "

"character). Note also that a single backslash followed by a newline is "

"interpreted as those two characters as part of the literal, *not* as a line "

"continuation."

msgstr ""

#: ../../reference/lexical_analysis.rst:677

msgid "String literal concatenation"

msgstr ""

#: ../../reference/lexical_analysis.rst:679

msgid ""

"Multiple adjacent string or bytes literals (delimited by whitespace), "

"possibly using different quoting conventions, are allowed, and their meaning "

"is the same as their concatenation. Thus, ``\"hello\" 'world'`` is "

"equivalent to ``\"helloworld\"``. This feature can be used to reduce the "

"number of backslashes needed, to split long strings conveniently across long "

"lines, or even to add comments to parts of strings, for example::"

msgstr ""

#: ../../reference/lexical_analysis.rst:686

msgid ""

"re.compile(\"[A-Za-z_]\" # letter or underscore\n"

" \"[A-Za-z0-9_]*\" # letter, digit or underscore\n"

" )"

msgstr ""

#: ../../reference/lexical_analysis.rst:690

msgid ""

"Note that this feature is defined at the syntactical level, but implemented "

"at compile time. The '+' operator must be used to concatenate string "

"expressions at run time. Also note that literal concatenation can use "

"different quoting styles for each component (even mixing raw strings and "

"triple quoted strings), and formatted string literals may be concatenated "

"with plain string literals."

msgstr ""

#: ../../reference/lexical_analysis.rst:713

msgid "f-strings"

msgstr "f-string（f 字串）"

#: ../../reference/lexical_analysis.rst:717

msgid ""

"A :dfn:`formatted string literal` or :dfn:`f-string` is a string literal "

"that is prefixed with ``'f'`` or ``'F'``. These strings may contain "

"replacement fields, which are expressions delimited by curly braces ``{}``. "

"While other string literals always have a constant value, formatted strings "

"are really expressions evaluated at run time."

msgstr ""

#: ../../reference/lexical_analysis.rst:723

msgid ""

"Escape sequences are decoded like in ordinary string literals (except when a "

"literal is also marked as a raw string). After decoding, the grammar for "