Skip to content

Commit d83a6e8

Browse files
author
GitHub Action's update-translation job
committed
Update translation from Transifex
1 parent 6536da7 commit d83a6e8

File tree

5 files changed

+68
-34
lines changed

5 files changed

+68
-34
lines changed

‎library/asyncio.po‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ msgid ""
1313
msgstr ""
1414
"Project-Id-Version: Python 3.14\n"
1515
"Report-Msgid-Bugs-To: \n"
16-
"POT-Creation-Date: 2025-09-27 14:12+0000\n"
16+
"POT-Creation-Date: 2025-10-17 14:15+0000\n"
1717
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
1818
"Last-Translator: Maciej Olko <[email protected]>, 2025\n"
1919
"Language-Team: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n"

‎library/codecs.po‎

Lines changed: 29 additions & 22 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:00+0000\n"
1616
"Last-Translator: python-doc bot, 2025\n"
1717
"Language-Team: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n"
@@ -1029,27 +1029,34 @@ msgid ""
10291029
"Unicode code point, is to store each code point as four consecutive bytes. "
10301030
"There are two possibilities: store the bytes in big endian or in little "
10311031
"endian order. These two encodings are called ``UTF-32-BE`` and ``UTF-32-LE`` "
1032-
"respectively. Their disadvantage is that if e.g. you use ``UTF-32-BE`` on a "
1033-
"little endian machine you will always have to swap bytes on encoding and "
1034-
"decoding. ``UTF-32`` avoids this problem: bytes will always be in natural "
1035-
"endianness. When these bytes are read by a CPU with a different endianness, "
1036-
"then bytes have to be swapped though. To be able to detect the endianness of "
1037-
"a ``UTF-16`` or ``UTF-32`` byte sequence, there's the so called BOM (\"Byte "
1038-
"Order Mark\"). This is the Unicode character ``U+FEFF``. This character can "
1039-
"be prepended to every ``UTF-16`` or ``UTF-32`` byte sequence. The byte "
1040-
"swapped version of this character (``0xFFFE``) is an illegal character that "
1041-
"may not appear in a Unicode text. So when the first character in a "
1042-
"``UTF-16`` or ``UTF-32`` byte sequence appears to be a ``U+FFFE`` the bytes "
1043-
"have to be swapped on decoding. Unfortunately the character ``U+FEFF`` had a "
1044-
"second purpose as a ``ZERO WIDTH NO-BREAK SPACE``: a character that has no "
1045-
"width and doesn't allow a word to be split. It can e.g. be used to give "
1046-
"hints to a ligature algorithm. With Unicode 4.0 using ``U+FEFF`` as a ``ZERO "
1047-
"WIDTH NO-BREAK SPACE`` has been deprecated (with ``U+2060`` (``WORD "
1048-
"JOINER``) assuming this role). Nevertheless Unicode software still must be "
1049-
"able to handle ``U+FEFF`` in both roles: as a BOM it's a device to determine "
1050-
"the storage layout of the encoded bytes, and vanishes once the byte sequence "
1051-
"has been decoded into a string; as a ``ZERO WIDTH NO-BREAK SPACE`` it's a "
1052-
"normal character that will be decoded like any other."
1032+
"respectively. Their disadvantage is that if, for example, you use ``UTF-32-"
1033+
"BE`` on a little endian machine you will always have to swap bytes on "
1034+
"encoding and decoding. Python's ``UTF-16`` and ``UTF-32`` codecs avoid this "
1035+
"problem by using the platform's native byte order when no BOM is present. "
1036+
"Python follows prevailing platform practice, so native-endian data round-"
1037+
"trips without redundant byte swapping, even though the Unicode Standard "
1038+
"defaults to big-endian when the byte order is unspecified. When these bytes "
1039+
"are read by a CPU with a different endianness, the bytes have to be swapped. "
1040+
"To be able to detect the endianness of a ``UTF-16`` or ``UTF-32`` byte "
1041+
"sequence, a BOM (\"Byte Order Mark\") is used. This is the Unicode character "
1042+
"``U+FEFF``. This character can be prepended to every ``UTF-16`` or "
1043+
"``UTF-32`` byte sequence. The byte swapped version of this character "
1044+
"(``0xFFFE``) is an illegal character that may not appear in a Unicode text. "
1045+
"When the first character of a ``UTF-16`` or ``UTF-32`` byte sequence is "
1046+
"``U+FFFE``, the bytes have to be swapped on decoding."
1047+
msgstr ""
1048+
1049+
msgid ""
1050+
"Unfortunately the character ``U+FEFF`` had a second purpose as a ``ZERO "
1051+
"WIDTH NO-BREAK SPACE``: a character that has no width and doesn't allow a "
1052+
"word to be split. It can e.g. be used to give hints to a ligature algorithm. "
1053+
"With Unicode 4.0 using ``U+FEFF`` as a ``ZERO WIDTH NO-BREAK SPACE`` has "
1054+
"been deprecated (with ``U+2060`` (``WORD JOINER``) assuming this role). "
1055+
"Nevertheless Unicode software still must be able to handle ``U+FEFF`` in "
1056+
"both roles: as a BOM it's a device to determine the storage layout of the "
1057+
"encoded bytes, and vanishes once the byte sequence has been decoded into a "
1058+
"string; as a ``ZERO WIDTH NO-BREAK SPACE`` it's a normal character that will "
1059+
"be decoded like any other."
10531060
msgstr ""
10541061

