Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit8527281

Browse files
author
GitHub Action's update-translation job
committed
Update translation from Transifex
1 parentd116285 commit8527281

File tree

5 files changed

+68
-34
lines changed

5 files changed

+68
-34
lines changed

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

10541061
msgid""

‎library/gc.po‎

Lines changed: 1 addition & 1 deletion
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-09-29 14:15+0000\n"
11+
"POT-Creation-Date:2025-10-19 14:13+0000\n"
1212
"PO-Revision-Date:2025-09-16 00:01+0000\n"
1313
"Language-Team:Indonesian (https://app.transifex.com/python-doc/teams/5390/"
1414
"id/)\n"

‎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:Indonesian (https://app.transifex.com/python-doc/teams/5390/"
@@ -1223,8 +1223,8 @@ msgid "justify"
12231223
msgstr""
12241224

12251225
msgid""
1226-
"Legal values are the strings: ``\"left\"``, ``\"center\"``,``\"right\"``, "
1227-
"and``\"fill\"``."
1226+
"Legal values are the strings: ``\"left\"``, ``\"center\"``,and "
1227+
"``\"right\"``."
12281228
msgstr""
12291229

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

668677
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: Indonesian (https://app.transifex.com/python-doc/teams/5390/"
@@ -84,6 +84,11 @@ msgstr ""
8484
msgid "Library"
8585
msgstr "Pustaka"
8686

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

385+
msgid ""
386+
":gh:`133789`: Fix unpickling of :mod:`pathlib` objects that were pickled in "
387+
"Python 3.13."
388+
msgstr ""
389+
380390
msgid ""
381391
":gh:`127081`: Fix libc thread safety issues with :mod:`dbm` by performing "
382392
"stateful operations in critical sections."
@@ -434,11 +444,19 @@ msgstr ""
434444
msgid "Core and Builtins"
435445
msgstr "Inti dan Bawaan"
436446

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

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

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp