Convert XLIFF2 to QTTS
Turn XLIFF2 files into QTTS. A Qt Linguist TS file grouped by context, with each message's source, disambiguating comment, translation or numerus forms, notes, translator comments and locations, unfinished translations marked and obsolete entries marked vanished.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop XLIFF2 files on the dialor turn it to pick what to do
Translations grouped by context.XLIFF 2.0 units become Qt Linguist messages in one TS file.
What you get
One TS file, grouped by context. Each message keeps its source text, its disambiguating comment, and its translation or numerus forms. Notes, translator comments and locations stay with the message.
A translation that is not finished is marked unfinished. Obsolete entries are marked vanished.
How contexts are built
A context that contains a vertical bar is split in two. The part before the bar becomes the Qt context, and the part after it becomes the comment. A unit id that is only a number is not taken as a context.
What changes in the text
The segments of a unit are joined into one piece of text. Inline codes keep their text. Placeholders such as
<ph/>become their display text.A plural entry keeps only its singular source text, because TS has one source text per message.
XLIFF2 and QTTS.What each format is.
The formats
XLIFF 2.0
XLIFF 2.0, the newer translation exchange format with units, segments and states.
- Extensions
- .xlf .xliff
- MIME type
- application
/x -xliff2 +xml - Kind
- Text and data
Qt Linguist TS
Qt Linguist translation sources with contexts, numerus forms and unfinished marks.
- Extensions
- .ts
- MIME type
- application
/x -linguist - Kind
- Text and data
In your code.The same XLIFF2 to QTTS conversion through the API, for your app or your agent.
$ cv convert report.xlf report.ts$ cv convert report.xlf report.tsQuestions.What people ask about XLIFF2 to QTTS.
Yes. They are marked unfinished in the TS file. Obsolete entries are marked vanished.
It is split in two. The part before the bar is the Qt context, and the part after it is the comment.
Numerus forms are kept for the translation. The source text is only the singular, because TS has one source text.
No. The segments of a unit are joined into one text for the message.