10551062
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: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n"
@@ -1226,8 +1226,8 @@ msgid "justify"
12261226
msgstr ""
12271227

12281228
msgid ""
1229-
"Legal values are the strings: ``\"left\"``, ``\"center\"``, ``\"right\"``, "
1230-
"and ``\"fill\"``."
1229+
"Legal values are the strings: ``\"left\"``, ``\"center\"``, and "
1230+
"``\"right\"``."
12311231
msgstr ""
12321232

12331233
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: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n"
@@ -658,12 +658,21 @@ msgstr ""
658658
msgid ""
659659
"This is a low-level interface to the functionality of :func:`warn`, passing "
660660
"in explicitly the message, category, filename and line number, and "
661-
"optionally the module name and the registry (which should be the "
662-
"``__warningregistry__`` dictionary of the module). The module name defaults "
663-
"to the filename with ``.py`` stripped; if no registry is passed, the warning "
664-
"is never suppressed. *message* must be a string and *category* a subclass "
665-
"of :exc:`Warning` or *message* may be a :exc:`Warning` instance, in which "
666-
"case *category* will be ignored."
661+
"optionally other arguments. *message* must be a string and *category* a "
662+
"subclass of :exc:`Warning` or *message* may be a :exc:`Warning` instance, in "
663+
"which case *category* will be ignored."
664+
msgstr ""
665+
666+
msgid ""
667+
"*module*, if supplied, should be the module name. If no module is passed, "
668+
"the filename with ``.py`` stripped is used."
669+
msgstr ""
670+
671+
msgid ""
672+
"*registry*, if supplied, should be the ``__warningregistry__`` dictionary of "
673+
"the module. If no registry is passed, each warning is treated as the first "
674+
"occurrence, that is, filter actions ``\"default\"``, ``\"module\"`` and "
675+
"``\"once\"`` are handled as ``\"always\"``."
667676
msgstr ""
668677

669678
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: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n"
@@ -85,6 +85,11 @@ msgstr ""
8585
msgid "Library"
8686
msgstr "Biblioteka"
8787

88+
msgid ""
89+
":gh:`140272`: Fix memory leak in the :meth:`!clear` method of the :mod:`dbm."
90+
"gnu` database."
91+
msgstr ""
92+
8893
msgid ""
8994
":gh:`140041`: Fix import of :mod:`ctypes` on Android and Cygwin when ABI "
9095
"flags are present."
@@ -378,6 +383,11 @@ msgid ""
378383
"by Kumar Aditya."
379384
msgstr ""
380385

386+
msgid ""
387+
":gh:`133789`: Fix unpickling of :mod:`pathlib` objects that were pickled in "
388+
"Python 3.13."
389+
msgstr ""
390+
381391
msgid ""
382392
":gh:`127081`: Fix libc thread safety issues with :mod:`dbm` by performing "
383393
"stateful operations in critical sections."
@@ -435,11 +445,19 @@ msgstr ""
435445
msgid "Core and Builtins"
436446
msgstr "Core i builtiny"
437447

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

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

0 commit comments

Comments
 (0)