lexical_analysis.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001 Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# python-doc bot, 2025
# Hengky Kurniawan, 2025
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.15\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-05-27 16:58+0000\n"
"PO-Revision-Date: 2025-09-16 00:02+0000\n"
"Last-Translator: Hengky Kurniawan, 2025\n"
"Language-Team: Indonesian (https://app.transifex.com/python-doc/teams/5390/"
"id/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: id\n"
"Plural-Forms: nplurals=1; plural=0;\n"

msgid "Lexical analysis"
msgstr ""

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 produces "
"these tokens."
msgstr ""

msgid ""
"The lexical analyzer determines the program text's :ref:`encoding "
"<encodings>` (UTF-8 by default), and decodes the text into :ref:`source "
"characters <lexical-source-character>`. If the text cannot be decoded, a :"
"exc:`SyntaxError` is raised."
msgstr ""

msgid ""
"Next, the lexical analyzer uses the source characters to generate a stream "
"of tokens. The type of a generated token generally depends on the next "
"source character to be processed. Similarly, other special behavior of the "
"analyzer depends on the first source character that hasn't yet been "
"processed. The following table gives a quick summary of these source "
"characters, with links to sections that contain more information."
msgstr ""

msgid "Character"
msgstr "Karakter"

msgid "Next token (or other relevant documentation)"
msgstr ""

msgid "space"
msgstr ""

msgid "tab"
msgstr ""

msgid "formfeed"
msgstr ""

msgid ":ref:`Whitespace <whitespace>`"
msgstr ""

msgid "CR, LF"
msgstr ""

msgid ":ref:`New line <line-structure>`"
msgstr ""

msgid ":ref:`Indentation <indentation>`"
msgstr ""

msgid "backslash (``\\``)"
msgstr ""

msgid ":ref:`Explicit line joining <explicit-joining>`"
msgstr ""

msgid "(Also significant in :ref:`string escape sequences <escape-sequences>`)"
msgstr ""

msgid "hash (``#``)"
msgstr ""

msgid ":ref:`Comment <comments>`"
msgstr ""

msgid "quote (``'``, ``\"``)"
msgstr ""

msgid ":ref:`String literal <strings>`"
msgstr ""

msgid "ASCII letter (``a``-``z``, ``A``-``Z``)"
msgstr ""

msgid "non-ASCII character"
msgstr ""

msgid ":ref:`Name <identifiers>`"
msgstr ""

msgid "Prefixed :ref:`string or bytes literal <strings>`"
msgstr ""

msgid "underscore (``_``)"
msgstr ""

msgid "(Can also be part of :ref:`numeric literals <numbers>`)"
msgstr ""

msgid "number (``0``-``9``)"
msgstr ""

msgid ":ref:`Numeric literal <numbers>`"
msgstr ""

msgid "dot (``.``)"
msgstr ""

msgid ":ref:`Operator <operators>`"
msgstr ""

msgid "question mark (``?``)"
msgstr ""

msgid "dollar (``$``)"
msgstr ""

msgid "backquote (``​`​``)"
msgstr ""

msgid "control character"
msgstr ""

msgid "Error (outside string literals and comments)"
msgstr ""

msgid "other printing character"
msgstr ""

msgid ":ref:`Operator or delimiter <operators>`"
msgstr ""

msgid "end of file"
msgstr ""

msgid ":ref:`End marker <endmarker-token>`"
msgstr ""

msgid "Line structure"
msgstr ""

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

msgid "Logical lines"
msgstr ""

msgid ""
"The end of a logical line is represented by the token :data:`~token."
"NEWLINE`. Statements cannot cross logical line boundaries except where :data:"
"`!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 :ref:`explicit <explicit-joining>` or :ref:`implicit "
"<implicit-joining>` *line joining* rules."
msgstr ""

msgid "Physical lines"
msgstr ""

msgid ""
"A physical line is a sequence of characters terminated by one the following "
"end-of-line sequences:"
msgstr ""

msgid "the Unix form using ASCII LF (linefeed),"
msgstr ""

