Unit Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlesnaming/cs/?format=api",
    "source": [
        "The Domain Name System was created at a time when the Internet was mainly used in North America. The initial design assumed that all domain names would be composed of letters and digits :rfc:`1035`. As Internet usage grew in other parts of the world, it became important to support non-ASCII characters. For this, extensions have been proposed to the Domain Name System :rfc:`3490`. In a nutshell, the solution that is used to support Internationalized Domain Names works as follows. First, it is possible to use most of the Unicode characters to encode domain names and hostnames, with a few exceptions (for example, the dot character cannot be part of a name since it is used as a separator). Once a domain name has been encoded as a series of Unicode characters, it is then converted into a string that contains the ``xn--`` prefix and a sequence of ASCII characters. More details on these algorithms can be found in :rfc:`3490` and :rfc:`3492`."
    ],
    "previous_source": "",
    "target": [
        ""
    ],
    "id_hash": -2463380304628674959,
    "content_hash": -2463380304628674959,
    "location": "../../principles/naming.rst:77",
    "context": "",
    "note": "",
    "flags": "",
    "state": 0,
    "fuzzy": false,
    "translated": false,
    "approved": false,
    "position": 14,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 161,
    "source_unit": "https://weblate.info.ucl.ac.be/api/units/33774/?format=api",
    "priority": 100,
    "id": 17423,
    "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlesnaming/cs/?checksum=5dd050aa1bea0e71",
    "url": "https://weblate.info.ucl.ac.be/api/units/17423/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2019-10-14T10:39:11.676782+02:00"
}