@@ -11,7 +11,7 @@ msgid ""
1111msgstr ""
1212"Project-Id-Version : Python 3.15\n "
1313"Report-Msgid-Bugs-To : \n "
14- "POT-Creation-Date : 2026-07-29 15:50 +0000\n "
14+ "POT-Creation-Date : 2026-08-15 14:15 +0000\n "
1515"PO-Revision-Date : 2025-09-16 00:01+0000\n "
1616"Last-Translator : Bhuvansh Kataria, 2026\n "
1717"Language-Team : Panjabi (Punjabi) (https://app.transifex.com/python-doc/ "
@@ -65,7 +65,7 @@ msgstr ""
6565msgid ""
6666"*name* and *value* are passed to ``BaseHeader`` from the :attr:`~email."
6767"policy.EmailPolicy.header_factory` call. The string value of any header "
68- "object is the *value* fully decoded to unicode ."
68+ "object is the *value* fully decoded to a string ."
6969msgstr ""
7070
7171msgid "This base class defines the following read-only properties:"
@@ -123,10 +123,10 @@ msgid ""
123123"defects to this list. On return, the ``kwds`` dictionary *must* contain "
124124"values for at least the keys ``decoded``, ``defects`` and ``parse_tree``. "
125125"``decoded`` should be the string value for the header (that is, the header "
126- "value fully decoded to unicode ). ``parse_tree`` is set to the parse tree "
126+ "value fully decoded to a string ). ``parse_tree`` is set to the parse tree "
127127"obtained from parsing the header. The parse method should assume that "
128128"*string* may contain content-transfer-encoded parts, but should correctly "
129- "handle all valid unicode characters as well so that it can parse un-encoded "
129+ "handle all valid Unicode characters as well so that it can parse un-encoded "
130130"header values."
131131msgstr ""
132132
@@ -162,7 +162,7 @@ msgid ""
162162"mechanism for encoding non-ASCII text as ASCII characters within a header "
163163"value. When a *value* containing encoded words is passed to the "
164164"constructor, the ``UnstructuredHeader`` parser converts such encoded words "
165- "into unicode , following the :rfc:`2047` rules for unstructured text. The "
165+ "into a string , following the :rfc:`2047` rules for unstructured text. The "
166166"parser uses heuristics to attempt to decode certain non-compliant encoded "
167167"words. Defects are registered in such cases, as well as defects for issues "
168168"such as invalid characters within the encoded words or the non-encoded text."
@@ -245,11 +245,10 @@ msgid ""
245245msgstr ""
246246
247247msgid ""
248- "The ``decoded`` value of the header will have all encoded words decoded to "
249- "unicode. :class:`~encodings.idna` encoded domain names are also decoded to "
250- "unicode. The ``decoded`` value is set by :ref:`joining <meth-str-join>` "
251- "the :class:`str` value of the elements of the ``groups`` attribute with ``', "
252- "'``."
248+ "The ``decoded`` value of the header will have all encoded words decoded to a "
249+ "string. :class:`~encodings.idna` encoded domain names are also decoded to a "
250+ "string. The ``decoded`` value is set by :ref:`joining <meth-str-join>` the :"
251+ "class:`str` value of the elements of the ``groups`` attribute with ``', '``."
253252msgstr ""
254253
255254msgid ""
@@ -495,7 +494,7 @@ msgid ""
495494"*domain*, in which case *username* and *domain* will be parsed from the "
496495"*addr_spec*. An *addr_spec* must be a properly RFC quoted string; if it is "
497496"not ``Address`` will raise an error. Unicode characters are allowed and "
498- "will be property encoded when serialized. However, per the RFCs, unicode is "
497+ "will be property encoded when serialized. However, per the RFCs, Unicode is "
499498"*not* allowed in the username portion of the address."
500499msgstr ""
501500
0 commit comments