msgid ""
"the Windows form using the ASCII sequence CR LF (return followed by "
"linefeed),"
msgstr ""

msgid "the '`Classic Mac OS`__' form using the ASCII CR (return) character."
msgstr ""

msgid ""
"Regardless of platform, each of these sequences is replaced by a single "
"ASCII LF (linefeed) character. (This is done even inside :ref:`string "
"literals <strings>`.) Each line can use any of the sequences; they do not "
"need to be consistent within a file."
msgstr ""

msgid ""
"The end of input also serves as an implicit terminator for the final "
"physical line."
msgstr ""

msgid "Formally:"
msgstr ""

msgid "Comments"
msgstr ""

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 ""

msgid "Encoding declarations"
msgstr ""

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 ""

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

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

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

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

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 ""

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 ""

msgid ""
"All lexical analysis, including string literals, comments and identifiers, "
"works on Unicode text decoded using the source encoding. Any Unicode code "
"point, except the NUL control character, can appear in Python source."
msgstr ""

msgid "Explicit line joining"
msgstr ""

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 ""

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 ""

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 ""

msgid "Implicit line joining"
msgstr ""

msgid ""
"Expressions in parentheses, square brackets or curly braces can be split "
"over more than one physical line without using backslashes. For example::"
msgstr ""

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 ""

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 ""

msgid "Blank lines"
msgstr ""

msgid ""
"A logical line that contains only spaces, tabs, formfeeds and possibly a "
"comment, is ignored (i.e., no :data:`~token.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 (that is, one "
"containing not even whitespace or a comment) terminates a multi-line "
"statement."
msgstr ""

msgid "Indentation"
msgstr ""

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 ""

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 ""

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 ""

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 ""

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 ""

msgid ""
"The indentation levels of consecutive lines are used to generate :data:"
"`~token.INDENT` and :data:`~token.DEDENT` tokens, using a stack, as follows."
msgstr ""

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 :data:`!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 :data:"
"`!DEDENT` token is generated. At the end of the file, a :data:`!DEDENT` "
"token is generated for each number remaining on the stack that is larger "
"than zero."
msgstr ""

msgid ""
"Here is an example of a correctly (though confusingly) indented piece of "
"Python code::"
msgstr ""

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 ""

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

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 ""

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 ""

msgid "Whitespace between tokens"
msgstr ""

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:"
msgstr ""

msgid ""
"Whitespace is needed between two tokens only if their concatenation could "
"otherwise be interpreted as a different token. For example, ``ab`` is one "
"token, but ``a b`` is two tokens. However, ``+a`` and ``+ a`` both produce "
"two tokens, ``+`` and ``a``, as ``+a`` is not a valid token."
msgstr ""

msgid "End marker"
msgstr ""

msgid ""
"At the end of non-interactive input, the lexical analyzer generates an :data:"
"`~token.ENDMARKER` token."
msgstr ""

msgid "Other tokens"
msgstr ""

msgid ""
"Besides :data:`~token.NEWLINE`, :data:`~token.INDENT` and :data:`~token."
"DEDENT`, the following categories of tokens exist: *identifiers* and "
"*keywords* (:data:`~token.NAME`), *literals* (such as :data:`~token.NUMBER` "
"and :data:`~token.STRING`), and other symbols (*operators* and "
"*delimiters*, :data:`~token.OP`). Whitespace characters (other than logical "
"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 ""

msgid "Names (identifiers and keywords)"
msgstr ""

msgid ""
":data:`~token.NAME` tokens represent *identifiers*, *keywords*, and *soft "
"keywords*."
msgstr ""

msgid "Names are composed of the following characters:"
msgstr ""

msgid "uppercase and lowercase letters (``A-Z`` and ``a-z``),"
msgstr ""

msgid "the underscore (``_``),"
msgstr ""

msgid ""
"digits (``0`` through ``9``), which cannot appear as the first character, and"
msgstr ""

msgid ""
"non-ASCII characters. Valid names may only contain \"letter-like\" and "
"\"digit-like\" characters; see :ref:`lexical-names-nonascii` for details."
msgstr ""

