Units API.

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

GET /api/units/31251/?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/boooks_arch-handbook/pt_BR/?format=api",
    "source": [
        "To apply the rule for creating <filename>boot1</filename>, <filename>boot1.out</filename> must be resolved. This, in turn, depends on the existence of <filename>boot1.o</filename>. This last file is simply the result of assembling our familiar <filename>boot1.S</filename>, without linking. Now, the rule for creating <filename>boot1.out</filename> is applied. This tells us that <filename>boot1.o</filename> should be linked with <literal>start</literal> as its entry point, and starting at address <literal>0x7c00</literal>. Finally, <filename>boot1</filename> is created from <filename>boot1.out</filename> applying the appropriate rule. This rule is the <filename>objcopy</filename> command applied to <filename>boot1.out</filename>. Note the flags passed to <filename>objcopy</filename>: <literal>-S</literal> tells it to strip all relocation and symbolic information; <literal>-O binary</literal> indicates the output format, that is, a simple, unformatted binary file."
    ],
    "previous_source": "",
    "target": [
        "Para aplicar a regra para criar <filename> boot1 </filename> , <filename> boot1.out </filename> deve ser resolvido. Isso, por sua vez, depende da exist�ncia de <filename> boot1.o </filename> . Este �ltimo arquivo � simplesmente o resultado da montagem de nosso familiar <filename> boot1.S </filename> , sem vincular. Agora, a regra para criar <filename> boot1.out </filename> � aplicado. Isso nos diz que <filename> boot1.o </filename> deve estar ligado a <literal> come�ar </literal> como seu ponto de entrada, e come�ando no endere�o <literal> 0x7c00 </literal> . Finalmente, <filename> boot1 </filename> � criado a partir de <filename> boot1.out </filename> aplicar a regra apropriada. Esta regra � a <filename> objcopy </filename> comando aplicado a <filename> boot1.out </filename> . Observe as bandeiras passadas para <filename> objcopy </filename> : <literal> -S </literal> diz para remover toda a reloca��o e informa��es simb�licas; <literal> Bin�rio -O </literal> indica o formato de sa�da, isto �, um arquivo bin�rio simples e n�o formatado. "
    ],
    "id_hash": 7897245605041597744,
    "content_hash": 7897245605041597744,
    "location": "book.translate.xml:1414",
    "context": "",
    "note": "(itstool) path: sect1/para",
    "flags": "",
    "labels": [],
    "state": 10,
    "fuzzy": true,
    "translated": false,
    "approved": false,
    "position": 154,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": true,
    "num_words": 109,
    "source_unit": "https://translate-dev.freebsd.org/api/units/102300/?format=api",
    "priority": 100,
    "id": 31251,
    "web_url": "https://translate-dev.freebsd.org/translate/freebsd-doc/boooks_arch-handbook/pt_BR/?checksum=ed98a7095084ed30",
    "url": "https://translate-dev.freebsd.org/api/units/31251/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2019-10-20T12:21:43.472416Z"
}