@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-10-09 14:15+0000\n"
+"POT-Creation-Date: 2025-10-19 14:13+0000\n"
 "PO-Revision-Date: 2025-09-16 00:00+0000\n"
 "Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
 "MIME-Version: 1.0\n"
@@ -1023,27 +1023,34 @@ msgid ""
 "Unicode code point, is to store each code point as four consecutive bytes. "
 "There are two possibilities: store the bytes in big endian or in little "
 "endian order. These two encodings are called ``UTF-32-BE`` and ``UTF-32-LE`` "
-"respectively. Their disadvantage is that if e.g. you use ``UTF-32-BE`` on a "
-"little endian machine you will always have to swap bytes on encoding and "
-"decoding. ``UTF-32`` avoids this problem: bytes will always be in natural "
-"endianness. When these bytes are read by a CPU with a different endianness, "
-"then bytes have to be swapped though. To be able to detect the endianness of "
-"a ``UTF-16`` or ``UTF-32`` byte sequence, there's the so called BOM (\"Byte "
-"Order Mark\"). This is the Unicode character ``U+FEFF``. This character can "
-"be prepended to every ``UTF-16`` or ``UTF-32`` byte sequence. The byte "
-"swapped version of this character (``0xFFFE``) is an illegal character that "
-"may not appear in a Unicode text. So when the first character in a "
-"``UTF-16`` or ``UTF-32`` byte sequence appears to be a ``U+FFFE`` the bytes "
-"have to be swapped on decoding. Unfortunately the character ``U+FEFF`` had a "
-"second purpose as a ``ZERO WIDTH NO-BREAK SPACE``: a character that has no "
-"width and doesn't allow a word to be split. It can e.g. be used to give "
-"hints to a ligature algorithm. With Unicode 4.0 using ``U+FEFF`` as a ``ZERO "
-"WIDTH NO-BREAK SPACE`` has been deprecated (with ``U+2060`` (``WORD "
-"JOINER``) assuming this role). Nevertheless Unicode software still must be "
-"able to handle ``U+FEFF`` in both roles: as a BOM it's a device to determine "
-"the storage layout of the encoded bytes, and vanishes once the byte sequence "
-"has been decoded into a string; as a ``ZERO WIDTH NO-BREAK SPACE`` it's a "
-"normal character that will be decoded like any other."
+"respectively. Their disadvantage is that if, for example, you use ``UTF-32-"
+"BE`` on a little endian machine you will always have to swap bytes on "
+"encoding and decoding. Python's ``UTF-16`` and ``UTF-32`` codecs avoid this "
+"problem by using the platform's native byte order when no BOM is present. "
+"Python follows prevailing platform practice, so native-endian data round-"
+"trips without redundant byte swapping, even though the Unicode Standard "
+"defaults to big-endian when the byte order is unspecified. When these bytes "
+"are read by a CPU with a different endianness, the bytes have to be swapped. "
+"To be able to detect the endianness of a ``UTF-16`` or ``UTF-32`` byte "
+"sequence, a BOM (\"Byte Order Mark\") is used. This is the Unicode character "
+"``U+FEFF``. This character can be prepended to every ``UTF-16`` or "
+"``UTF-32`` byte sequence. The byte swapped version of this character "
+"(``0xFFFE``) is an illegal character that may not appear in a Unicode text. "
+"When the first character of a ``UTF-16`` or ``UTF-32`` byte sequence is "
+"``U+FFFE``, the bytes have to be swapped on decoding."
+msgstr ""
+
+msgid ""
+"Unfortunately the character ``U+FEFF`` had a second purpose as a ``ZERO "
+"WIDTH NO-BREAK SPACE``: a character that has no width and doesn't allow a "
+"word to be split. It can e.g. be used to give hints to a ligature algorithm. "
+"With Unicode 4.0 using ``U+FEFF`` as a ``ZERO WIDTH NO-BREAK SPACE`` has "
+"been deprecated (with ``U+2060`` (``WORD JOINER``) assuming this role). "
+"Nevertheless Unicode software still must be able to handle ``U+FEFF`` in "
+"both roles: as a BOM it's a device to determine the storage layout of the "
+"encoded bytes, and vanishes once the byte sequence has been decoded into a "
+"string; as a ``ZERO WIDTH NO-BREAK SPACE`` it's a normal character that will "
+"be decoded like any other."
 msgstr ""
 
 msgid ""
 
