@@ -12,7 +12,7 @@ msgid ""
1212msgstr ""
1313"Project-Id-Version : Python 3.15\n "
1414"Report-Msgid-Bugs-To : \n "
15- "POT-Creation-Date : 2026-08-11 14:51 +0000\n "
15+ "POT-Creation-Date : 2026-08-15 14:15 +0000\n "
1616"PO-Revision-Date : 2025-09-16 00:01+0000\n "
1717"Last-Translator : Dmitry Luschan, 2025\n "
1818"Language-Team : Russian (https://app.transifex.com/python-doc/teams/5390/ "
@@ -68,7 +68,7 @@ msgstr ""
6868msgid ""
6969"*name* and *value* are passed to ``BaseHeader`` from the :attr:`~email."
7070"policy.EmailPolicy.header_factory` call. The string value of any header "
71- "object is the *value* fully decoded to unicode ."
71+ "object is the *value* fully decoded to a string ."
7272msgstr ""
7373
7474msgid "This base class defines the following read-only properties:"
@@ -126,10 +126,10 @@ msgid ""
126126"defects to this list. On return, the ``kwds`` dictionary *must* contain "
127127"values for at least the keys ``decoded``, ``defects`` and ``parse_tree``. "
128128"``decoded`` should be the string value for the header (that is, the header "
129- "value fully decoded to unicode ). ``parse_tree`` is set to the parse tree "
129+ "value fully decoded to a string ). ``parse_tree`` is set to the parse tree "
130130"obtained from parsing the header. The parse method should assume that "
131131"*string* may contain content-transfer-encoded parts, but should correctly "
132- "handle all valid unicode characters as well so that it can parse un-encoded "
132+ "handle all valid Unicode characters as well so that it can parse un-encoded "
133133"header values."
134134msgstr ""
135135
@@ -165,7 +165,7 @@ msgid ""
165165"mechanism for encoding non-ASCII text as ASCII characters within a header "
166166"value. When a *value* containing encoded words is passed to the "
167167"constructor, the ``UnstructuredHeader`` parser converts such encoded words "
168- "into unicode , following the :rfc:`2047` rules for unstructured text. The "
168+ "into a string , following the :rfc:`2047` rules for unstructured text. The "
169169"parser uses heuristics to attempt to decode certain non-compliant encoded "
170170"words. Defects are registered in such cases, as well as defects for issues "
171171"such as invalid characters within the encoded words or the non-encoded text."
@@ -248,11 +248,10 @@ msgid ""
248248msgstr ""
249249
250250msgid ""
251- "The ``decoded`` value of the header will have all encoded words decoded to "
252- "unicode. :class:`~encodings.idna` encoded domain names are also decoded to "
253- "unicode. The ``decoded`` value is set by :ref:`joining <meth-str-join>` "
254- "the :class:`str` value of the elements of the ``groups`` attribute with ``', "
255- "'``."
251+ "The ``decoded`` value of the header will have all encoded words decoded to a "
252+ "string. :class:`~encodings.idna` encoded domain names are also decoded to a "
253+ "string. The ``decoded`` value is set by :ref:`joining <meth-str-join>` the :"
254+ "class:`str` value of the elements of the ``groups`` attribute with ``', '``."
256255msgstr ""
257256
258257msgid ""
@@ -498,7 +497,7 @@ msgid ""
498497"*domain*, in which case *username* and *domain* will be parsed from the "
499498"*addr_spec*. An *addr_spec* must be a properly RFC quoted string; if it is "
500499"not ``Address`` will raise an error. Unicode characters are allowed and "
501- "will be property encoded when serialized. However, per the RFCs, unicode is "
500+ "will be property encoded when serialized. However, per the RFCs, Unicode is "
502501"*not* allowed in the username portion of the address."
503502msgstr ""
504503
0 commit comments