Unit Instance

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

{
    "translation": "https://translate-dev.freebsd.org/api/translations/documentation/booksdev-model_index/en/?format=api",
    "source": [
        "There is no standards to how design should be done, nor is design collected in a centralised repository.  The main design is that of 4.4BSD.  footnote:[According to Kirk McKusick, after 20 years of developing UNIX operating systems, the interfaces are for the most part figured out. There is therefore no need for much design. However, new applications of the system and new hardware leads to some implementations being more beneficial than those that used to be preferred. One example is the introduction of web browsing that made the normal TCP/IP connection a short burst of data rather than a steady stream over a longer period of time.] As design is a part of the \"Code\" bracket in Jørgenssen's model, it is up to every developer or sub-project how this should be done.  Even if the design should be stored in a central repository, the output from the design stages would be of limited use as the differences of methodologies would make them poorly if at all interoperable.  For the overall design of the project, the project relies on the sub-projects to negotiate fit interfaces between each other rather than to dictate interfacing."
    ],
    "previous_source": "",
    "target": [
        "There is no standards to how design should be done, nor is design collected in a centralised repository.  The main design is that of 4.4BSD.  footnote:[According to Kirk McKusick, after 20 years of developing UNIX operating systems, the interfaces are for the most part figured out. There is therefore no need for much design. However, new applications of the system and new hardware leads to some implementations being more beneficial than those that used to be preferred. One example is the introduction of web browsing that made the normal TCP/IP connection a short burst of data rather than a steady stream over a longer period of time.] As design is a part of the \"Code\" bracket in Jørgenssen's model, it is up to every developer or sub-project how this should be done.  Even if the design should be stored in a central repository, the output from the design stages would be of limited use as the differences of methodologies would make them poorly if at all interoperable.  For the overall design of the project, the project relies on the sub-projects to negotiate fit interfaces between each other rather than to dictate interfacing."
    ],
    "id_hash": -9116959103793094676,
    "content_hash": -9116959103793094676,
    "location": "documentation/content/en/books/dev-model/_index.adoc:353",
    "context": "",
    "note": "type: Plain text",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 93,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 192,
    "source_unit": "https://translate-dev.freebsd.org/api/units/1174162/?format=api",
    "priority": 100,
    "id": 1174162,
    "web_url": "https://translate-dev.freebsd.org/translate/documentation/booksdev-model_index/en/?checksum=017a0dffb2a61fec",
    "url": "https://translate-dev.freebsd.org/api/units/1174162/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2021-06-03T20:44:20.174087Z"
}