msgid ""
"Names must contain at least one character, but have no upper length limit. "
"Case is significant."
msgstr ""

msgid "Formally, names are described by the following lexical definitions:"
msgstr ""

msgid ""
"Note that not all names matched by this grammar are valid; see :ref:`lexical-"
"names-nonascii` for details."
msgstr ""

msgid "Keywords"
msgstr ""

msgid ""
"The following names 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 ""

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 ""

msgid "Soft Keywords"
msgstr ""

msgid ""
"Some names are only reserved under specific contexts. These are known as "
"*soft keywords*:"
msgstr ""

msgid ""
"``match``, ``case``, and ``_``, when used in the :keyword:`match` statement."
msgstr ""

msgid "``type``, when used in the :keyword:`type` statement."
msgstr ""

msgid "``lazy``, when used before an :keyword:`import` statement."
msgstr ""

msgid ""
"These syntactically act as keywords in their specific contexts, but this "
"distinction is done at the parser level, not when tokenizing."
msgstr ""

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 ""

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

msgid "``lazy`` is now a soft keyword."
msgstr ""

msgid "Reserved classes of identifiers"
msgstr ""

msgid ""
"Certain classes of identifiers (besides keywords) have special meanings.  "
"These classes are identified by the patterns of leading and trailing "
"underscore characters:"
msgstr ""

msgid "``_*``"
msgstr ""

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

msgid "``_``"
msgstr ""

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 ""

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 ""

msgid ""
"Elsewhere, ``_`` is a regular identifier. It is often used to name "
"\"special\" items, but it is not special to Python itself."
msgstr ""

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 ""

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

msgid "``__*__``"
msgstr ""

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 ""

msgid "``__*``"
msgstr ""

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 ""

msgid "Non-ASCII characters in names"
msgstr ""

msgid ""
"Names that contain non-ASCII characters need additional normalization and "
"validation beyond the rules and grammar explained :ref:`above "
"<identifiers>`. For example, ``ř_1``, ``蛇``, or ``साँप``  are valid names, "
"but ``r〰2``, ``€``, or ``🐍`` are not."
msgstr ""

msgid "This section explains the exact rules."
msgstr ""

msgid ""
"All names are converted into the `normalization form`_ NFKC while parsing. "
"This means that, for example, some typographic variants of characters are "
"converted to their \"basic\" form. For example, ``fiⁿₐˡᵢᶻₐᵗᵢᵒₙ`` normalizes "
"to ``finalization``, so Python treats them as the same name::"
msgstr ""

msgid ""
">>> fiⁿₐˡᵢᶻₐᵗᵢᵒₙ = 3\n"
">>> finalization\n"
"3"
msgstr ""

msgid ""
"Normalization is done at the lexical level only. Run-time functions that "
"take names as *strings* generally do not normalize their arguments. For "
"example, the variable defined above is accessible at run time in the :func:"
"`globals` dictionary as ``globals()[\"finalization\"]`` but not ``globals()"
"[\"fiⁿₐˡᵢᶻₐᵗᵢᵒₙ\"]``."
msgstr ""

msgid ""
"Similarly to how ASCII-only names must contain only letters, digits and the "
"underscore, and cannot start with a digit, a valid name must start with a "
"character in the \"letter-like\" set ``xid_start``, and the remaining "
"characters must be in the \"letter- and digit-like\" set ``xid_continue``."
msgstr ""

msgid ""
"These sets are based on the *XID_Start* and *XID_Continue* sets as defined "
"by the Unicode standard annex `UAX-31`_. Python's ``xid_start`` additionally "
"includes the underscore (``_``). Note that Python does not necessarily "
"conform to `UAX-31`_."
msgstr ""

msgid ""
"A non-normative listing of characters in the *XID_Start* and *XID_Continue* "
"sets as defined by Unicode is available in the `DerivedCoreProperties.txt`_ "
"file in the Unicode Character Database. For reference, the construction "
"rules for the ``xid_*`` sets are given below."
msgstr ""

