Convert XLIFF to JSON

Turn XLIFF files into JSON. JSON for agents with the source and target languages and one object per entry holding its context, source and plural source, translation or plural forms, state, notes, comments, source references, flags and an obsolete mark.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop XLIFF files on the dialor turn it to pick what to do

Translation entries as JSON data.One object per entry, with the languages, source, translation, state and notes.

  1. What you get

    One JSON file for agents. It holds the source and target languages and one object for each entry in the XLIFF file.

    Each entry object carries its context, source and plural source, and its translation or plural forms. It also carries the state, notes, comments, source references, flags and an obsolete mark.

  2. How inline codes are handled

    Inline codes keep their text. Empty placeholders such as <x/> become their equiv-text. When a placeholder has no equiv-text, it is dropped.

  3. Trans-unit ids

    A numeric trans-unit id is not taken as a context. The context field is not filled from an id that is only a number.

    If you need to combine the result with other data, merge JSON joins JSON files. You can also browse every JSON conversion.

XLIFF and JSON.What each format is.

The formats

From · XLIFF

XLIFF 1.2

XLIFF 1.2, the XML exchange format of translation tools, with trans-units, states and notes.

Extensions
.xlf .xliff
MIME type
application/xliff+xml
Kind
Text and data
To · JSON

JSON

JSON, the data format of every API.

Extensions
.json
MIME type
application/json
Kind
Text and data

In your code.The same XLIFF to JSON conversion through the API, for your app or your agent.

terminal
$ cv convert report.xlf report.json
$ cv convert report.xlf report.json

Questions.What people ask about XLIFF to JSON.

01OF 04

It contains the source and target languages and one object per entry. Each object holds the context, source, translation, state, notes, comments, source references, flags and an obsolete mark, plus the plural source and plural forms where they apply.

An empty placeholder such as <x/> becomes its equiv-text. If it has no equiv-text, it is dropped.

Yes. Inline codes keep their text in the JSON.

No. A numeric trans-unit id is not taken as a context.

More conversions.Other ways in and out of XLIFF and JSON.