python-docs-pl/library/struct.po at 3.8 · python/python-docs-pl

645 lines (495 loc) · 16.9 KB
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2021, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# Translators:
# Maciej Olko <maciej.olko@gmail.com>, 2020
# Tomasz Rodzen <t.rodzen@poczta.fm>, 2020
"Project-Id-Version: Python 3.8\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-01-01 16:06+0000\n"
"PO-Revision-Date: 2020-05-30 12:10+0000\n"
"Last-Translator: Tomasz Rodzen <t.rodzen@poczta.fm>, 2020\n"
"Language-Team: Polish (https://www.transifex.com/python-doc/teams/5390/pl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pl\n"
"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && "
"(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && "
"n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"
msgid ":mod:`struct` --- Interpret bytes as packed binary data"
msgid "**Source code:** :source:`Lib/struct.py`"
"This module performs conversions between Python values and C structs "
"represented as Python :class:`bytes` objects.  This can be used in handling "
"binary data stored in files or from network connections, among other "
"sources.  It uses :ref:`struct-format-strings` as compact descriptions of "
"the layout of the C structs and the intended conversion to/from Python "
"By default, the result of packing a given C struct includes pad bytes in "
"order to maintain proper alignment for the C types involved; similarly, "
"alignment is taken into account when unpacking.  This behavior is chosen so "
"that the bytes of a packed struct correspond exactly to the layout in memory "
"of the corresponding C struct.  To handle platform-independent data formats "
"or omit implicit pad bytes, use ``standard`` size and alignment instead of "
"``native`` size and alignment: see :ref:`struct-alignment` for details."
"Several :mod:`struct` functions (and methods of :class:`Struct`) take a "
"*buffer* argument.  This refers to objects that implement the :ref:"
"`bufferobjects` and provide either a readable or read-writable buffer.  The "
"most common types used for that purpose are :class:`bytes` and :class:"
"`bytearray`, but many other types that can be viewed as an array of bytes "
"implement the buffer protocol, so that they can be read/filled without "
"additional copying from a :class:`bytes` object."
msgid "Functions and Exceptions"
msgid "The module defines the following exception and functions:"
"Exception raised on various occasions; argument is a string describing what "
"is wrong."
"Return a bytes object containing the values *v1*, *v2*, ... packed according "
"to the format string *format*.  The arguments must match the values required "
"by the format exactly."
"Pack the values *v1*, *v2*, ... according to the format string *format* and "
"write the packed bytes into the writable buffer *buffer* starting at "
"position *offset*.  Note that *offset* is a required argument."
"Unpack from the buffer *buffer* (presumably packed by ``pack(format, ...)``) "
"according to the format string *format*.  The result is a tuple even if it "
"contains exactly one item.  The buffer's size in bytes must match the size "
"required by the format, as reflected by :func:`calcsize`."
"Unpack from *buffer* starting at position *offset*, according to the format "
"string *format*.  The result is a tuple even if it contains exactly one "
"item.  The buffer's size in bytes, starting at position *offset*, must be at "
"least the size required by the format, as reflected by :func:`calcsize`."
"Iteratively unpack from the buffer *buffer* according to the format string "
"*format*.  This function returns an iterator which will read equally-sized "
"chunks from the buffer until all its contents have been consumed.  The "
"buffer's size in bytes must be a multiple of the size required by the "
"format, as reflected by :func:`calcsize`."
msgid "Each iteration yields a tuple as specified by the format string."
"Return the size of the struct (and hence of the bytes object produced by "
"``pack(format, ...)``) corresponding to the format string *format*."
msgid "Format Strings"
"Format strings are the mechanism used to specify the expected layout when "
"packing and unpacking data.  They are built up from :ref:`format-"
"characters`, which specify the type of data being packed/unpacked.  In "
"addition, there are special characters for controlling the :ref:`struct-"
"alignment`."
msgid "Byte Order, Size, and Alignment"
"By default, C types are represented in the machine's native format and byte "
"order, and properly aligned by skipping pad bytes if necessary (according to "
"the rules used by the C compiler)."
"Alternatively, the first character of the format string can be used to "
"indicate the byte order, size and alignment of the packed data, according to "
"the following table:"
msgid "Character"
msgid "Byte order"
msgid "Size"
msgid "Alignment"
msgid "``@``"
msgid "native"
msgid "``=``"
msgid "standard"
msgid "none"
msgid "``<``"
msgid "little-endian"
msgid "``>``"
msgid "big-endian"
msgid "``!``"
msgid "network (= big-endian)"
msgid "If the first character is not one of these, ``'@'`` is assumed."
"Native byte order is big-endian or little-endian, depending on the host "
"system. For example, Intel x86 and AMD64 (x86-64) are little-endian; "
"Motorola 68000 and PowerPC G5 are big-endian; ARM and Intel Itanium feature "
"switchable endianness (bi-endian). Use ``sys.byteorder`` to check the "
"endianness of your system."
"Native size and alignment are determined using the C compiler's ``sizeof`` "
"expression.  This is always combined with native byte order."
"Standard size depends only on the format character;  see the table in the :"
"ref:`format-characters` section."
"Note the difference between ``'@'`` and ``'='``: both use native byte order, "
"but the size and alignment of the latter is standardized."
"The form ``'!'`` represents the network byte order which is always big-"
"endian as defined in `IETF RFC 1700 <IETF RFC 1700_>`_."
"There is no way to indicate non-native byte order (force byte-swapping); use "
"the appropriate choice of ``'<'`` or ``'>'``."
msgid "Notes:"
msgstr "Uwagi:"
"Padding is only automatically added between successive structure members. No "
"padding is added at the beginning or the end of the encoded struct."
"No padding is added when using non-native size and alignment, e.g. with '<', "
"'>', '=', and '!'."
"To align the end of a structure to the alignment requirement of a particular "
"type, end the format with the code for that type with a repeat count of "
"zero.  See :ref:`struct-examples`."
msgid "Format Characters"
"Format characters have the following meaning; the conversion between C and "
"Python values should be obvious given their types.  The 'Standard size' "
"column refers to the size of the packed value in bytes when using standard "
"size; that is, when the format string starts with one of ``'<'``, ``'>'``, "
"``'!'`` or ``'='``.  When using native size, the size of the packed value is "
"platform-dependent."
msgid "Format"
msgstr "Format"
msgid "C Type"
msgstr "typ języka C "
msgid "Python type"
msgid "Standard size"
msgid "Notes"
msgstr "Notatki"
msgid "``x``"
msgid "pad byte"
msgid "no value"
msgid "``c``"
msgid ":c:type:`char`"
msgid "bytes of length 1"
msgid "``b``"
msgid ":c:type:`signed char`"
msgid "integer"
msgid "\\(1), \\(2)"
msgid "``B``"
msgid ":c:type:`unsigned char`"
msgid "\\(2)"
msgstr "\\(2)"
msgid "``?``"
msgid ":c:type:`_Bool`"
msgid "bool"
msgid "\\(1)"
msgstr "\\(1)"
msgid "``h``"
msgid ":c:type:`short`"
msgid "``H``"
msgid ":c:type:`unsigned short`"
msgid "``i``"
msgid ":c:type:`int`"
msgid "``I``"
msgid ":c:type:`unsigned int`"
msgid "``l``"
msgid ":c:type:`long`"
msgid "``L``"
msgid ":c:type:`unsigned long`"
msgid "``q``"
msgid ":c:type:`long long`"
msgid "``Q``"
msgid ":c:type:`unsigned long long`"
msgid "``n``"
msgid ":c:type:`ssize_t`"
msgid "\\(3)"
msgstr "\\(3)"
msgid "``N``"
msgid ":c:type:`size_t`"
msgid "``e``"
msgid "\\(6)"
msgid "float"
msgstr "typ (float) zmiennoprzecinkowy pojedynczej precyzji"
msgid "\\(4)"
msgstr "\\(4)"
msgid "``f``"
msgid ":c:type:`float`"
msgid "``d``"
msgid ":c:type:`double`"
msgid "``s``"
msgid ":c:type:`char[]`"
msgid "bytes"
msgid "``p``"
msgid "``P``"
msgid ":c:type:`void \\*`"
msgid "\\(5)"
msgstr "\\(5)"
msgid "Added support for the ``'n'`` and ``'N'`` formats."
msgid "Added support for the ``'e'`` format."
"The ``'?'`` conversion code corresponds to the :c:type:`_Bool` type defined "
"by C99. If this type is not available, it is simulated using a :c:type:"
"`char`. In standard mode, it is always represented by one byte."
"When attempting to pack a non-integer using any of the integer conversion "
"codes, if the non-integer has a :meth:`__index__` method then that method is "
"called to convert the argument to an integer before packing."
msgid "Use of the :meth:`__index__` method for non-integers is new in 3.2."
"The ``'n'`` and ``'N'`` conversion codes are only available for the native "
"size (selected as the default or with the ``'@'`` byte order character). For "
"the standard size, you can use whichever of the other integer formats fits "
"your application."
"For the ``'f'``, ``'d'`` and ``'e'`` conversion codes, the packed "
"representation uses the IEEE 754 binary32, binary64 or binary16 format (for "
"``'f'``, ``'d'`` or ``'e'`` respectively), regardless of the floating-point "
"format used by the platform."
"The ``'P'`` format character is only available for the native byte ordering "
"(selected as the default or with the ``'@'`` byte order character). The byte "
"order character ``'='`` chooses to use little- or big-endian ordering based "
"on the host system. The struct module does not interpret this as native "
"ordering, so the ``'P'`` format is not available."
"The IEEE 754 binary16 \"half precision\" type was introduced in the 2008 "
"revision of the `IEEE 754 standard <ieee 754 standard_>`_. It has a sign "
"bit, a 5-bit exponent and 11-bit precision (with 10 bits explicitly stored), "
"and can represent numbers between approximately ``6.1e-05`` and ``6.5e+04`` "
"at full precision. This type is not widely supported by C compilers: on a "
"typical machine, an unsigned short can be used for storage, but not for math "
"operations. See the Wikipedia page on the `half-precision floating-point "
"format <half precision format_>`_ for more information."
"A format character may be preceded by an integral repeat count.  For "
"example, the format string ``'4h'`` means exactly the same as ``'hhhh'``."
"Whitespace characters between formats are ignored; a count and its format "
"must not contain whitespace though."
"For the ``'s'`` format character, the count is interpreted as the length of "
"the bytes, not a repeat count like for the other format characters; for "
"example, ``'10s'`` means a single 10-byte string, while ``'10c'`` means 10 "
"characters. If a count is not given, it defaults to 1.  For packing, the "
"string is truncated or padded with null bytes as appropriate to make it fit. "
"For unpacking, the resulting bytes object always has exactly the specified "
"number of bytes.  As a special case, ``'0s'`` means a single, empty string "
"(while ``'0c'`` means 0 characters)."
"When packing a value ``x`` using one of the integer formats (``'b'``, "
"``'B'``, ``'h'``, ``'H'``, ``'i'``, ``'I'``, ``'l'``, ``'L'``, ``'q'``, "
"``'Q'``), if ``x`` is outside the valid range for that format then :exc:"
"`struct.error` is raised."
"In 3.0, some of the integer formats wrapped out-of-range values and raised :"
"exc:`DeprecationWarning` instead of :exc:`struct.error`."
"The ``'p'`` format character encodes a \"Pascal string\", meaning a short "
"variable-length string stored in a *fixed number of bytes*, given by the "
"count. The first byte stored is the length of the string, or 255, whichever "
"is smaller.  The bytes of the string follow.  If the string passed in to :"
"func:`pack` is too long (longer than the count minus 1), only the leading "
"``count-1`` bytes of the string are stored.  If the string is shorter than "
"``count-1``, it is padded with null bytes so that exactly count bytes in all "
"are used.  Note that for :func:`unpack`, the ``'p'`` format character "
"consumes ``count`` bytes, but that the string returned can never contain "
"more than 255 bytes."
"For the ``'?'`` format character, the return value is either :const:`True` "
"or :const:`False`. When packing, the truth value of the argument object is "
"used. Either 0 or 1 in the native or standard bool representation will be "
"packed, and any non-zero value will be ``True`` when unpacking."
msgid "Examples"
msgstr "Przykłady"
"All examples assume a native byte order, size, and alignment with a big-"
"endian machine."
msgid "A basic example of packing/unpacking three integers::"
"Unpacked fields can be named by assigning them to variables or by wrapping "
"the result in a named tuple::"
"The ordering of format characters may have an impact on size since the "
"padding needed to satisfy alignment requirements is different::"
"The following format ``'llh0l'`` specifies two pad bytes at the end, "
"assuming longs are aligned on 4-byte boundaries::"
"This only works when native size and alignment are in effect; standard size "
"and alignment does not enforce any alignment."
msgid "Module :mod:`array`"
msgid "Packed binary storage of homogeneous data."
msgid "Module :mod:`xdrlib`"
msgid "Packing and unpacking of XDR data."
msgid "Classes"
msgstr "Klasy"
msgid "The :mod:`struct` module also defines the following type:"
"Return a new Struct object which writes and reads binary data according to "
"the format string *format*.  Creating a Struct object once and calling its "
"methods is more efficient than calling the :mod:`struct` functions with the "
"same format since the format string only needs to be compiled once."
"The compiled versions of the most recent format strings passed to :class:"
"`Struct` and the module-level functions are cached, so programs that use "
"only a few format strings needn't worry about reusing a single :class:"
"`Struct` instance."
msgid "Compiled Struct objects support the following methods and attributes:"
"Identical to the :func:`pack` function, using the compiled format. "
"(``len(result)`` will equal :attr:`size`.)"
msgid "Identical to the :func:`pack_into` function, using the compiled format."
"Identical to the :func:`unpack` function, using the compiled format. The "
"buffer's size in bytes must equal :attr:`size`."
"Identical to the :func:`unpack_from` function, using the compiled format. "
"The buffer's size in bytes, starting at position *offset*, must be at least :"
"attr:`size`."
"Identical to the :func:`iter_unpack` function, using the compiled format. "
"The buffer's size in bytes must be a multiple of :attr:`size`."
msgid "The format string used to construct this Struct object."
msgid "The format string type is now :class:`str` instead of :class:`bytes`."
"The calculated size of the struct (and hence of the bytes object produced by "
"the :meth:`pack` method) corresponding to :attr:`format`."
Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

FilesExpand file tree

struct.po

Latest commit

History

struct.po

File metadata and controls