msgid "The set ``id_start`` is defined as the union of:"
msgstr ""

msgid "Unicode category ``<Lu>`` - uppercase letters (includes ``A`` to ``Z``)"
msgstr ""

msgid "Unicode category ``<Ll>`` - lowercase letters (includes ``a`` to ``z``)"
msgstr ""

msgid "Unicode category ``<Lt>`` - titlecase letters"
msgstr ""

msgid "Unicode category ``<Lm>`` - modifier letters"
msgstr ""

msgid "Unicode category ``<Lo>`` - other letters"
msgstr ""

msgid "Unicode category ``<Nl>`` - letter numbers"
msgstr ""

msgid "{``\"_\"``} - the underscore"
msgstr ""

msgid ""
"``<Other_ID_Start>`` - an explicit set of characters in `PropList.txt`_ to "
"support backwards compatibility"
msgstr ""

msgid ""
"The set ``xid_start`` then closes this set under NFKC normalization, by "
"removing all characters whose normalization is not of the form ``id_start "
"id_continue*``."
msgstr ""

msgid "The set ``id_continue`` is defined as the union of:"
msgstr ""

msgid "``id_start`` (see above)"
msgstr ""

msgid "Unicode category ``<Nd>`` - decimal numbers (includes ``0`` to ``9``)"
msgstr ""

msgid "Unicode category ``<Pc>`` - connector punctuations"
msgstr ""

msgid "Unicode category ``<Mn>`` - nonspacing marks"
msgstr ""

msgid "Unicode category ``<Mc>`` - spacing combining marks"
msgstr ""

msgid ""
"``<Other_ID_Continue>`` - another explicit set of characters in `PropList."
"txt`_ to support backwards compatibility"
msgstr ""

msgid "Again, ``xid_continue`` closes this set under NFKC normalization."
msgstr ""

msgid ""
"Unicode categories use the version of the Unicode Character Database as "
"included in the :mod:`unicodedata` module."
msgstr ""

msgid ":pep:`3131` -- Supporting Non-ASCII Identifiers"
msgstr ""

msgid ":pep:`672` -- Unicode-related Security Considerations for Python"
msgstr ""

msgid "Literals"
msgstr ""

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

msgid ""
"In terms of lexical analysis, Python has :ref:`string, bytes <strings>` and :"
"ref:`numeric <numbers>` literals."
msgstr ""

msgid ""
"Other \"literals\" are lexically denoted using :ref:`keywords <keywords>` "
"(``None``, ``True``, ``False``) and the special :ref:`ellipsis token "
"<lexical-ellipsis>` (``...``)."
msgstr ""

msgid "String and Bytes literals"
msgstr ""

msgid ""
"String literals are text enclosed in single quotes (``'``) or double quotes "
"(``\"``). For example:"
msgstr ""

msgid ""
"\"spam\"\n"
"'eggs'"
msgstr ""

msgid ""
"The quote used to start the literal also terminates it, so a string literal "
"can only contain the other quote (except with escape sequences, see below). "
"For example:"
msgstr ""

msgid ""
"'Say \"Hello\", please.'\n"
"\"Don't do that!\""
msgstr ""

msgid ""
"Except for this limitation, the choice of quote character (``'`` or ``\"``) "
"does not affect how the literal is parsed."
msgstr ""

msgid ""
"Inside a string literal, the backslash (``\\``) character introduces an :dfn:"
"`escape sequence`, which has special meaning depending on the character "
"after the backslash. For example, ``\\\"`` denotes the double quote "
"character, and does *not* end the string:"
msgstr ""

msgid ""
">>> print(\"Say \\\"Hello\\\" to everyone!\")\n"
"Say \"Hello\" to everyone!"
msgstr ""

msgid ""
"See :ref:`escape sequences <escape-sequences>` below for a full list of such "
"sequences, and more details."
msgstr ""

msgid "Triple-quoted strings"
msgstr ""

msgid ""
"Strings can also be enclosed in matching groups of three single or double "
"quotes. These are generally referred to as :dfn:`triple-quoted strings`::"
msgstr ""

