Units API.

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

GET /api/units/98006/?format=api
HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://translate-dev.freebsd.org/api/translations/freebsd-doc/articles_cups/en/?format=api",
    "source": [
        "Difficulties with <application>CUPS</application> often lies in permissions. First, double check the <citerefentry><refentrytitle>devfs</refentrytitle><manvolnum>8</manvolnum></citerefentry> permissions as outlined above. Next, check the actual permissions of the devices created in the file system. It is also helpful to make sure your user is a member of the <systemitem class=\"groupname\">cups</systemitem> group. If the permissions check boxes in the Administration section of the <application>CUPS</application> web interface do not seem to be working, another fix might be to manually backup the main <application>CUPS</application> configuration file located at <filename>/usr/local/etc/cups/cupsd.conf</filename> and edit the various configuration options and try different combinations of configuration options. One sample <filename>/usr/local/etc/cups/cupsd.conf</filename> to test is listed below. Please note that this sample <filename>cupsd.conf</filename> sacrifices security for easier configuration; once the administrator successfully connects to the <application>CUPS</application> server and configures the clients, it is advisable to revisit this configuration file and begin locking down access."
    ],
    "previous_source": "",
    "target": [
        "Difficulties with <application>CUPS</application> often lies in permissions. First, double check the <citerefentry><refentrytitle>devfs</refentrytitle><manvolnum>8</manvolnum></citerefentry> permissions as outlined above. Next, check the actual permissions of the devices created in the file system. It is also helpful to make sure your user is a member of the <systemitem class=\"groupname\">cups</systemitem> group. If the permissions check boxes in the Administration section of the <application>CUPS</application> web interface do not seem to be working, another fix might be to manually backup the main <application>CUPS</application> configuration file located at <filename>/usr/local/etc/cups/cupsd.conf</filename> and edit the various configuration options and try different combinations of configuration options. One sample <filename>/usr/local/etc/cups/cupsd.conf</filename> to test is listed below. Please note that this sample <filename>cupsd.conf</filename> sacrifices security for easier configuration; once the administrator successfully connects to the <application>CUPS</application> server and configures the clients, it is advisable to revisit this configuration file and begin locking down access."
    ],
    "id_hash": -52277833248327394,
    "content_hash": -52277833248327394,
    "location": "article.translate.xml:267",
    "context": "",
    "note": "(itstool) path: sect1/para",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 47,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": true,
    "num_words": 139,
    "source_unit": "https://translate-dev.freebsd.org/api/units/98006/?format=api",
    "priority": 100,
    "id": 98006,
    "web_url": "https://translate-dev.freebsd.org/translate/freebsd-doc/articles_cups/en/?checksum=7f4645966f9b391e",
    "url": "https://translate-dev.freebsd.org/api/units/98006/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2019-10-20T12:02:13.076592Z"
}