Convert TMX to JSON
Turn TMX 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 TMX files on the dialor turn it to pick what to do
Translation memory as plain JSON.One file with the languages and one object for each entry.
What you get
A single JSON file. It holds the source language and the target language, then one object for each entry in the TMX file.
Each entry object carries its context, its source and plural source, and its translation or plural forms. It also carries its state, notes, comments, source references, flags and an obsolete mark.
Which language is the target
The source language is the one named in the TMX header. The target is the first language in the file other than that one.
Further languages are dropped. If an entry holds translations in three languages, only the first one after the source language appears in the JSON.
Working with the result
The JSON is laid out for agents and scripts to read, so each field has its own name instead of sitting inside TMX markup. To combine the output with other data, try merge JSON. You can also browse every JSON conversion.
TMX and JSON.What each format is.
The formats
TMX Translation Memory
Translation Memory eXchange files of aligned source and target segments.
- Extensions
- .tmx
- MIME type
- application
/x -tmx +xml - Kind
- Text and data
JSON
JSON, the data format of every API.
- Extensions
- .json
- MIME type
- application
/json - Kind
- Text and data
In your code.The same TMX to JSON conversion through the API, for your app or your agent.
$ cv convert report.tmx report.json$ cv convert report.tmx report.jsonQuestions.What people ask about TMX to JSON.
The first language other than the source language named in the header. The source language is the one the header declares.
No. Further languages are dropped, so only one target language appears in the JSON.
Each entry is one object. It holds context, source and plural source, translation or plural forms, state, notes, comments, source references, flags and an obsolete mark.
Yes. The result is one JSON file for the TMX file.