Skip to content

Commit 64406b8

Browse files
author
GitHub Action's update-translation job
committed
Update translation from Transifex
1 parent 257141b commit 64406b8

4 files changed

Lines changed: 67 additions & 33 deletions

File tree

‎library/codecs.po‎

Lines changed: 29 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ msgid ""
88
msgstr ""
99
"Project-Id-Version: Python 3.14\n"
1010
"Report-Msgid-Bugs-To: \n"
11-
"POT-Creation-Date: 2025-10-09 14:15+0000\n"
11+
"POT-Creation-Date: 2025-10-19 14:13+0000\n"
1212
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
1313
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
1414
"MIME-Version: 1.0\n"
@@ -1023,27 +1023,34 @@ msgid ""
10231023
"Unicode code point, is to store each code point as four consecutive bytes. "
10241024
"There are two possibilities: store the bytes in big endian or in little "
10251025
"endian order. These two encodings are called ``UTF-32-BE`` and ``UTF-32-LE`` "
1026-
"respectively. Their disadvantage is that if e.g. you use ``UTF-32-BE`` on a "
1027-
"little endian machine you will always have to swap bytes on encoding and "
1028-
"decoding. ``UTF-32`` avoids this problem: bytes will always be in natural "
1029-
"endianness. When these bytes are read by a CPU with a different endianness, "
1030-
"then bytes have to be swapped though. To be able to detect the endianness of "
1031-
"a ``UTF-16`` or ``UTF-32`` byte sequence, there's the so called BOM (\"Byte "
1032-
"Order Mark\"). This is the Unicode character ``U+FEFF``. This character can "
1033-
"be prepended to every ``UTF-16`` or ``UTF-32`` byte sequence. The byte "
1034-
"swapped version of this character (``0xFFFE``) is an illegal character that "
1035-
"may not appear in a Unicode text. So when the first character in a "
1036-
"``UTF-16`` or ``UTF-32`` byte sequence appears to be a ``U+FFFE`` the bytes "
1037-
"have to be swapped on decoding. Unfortunately the character ``U+FEFF`` had a "
1038-
"second purpose as a ``ZERO WIDTH NO-BREAK SPACE``: a character that has no "
1039-
"width and doesn't allow a word to be split. It can e.g. be used to give "
1040-
"hints to a ligature algorithm. With Unicode 4.0 using ``U+FEFF`` as a ``ZERO "
1041-
"WIDTH NO-BREAK SPACE`` has been deprecated (with ``U+2060`` (``WORD "
1042-
"JOINER``) assuming this role). Nevertheless Unicode software still must be "
1043-
"able to handle ``U+FEFF`` in both roles: as a BOM it's a device to determine "
1044-
"the storage layout of the encoded bytes, and vanishes once the byte sequence "
1045-
"has been decoded into a string; as a ``ZERO WIDTH NO-BREAK SPACE`` it's a "
1046-
"normal character that will be decoded like any other."
1026+
"respectively. Their disadvantage is that if, for example, you use ``UTF-32-"
1027+
"BE`` on a little endian machine you will always have to swap bytes on "
1028+
"encoding and decoding. Python's ``UTF-16`` and ``UTF-32`` codecs avoid this "
1029+
"problem by using the platform's native byte order when no BOM is present. "
1030+
"Python follows prevailing platform practice, so native-endian data round-"
1031+
"trips without redundant byte swapping, even though the Unicode Standard "
1032+
"defaults to big-endian when the byte order is unspecified. When these bytes "
1033+
"are read by a CPU with a different endianness, the bytes have to be swapped. "
1034+
"To be able to detect the endianness of a ``UTF-16`` or ``UTF-32`` byte "
1035+
"sequence, a BOM (\"Byte Order Mark\") is used. This is the Unicode character "
1036+
"``U+FEFF``. This character can be prepended to every ``UTF-16`` or "
1037+
"``UTF-32`` byte sequence. The byte swapped version of this character "
1038+
"(``0xFFFE``) is an illegal character that may not appear in a Unicode text. "
1039+
"When the first character of a ``UTF-16`` or ``UTF-32`` byte sequence is "
1040+
"``U+FFFE``, the bytes have to be swapped on decoding."
1041+
msgstr ""
1042+
1043+
msgid ""
1044+
"Unfortunately the character ``U+FEFF`` had a second purpose as a ``ZERO "
1045+
"WIDTH NO-BREAK SPACE``: a character that has no width and doesn't allow a "
1046+
"word to be split. It can e.g. be used to give hints to a ligature algorithm. "
1047+
"With Unicode 4.0 using ``U+FEFF`` as a ``ZERO WIDTH NO-BREAK SPACE`` has "
1048+
"been deprecated (with ``U+2060`` (``WORD JOINER``) assuming this role). "
1049+
"Nevertheless Unicode software still must be able to handle ``U+FEFF`` in "
1050+
"both roles: as a BOM it's a device to determine the storage layout of the "
1051+
"encoded bytes, and vanishes once the byte sequence has been decoded into a "
1052+
"string; as a ``ZERO WIDTH NO-BREAK SPACE`` it's a normal character that will "
1053+
"be decoded like any other."
10471054
msgstr ""
10481055

10491056
msgid ""