@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-10-17 14:15+0000\n"
+"POT-Creation-Date: 2025-10-19 14:13+0000\n"
 "PO-Revision-Date: 2025-09-16 00:01+0000\n"
 "Last-Translator: python-doc bot, 2025\n"
 "Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
@@ -1222,8 +1222,8 @@ msgid "justify"
 msgstr ""
 
 msgid ""
-"Legal values are the strings: ``\"left\"``, ``\"center\"``, ``\"right\"``, "
-"and ``\"fill\"``."
+"Legal values are the strings: ``\"left\"``, ``\"center\"``, and "
+"``\"right\"``."
 msgstr ""
 
 msgid "region"
 
@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-10-09 14:15+0000\n"
+"POT-Creation-Date: 2025-10-19 14:13+0000\n"
 "PO-Revision-Date: 2025-09-16 00:02+0000\n"
 "Last-Translator: python-doc bot, 2025\n"
 "Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
@@ -656,12 +656,21 @@ msgstr ""
 msgid ""
 "This is a low-level interface to the functionality of :func:`warn`, passing "
 "in explicitly the message, category, filename and line number, and "
-"optionally the module name and the registry (which should be the "
-"``__warningregistry__`` dictionary of the module).  The module name defaults "
-"to the filename with ``.py`` stripped; if no registry is passed, the warning "
-"is never suppressed. *message* must be a string and *category* a subclass "
-"of :exc:`Warning` or *message* may be a :exc:`Warning` instance, in which "
-"case *category* will be ignored."
+"optionally other arguments. *message* must be a string and *category* a "
+"subclass of :exc:`Warning` or *message* may be a :exc:`Warning` instance, in "
+"which case *category* will be ignored."
+msgstr ""
+
+msgid ""
+"*module*, if supplied, should be the module name. If no module is passed, "
+"the filename with ``.py`` stripped is used."
+msgstr ""
+
+msgid ""
+"*registry*, if supplied, should be the ``__warningregistry__`` dictionary of "
+"the module. If no registry is passed, each warning is treated as the first "
+"occurrence, that is, filter actions ``\"default\"``, ``\"module\"`` and "
+"``\"once\"`` are handled as ``\"always\"``."
 msgstr ""
 
 msgid ""
 
@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-10-17 14:15+0000\n"
+"POT-Creation-Date: 2025-10-19 14:13+0000\n"
 "PO-Revision-Date: 2025-09-16 00:02+0000\n"
 "Last-Translator: python-doc bot, 2025\n"
 "Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
@@ -83,6 +83,11 @@ msgstr ""
 msgid "Library"
 msgstr ""
 
+msgid ""
+":gh:`140272`: Fix memory leak in the :meth:`!clear` method of the :mod:`dbm."
+"gnu` database."
+msgstr ""
+
 msgid ""
 ":gh:`140041`: Fix import of :mod:`ctypes` on Android and Cygwin when ABI "
 "flags are present."
@@ -376,6 +381,11 @@ msgid ""
 "by Kumar Aditya."
 msgstr ""
 
+msgid ""
+":gh:`133789`: Fix unpickling of :mod:`pathlib` objects that were pickled in "
+"Python 3.13."
+msgstr ""
+
 msgid ""
 ":gh:`127081`: Fix libc thread safety issues with :mod:`dbm` by performing "
 "stateful operations in critical sections."
@@ -433,11 +443,19 @@ msgstr ""
 msgid "Core and Builtins"
 msgstr ""
 
+msgid ""
+":gh:`140257`: Fix data race between interpreter_clear() and take_gil() on "
+"eval_breaker during finalization with daemon threads."
+msgstr ""
+
 msgid ""
 ":gh:`140061`: Fixing the checking of whether an object is uniquely "
 "referenced to ensure free-threaded compatibility. Patch by Sergey Miryanov."
 msgstr ""
 
+msgid ":gh:`140067`: Fix memory leak in sub-interpreter creation."
+msgstr ""
+
 msgid ""
 ":gh:`140000`: Fix potential memory leak when a reference cycle exists "
 "between an instance of :class:`typing.TypeAliasType`, :class:`typing."