msgid "\"\"\"This is a triple-quoted string.\"\"\""
msgstr ""

msgid ""
"In triple-quoted literals, unescaped quotes are allowed (and are retained), "
"except that three unescaped quotes in a row terminate the literal, if they "
"are of the same kind (``'`` or ``\"``) used at the start::"
msgstr ""

msgid "\"\"\"This string has \"quotes\" inside.\"\"\""
msgstr ""

msgid "Unescaped newlines are also allowed and retained::"
msgstr ""

msgid ""
"'''This triple-quoted string\n"
"continues on the next line.'''"
msgstr ""

msgid "String prefixes"
msgstr ""

msgid ""
"String literals can have an optional :dfn:`prefix` that influences how the "
"content of the literal is parsed, for example:"
msgstr ""

msgid ""
"b\"data\"\n"
"f'{result=}'"
msgstr ""

msgid "The allowed prefixes are:"
msgstr ""

msgid "``b``: :ref:`Bytes literal <bytes-literal>`"
msgstr ""

msgid "``r``: :ref:`Raw string <raw-strings>`"
msgstr ""

msgid "``f``: :ref:`Formatted string literal <f-strings>` (\"f-string\")"
msgstr ""

msgid "``t``: :ref:`Template string literal <t-strings>` (\"t-string\")"
msgstr ""

msgid "``u``: No effect (allowed for backwards compatibility)"
msgstr ""

msgid "See the linked sections for details on each type."
msgstr ""

msgid ""
"Prefixes are case-insensitive (for example, '``B``' works the same as "
"'``b``'). The '``r``' prefix can be combined with '``f``', '``t``' or "
"'``b``', so '``fr``', '``rf``', '``tr``', '``rt``', '``br``', and '``rb``' "
"are also valid prefixes."
msgstr ""

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

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 ""

msgid "Formal grammar"
msgstr ""

msgid ""
"String literals, except :ref:`\"f-strings\" <f-strings>` and :ref:`\"t-"
"strings\" <t-strings>`, are described by the following lexical definitions."
msgstr ""

msgid ""
"These definitions use :ref:`negative lookaheads <lexical-lookaheads>` (``!"
"``) to indicate that an ending quote ends the literal."
msgstr ""

msgid ""
"Note that as in all lexical definitions, whitespace is significant. In "
"particular, the prefix (if any) must be immediately followed by the starting "
"quote."
msgstr ""

msgid "Escape sequences"
msgstr ""

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 ""

msgid "Escape Sequence"
msgstr ""

msgid "Meaning"
msgstr "Artinya"

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

msgid ":ref:`string-escape-ignore`"
msgstr ""

msgid "``\\\\``"
msgstr ""

msgid ":ref:`Backslash <string-escape-escaped-char>`"
msgstr ""

msgid "``\\'``"
msgstr ""

msgid ":ref:`Single quote <string-escape-escaped-char>`"
msgstr ""

msgid "``\\\"``"
msgstr ""

msgid ":ref:`Double quote <string-escape-escaped-char>`"
msgstr ""

msgid "``\\a``"
msgstr ""

msgid "ASCII Bell (BEL)"
msgstr ""

msgid "``\\b``"
msgstr "``\\b``"

msgid "ASCII Backspace (BS)"
msgstr ""

msgid "``\\f``"
msgstr ""

msgid "ASCII Formfeed (FF)"
msgstr ""

msgid "``\\n``"
msgstr "``\\n``"

msgid "ASCII Linefeed (LF)"
msgstr ""

msgid "``\\r``"
msgstr "``\\r``"

msgid "ASCII Carriage Return (CR)"
msgstr ""

msgid "``\\t``"
msgstr ""

msgid "ASCII Horizontal Tab (TAB)"
msgstr ""

msgid "``\\v``"
msgstr ""

msgid "ASCII Vertical Tab (VT)"
msgstr ""

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

msgid ":ref:`string-escape-oct`"
msgstr ""

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

msgid ":ref:`string-escape-hex`"
msgstr ""

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