reference/lixical_analysis.po -> powrap issues

Author: sba72

reference/lexical_analysis.po

@@ -26,18 +26,18 @@ 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 produces "
-"these tokens."
+"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 ""
 
 #: ../../reference/lexical_analysis.rst:15
 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."
+"characters <lexical-source-character>`. If the text cannot be decoded, "
+"a :exc:`SyntaxError` is raised."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:20
@@ -208,12 +208,12 @@ msgstr ""
 
 #: ../../reference/lexical_analysis.rst:102
 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."
+"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 ""
 
 #: ../../reference/lexical_analysis.rst:113
@@ -441,8 +441,9 @@ msgstr ""
 
 #: ../../reference/lexical_analysis.rst:296
 msgid ""
-"The indentation levels of consecutive lines are used to generate :data:"
-"`~token.INDENT` and :data:`~token.DEDENT` tokens, using a stack, as follows."
+"The indentation levels of consecutive lines are used to "
+"generate :data:`~token.INDENT` and :data:`~token.DEDENT` tokens, using a "
+"stack, as follows."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:300
@@ -454,10 +455,10 @@ msgid ""
 "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."
+"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 ""
 
 #: ../../reference/lexical_analysis.rst:311
@@ -528,8 +529,8 @@ msgstr ""
 
 #: ../../reference/lexical_analysis.rst:367
 msgid ""
-"At the end of non-interactive input, the lexical analyzer generates an :data:"
-"`~token.ENDMARKER` token."
+"At the end of non-interactive input, the lexical analyzer generates "
+"an :data:`~token.ENDMARKER` token."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:374
@@ -538,14 +539,15 @@ msgstr ""
 
 #: ../../reference/lexical_analysis.rst:376
 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."
+"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 ""
 
 #: ../../reference/lexical_analysis.rst:390
@@ -688,16 +690,16 @@ msgstr ""
 
 #: ../../reference/lexical_analysis.rst:491
 msgid ""
-"In a ``case`` pattern within a :keyword:`match` statement, ``_`` is a :ref:"
-"`soft keyword <soft-keywords>` that denotes a :ref:`wildcard <wildcard-"
-"patterns>`."
+"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:495
 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``.)"
+"evaluation available in the variable ``_``. (It is stored in "
+"the :mod:`builtins` module, alongside built-in functions like ``print``.)"
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:500
@@ -778,9 +780,9 @@ 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ⁿₐˡᵢᶻₐᵗᵢᵒₙ\"]``."
+"example, the variable defined above is accessible at run time in "
+"the :func:`globals` dictionary as ``globals()[\"finalization\"]`` but not "
+"``globals()[\"fiⁿₐˡᵢᶻₐᵗᵢᵒₙ\"]``."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:557
@@ -878,8 +880,8 @@ msgstr ""
 
 #: ../../reference/lexical_analysis.rst:596
 msgid ""
-"``<Other_ID_Continue>`` - another explicit set of characters in `PropList."
-"txt`_ to support backwards compatibility"
+"``<Other_ID_Continue>`` - another explicit set of characters in "
+"`PropList.txt`_ to support backwards compatibility"
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:599
@@ -910,8 +912,8 @@ msgstr ""
 
 #: ../../reference/lexical_analysis.rst:624
 msgid ""
-"In terms of lexical analysis, Python has :ref:`string, bytes <strings>` and :"
-"ref:`numeric <numbers>` literals."
+"In terms of lexical analysis, Python has :ref:`string, bytes <strings>` "
+"and :ref:`numeric <numbers>` literals."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:627
@@ -958,10 +960,10 @@ msgstr ""
 
 #: ../../reference/lexical_analysis.rst:660
 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:"
+"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 ""
 
 #: ../../reference/lexical_analysis.rst:666
@@ -1072,8 +1074,8 @@ msgstr ""
 #: ../../reference/lexical_analysis.rst:733
 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."
+"simplify the maintenance of dual Python 2.x and 3.x codebases. "
+"See :pep:`414` for more information."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:739
@@ -1323,15 +1325,15 @@ msgstr ""
 
 #: ../../reference/lexical_analysis.rst:878
 msgid ""
-"Octal escapes with value larger than ``0o377`` (255) produce a :exc:"
-"`DeprecationWarning`."
+"Octal escapes with value larger than ``0o377`` (255) produce "
+"a :exc:`DeprecationWarning`."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:882
 msgid ""
-"Octal escapes with value larger than ``0o377`` (255) produce a :exc:"
-"`SyntaxWarning`. In a future Python version they will raise a :exc:"
-"`SyntaxError`."
+"Octal escapes with value larger than ``0o377`` (255) produce "
+"a :exc:`SyntaxWarning`. In a future Python version they will raise "
+"a :exc:`SyntaxError`."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:890
@@ -1450,8 +1452,8 @@ msgid ""
 ":dfn:`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 escape sequences (typically :ref:"
-"`string-escape-hex` or :ref:`string-escape-oct`):"
+"128 or greater must be expressed with escape sequences "
+"(typically :ref:`string-escape-hex` or :ref:`string-escape-oct`):"
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:984
@@ -1669,7 +1671,7 @@ msgstr ""
 #: ../../reference/lexical_analysis.rst:1148
 msgid "a *conversion specifier* -- ``!s``, ``!r`` or ``!a``; and/or"
 msgstr ""
-"einen *Konvertierungsbezeichner* – ``!s``, ``!r`` oder ``!a``; und/oder"
+"einen *Konvertierungsbezeichner* – ``!s``, ``!r`` oder ``!a``, und/oder"
 
 #: ../../reference/lexical_analysis.rst:1149
 msgid "a *format specifier* prefixed with a colon (``:``)."
@@ -1963,8 +1965,8 @@ msgstr ""
 
 #: ../../reference/lexical_analysis.rst:1414
 msgid ""
-"Floating-point (float) literals, such as ``3.14`` or ``1.5``, denote :ref:"
-"`approximations of real numbers <datamodel-float>`."
+"Floating-point (float) literals, such as ``3.14`` or ``1.5``, "
+"denote :ref:`approximations of real numbers <datamodel-float>`."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:1417
@@ -2156,14 +2158,15 @@ msgstr ""
 #: ../../reference/lexical_analysis.rst:1581
 msgid ""
 "For some tokens, the distinction is unclear. For example, some people "
-"consider ``.``, ``(``, and ``)`` to be delimiters, while others see the :py:"
-"func:`getattr` operator and the function call operator(s)."
+"consider ``.``, ``(``, and ``)`` to be delimiters, while others see "
+"the :py:func:`getattr` operator and the function call operator(s)."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:1585
 msgid ""
-"Some of Python's operators, like ``and``, ``or``, and ``not in``, use :ref:"
-"`keyword <keywords>` tokens rather than \"symbols\" (operator tokens)."
+"Some of Python's operators, like ``and``, ``or``, and ``not in``, "
+"use :ref:`keyword <keywords>` tokens rather than \"symbols\" (operator "
+"tokens)."
 msgstr ""
 
 #: ../../reference/lexical_analysis.rst:1588