Translation components API.

See the Weblate's Web API documentation for detailed description of the API.

GET /api/translations/cnp3-ebook/principlesreferencemodels/en/units/?format=api&page=3
HTTP 200 OK
Allow: GET, POST, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 44,
    "next": null,
    "previous": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlesreferencemodels/en/units/?format=api&page=2",
    "results": [
        {
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlesreferencemodels/en/?format=api",
            "source": [
                "There are different types of transport layers. The most widely used transport layers on the Internet are :term:`TCP`, that provides a reliable connection-oriented bytestream transport service, and :term:`UDP`, that provides an unreliable connection-less transport service."
            ],
            "previous_source": "",
            "target": [
                "There are different types of transport layers. The most widely used transport layers on the Internet are :term:`TCP`, that provides a reliable connection-oriented bytestream transport service, and :term:`UDP`, that provides an unreliable connection-less transport service."
            ],
            "id_hash": -5550533315756247151,
            "content_hash": -5550533315756247151,
            "location": "../../principles/referencemodels.rst:135",
            "context": "",
            "note": "",
            "flags": "",
            "state": 100,
            "fuzzy": false,
            "translated": true,
            "approved": false,
            "position": 19,
            "has_suggestion": false,
            "has_comment": false,
            "has_failing_check": false,
            "num_words": 35,
            "source_unit": "https://weblate.info.ucl.ac.be/api/units/37545/?format=api",
            "priority": 100,
            "id": 37545,
            "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlesreferencemodels/en/?checksum=32f88b5b7860b791",
            "url": "https://weblate.info.ucl.ac.be/api/units/37545/?format=api",
            "explanation": "",
            "extra_flags": "",
            "pending": false,
            "timestamp": "2022-09-17T01:14:28.490634+02:00"
        },
        {
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlesreferencemodels/en/?format=api",
            "source": [
                "In contrast with OSI, the TCP/IP community did not spend a lot of effort defining a detailed reference model; in fact, the goals of the Internet architecture were only documented after TCP/IP had been deployed [Clark88]_. :rfc:`1122`, which defines the requirements for Internet hosts, mentions four different layers. Starting from the top, these are :"
            ],
            "previous_source": "",
            "target": [
                "In contrast with OSI, the TCP/IP community did not spend a lot of effort defining a detailed reference model; in fact, the goals of the Internet architecture were only documented after TCP/IP had been deployed [Clark88]_. :rfc:`1122`, which defines the requirements for Internet hosts, mentions four different layers. Starting from the top, these are :"
            ],
            "id_hash": -1694060610494554768,
            "content_hash": -1694060610494554768,
            "location": "../../principles/referencemodels.rst:221",
            "context": "",
            "note": "",
            "flags": "",
            "state": 100,
            "fuzzy": false,
            "translated": true,
            "approved": false,
            "position": 31,
            "has_suggestion": false,
            "has_comment": false,
            "has_failing_check": false,
            "num_words": 55,
            "source_unit": "https://weblate.info.ucl.ac.be/api/units/37546/?format=api",
            "priority": 100,
            "id": 37546,
            "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlesreferencemodels/en/?checksum=687d7cd9ab7d9d70",
            "url": "https://weblate.info.ucl.ac.be/api/units/37546/?format=api",
            "explanation": "",
            "extra_flags": "",
            "pending": false,
            "timestamp": "2022-09-17T01:14:28.528450+02:00"
        },
        {
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlesreferencemodels/en/?format=api",
            "source": [
                "the `Session layer`. The Session layer contains the protocols and mechanisms that are necessary to organize and to synchronize the dialogue and to manage the data exchange of presentation layer entities. While one of the main functions of the transport layer is to cope with the unreliability of the network layer, the session's layer objective is to hide the possible failures of transport-level connections to the upper layer higher. For this, the Session Layer provides services that allow establishing a session-connection, to support in-order data exchange (including mechanisms that allow recovering from the abrupt release of an underlying transport connection), and to release the connection in an orderly manner."
            ],
            "previous_source": "",
            "target": [
                "the `Session layer`. The Session layer contains the protocols and mechanisms that are necessary to organize and to synchronize the dialogue and to manage the data exchange of presentation layer entities. While one of the main functions of the transport layer is to cope with the unreliability of the network layer, the session's layer objective is to hide the possible failures of transport-level connections to the upper layer higher. For this, the Session Layer provides services that allow establishing a session-connection, to support in-order data exchange (including mechanisms that allow recovering from the abrupt release of an underlying transport connection), and to release the connection in an orderly manner."
            ],
            "id_hash": -1763300224796422075,
            "content_hash": -1763300224796422075,
            "location": "../../principles/referencemodels.rst:237",
            "context": "",
            "note": "",
            "flags": "",
            "state": 100,
            "fuzzy": false,
            "translated": true,
            "approved": false,
            "position": 39,
            "has_suggestion": false,
            "has_comment": false,
            "has_failing_check": false,
            "num_words": 109,
            "source_unit": "https://weblate.info.ucl.ac.be/api/units/37547/?format=api",
            "priority": 100,
            "id": 37547,
            "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlesreferencemodels/en/?checksum=67877fc9b4a49045",
            "url": "https://weblate.info.ucl.ac.be/api/units/37547/?format=api",
            "explanation": "",
            "extra_flags": "",
            "pending": false,
            "timestamp": "2022-09-17T01:14:28.557613+02:00"
        },
        {
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlesreferencemodels/en/?format=api",
            "source": [
                "the `Presentation layer` was designed to cope with the different ways of representing information on computers. There are many differences in the way computer store information. Some computers store integers as 32 bits field, others use 64 bits field and the same problem arises with floating point number. For textual information, this is even more complex with the many different character codes that have been used [#funicode]_. The situation is even more complex when considering the exchange of structured information such as database records. To solve this problem, the Presentation layer provides a common representation of the data transferred. The :term:`ASN.1` notation was designed for the Presentation layer and is still used today by some protocols."
            ],
            "previous_source": "",
            "target": [
                "the `Presentation layer` was designed to cope with the different ways of representing information on computers. There are many differences in the way computer store information. Some computers store integers as 32 bits field, others use 64 bits field and the same problem arises with floating point number. For textual information, this is even more complex with the many different character codes that have been used [#funicode]_. The situation is even more complex when considering the exchange of structured information such as database records. To solve this problem, the Presentation layer provides a common representation of the data transferred. The :term:`ASN.1` notation was designed for the Presentation layer and is still used today by some protocols."
            ],
            "id_hash": -5396818192196411735,
            "content_hash": -5396818192196411735,
            "location": "../../principles/referencemodels.rst:238",
            "context": "",
            "note": "",
            "flags": "",
            "state": 100,
            "fuzzy": false,
            "translated": true,
            "approved": false,
            "position": 40,
            "has_suggestion": false,
            "has_comment": false,
            "has_failing_check": false,
            "num_words": 116,
            "source_unit": "https://weblate.info.ucl.ac.be/api/units/37548/?format=api",
            "priority": 100,
            "id": 37548,
            "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlesreferencemodels/en/?checksum=351aa672a0c45ea9",
            "url": "https://weblate.info.ucl.ac.be/api/units/37548/?format=api",
            "explanation": "",
            "extra_flags": "",
            "pending": false,
            "timestamp": "2022-09-17T01:14:28.578816+02:00"
        }
    ]
}