‎library/tkinter.po‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ msgid ""
1111
msgstr ""
1212
"Project-Id-Version: Python 3.14\n"
1313
"Report-Msgid-Bugs-To: \n"
14-
"POT-Creation-Date: 2025-10-17 14:15+0000\n"
14+
"POT-Creation-Date: 2025-10-19 14:13+0000\n"
1515
"PO-Revision-Date: 2025-09-16 00:01+0000\n"
1616
"Last-Translator: python-doc bot, 2025\n"
1717
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
@@ -1222,8 +1222,8 @@ msgid "justify"
12221222
msgstr ""
12231223

12241224
msgid ""
1225-
"Legal values are the strings: ``\"left\"``, ``\"center\"``, ``\"right\"``, "
1226-
"and ``\"fill\"``."
1225+
"Legal values are the strings: ``\"left\"``, ``\"center\"``, and "
1226+
"``\"right\"``."
12271227
msgstr ""
12281228

12291229
msgid "region"

‎library/warnings.po‎

Lines changed: 16 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ msgid ""
1111
msgstr ""
1212
"Project-Id-Version: Python 3.14\n"
1313
"Report-Msgid-Bugs-To: \n"
14-
"POT-Creation-Date: 2025-10-09 14:15+0000\n"
14+
"POT-Creation-Date: 2025-10-19 14:13+0000\n"
1515
"PO-Revision-Date: 2025-09-16 00:02+0000\n"
1616
"Last-Translator: python-doc bot, 2025\n"
1717
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
@@ -656,12 +656,21 @@ msgstr ""
656656
msgid ""
657657
"This is a low-level interface to the functionality of :func:`warn`, passing "
658658
"in explicitly the message, category, filename and line number, and "
659-
"optionally the module name and the registry (which should be the "
660-
"``__warningregistry__`` dictionary of the module). The module name defaults "
661-
"to the filename with ``.py`` stripped; if no registry is passed, the warning "
662-
"is never suppressed. *message* must be a string and *category* a subclass "
663-
"of :exc:`Warning` or *message* may be a :exc:`Warning` instance, in which "
664-
"case *category* will be ignored."
659+
"optionally other arguments. *message* must be a string and *category* a "
660+
"subclass of :exc:`Warning` or *message* may be a :exc:`Warning` instance, in "
661+
"which case *category* will be ignored."
662+
msgstr ""
663+
664+
msgid ""
665+
"*module*, if supplied, should be the module name. If no module is passed, "
666+
"the filename with ``.py`` stripped is used."
667+
msgstr ""
668+
669+
msgid ""
670+
"*registry*, if supplied, should be the ``__warningregistry__`` dictionary of "
671+
"the module. If no registry is passed, each warning is treated as the first "
672+
"occurrence, that is, filter actions ``\"default\"``, ``\"module\"`` and "
673+
"``\"once\"`` are handled as ``\"always\"``."
665674
msgstr ""
666675

667676
msgid ""

‎whatsnew/changelog.po‎

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ msgid ""
1111
msgstr ""
1212
"Project-Id-Version: Python 3.14\n"
1313
"Report-Msgid-Bugs-To: \n"
14-
"POT-Creation-Date: 2025-10-17 14:15+0000\n"
14+
"POT-Creation-Date: 2025-10-19 14:13+0000\n"
1515
"PO-Revision-Date: 2025-09-16 00:02+0000\n"
1616
"Last-Translator: python-doc bot, 2025\n"
1717
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
@@ -83,6 +83,11 @@ msgstr ""
8383
msgid "Library"
8484
msgstr ""
8585

86+
msgid ""
87+
":gh:`140272`: Fix memory leak in the :meth:`!clear` method of the :mod:`dbm."
88+
"gnu` database."
89+
msgstr ""
90+
8691
msgid ""
8792
":gh:`140041`: Fix import of :mod:`ctypes` on Android and Cygwin when ABI "
8893
"flags are present."
@@ -376,6 +381,11 @@ msgid ""
376381
"by Kumar Aditya."
377382
msgstr ""
378383

384+
msgid ""
385+
":gh:`133789`: Fix unpickling of :mod:`pathlib` objects that were pickled in "
386+
"Python 3.13."
387+
msgstr ""
388+
379389
msgid ""
380390
":gh:`127081`: Fix libc thread safety issues with :mod:`dbm` by performing "
381391
"stateful operations in critical sections."
@@ -433,11 +443,19 @@ msgstr ""
433443
msgid "Core and Builtins"
434444
msgstr ""
435445

446+
msgid ""
447+
":gh:`140257`: Fix data race between interpreter_clear() and take_gil() on "
448+
"eval_breaker during finalization with daemon threads."
449+
msgstr ""
450+
436451
msgid ""
437452
":gh:`140061`: Fixing the checking of whether an object is uniquely "
438453
"referenced to ensure free-threaded compatibility. Patch by Sergey Miryanov."
439454
msgstr ""
440455

456+
msgid ":gh:`140067`: Fix memory leak in sub-interpreter creation."
457+
msgstr ""
458+
441459
msgid ""
442460
":gh:`140000`: Fix potential memory leak when a reference cycle exists "
443461
"between an instance of :class:`typing.TypeAliasType`, :class:`typing."

0 commit comments

Comments
 (0)