Download

XLIFF · TMX

XLIFF and TMX: work with any CAT tool, keep the project yours.

XLIFF carries the strings of one task to a translator and back, with their statuses. TMX carries finished translations between translation memories. Lingobit Localizer writes and reads XLIFF 1.2 and imports and exports TMX, so translators and agencies can use the tools they already have.

Download free trial XLIFF details

XLIFF in every edition; TMX: Professional and higher

Your project LOC MyApp.loc Lingobit Localizer Project SourceGerman New Order Neue Bestellung Customer: Kunde: Quantity: Menge: Each string, translated in the project You get MyApp.loc MyApp_de.xlf MyApp_fr.xlf MyApp_ja.xlf A translated file for each language; back with statuses Your project LOC MyApp.loc Translate in Lingobit Project SourceGerman New Order Neue Bestellung Customer: Kunde: Quantity: Menge: You get MyApp.loc source MyApp_de.xlf MyApp_fr.xlf MyApp_ja.xlf
XLIFF
Version 1.2, written and read
XLIFF 2.0
Not supported
TMX
Import into memory, export
Matched by
Key, not by position
On this page

XLIFF, TMX, or CSV?

Pick by what has to travel: open work for a translator, finished translations for reuse, or a list for someone without a CAT tool.

FileCarriesStatusesIn Lingobit
XLIFF 1.2 (.xlf, .xliff)The strings of one task, one target language, with keys and notesYesPrepare Translation Task, Import Translation Results
TMX (.tmx)Pairs of source and translation, from any project or toolNoImport Matching Translations, export of project translations and memory
CSV or textKeys, source, and translation in columnsNoPrepare Translation Task, Import Translation Results
Translator project (.ltp)The task with previews and checks, for Translator EditionYesPrepare Translation Task, Import Translation Results

For translators who can use Translator Edition, included with every Localizer license, the translator project gives them the dialog previews and the project's checks; XLIFF is for those who stay in their CAT tool. See Translation workflow for who gets what.

XLIFF 1.2: out with the task, back with the work.

Prepare Translation Task writes one XLIFF 1.2 file for each language with the strings you chose for the task. Each string is a trans-unit whose ID is the Lingobit key, so the translation finds its string again on import, even when the next build has moved or added resources.

<trans-unit id="..." >
  <source>File saved.</source>
  <target state="translated">Datei gespeichert.</target>
</trans-unit>
  • What goes out: the languages and items of the task; with the Translation Task filter, the strings that are not Complete or Locked.
  • What comes back: Import Translation Results reads the targets, matches them by key, and lists in Output what changed and what was not imported.
  • Locked strings go out with translate="no", so CAT tools do not offer them for editing.
  • Inline markup: units with inline XLIFF elements are skipped on import, with a warning in Output.

XLIFF 2.0 is not supported. If your agency's tool writes 2.0 by default, ask for XLIFF 1.2; most CAT tools can still write it.

XLIFF can also be a source file: the .xliff that Xcode exports is translated in place (Professional and higher). See Apple XIB / Xcode.

XLIFF states and Lingobit statuses.

On import, the state of each target decides its status; the standard preset is shown. The other presets take any target, or only approved ones.

XLIFF on importLingobit status
final, signed-off, approved="yes"Complete
needs-review-*; machine-translation qualifiers; a target equal to its sourceFor Review
translated, or no stateIn Process
new, needs-translation, needs-l10n, needs-adaptation, rejectedNot imported

On export the direction is reversed: Complete goes out as final with approved="yes", For Review as needs-review-translation. CSV carries no statuses.

Professional and higher

TMX: reuse translations you already paid for.

A TMX file is a translation memory in an open XML format: each unit holds a source text and its translations, without keys or statuses. Agencies and CAT tools export them; earlier projects, in Lingobit or elsewhere, leave them behind.

  • Import only what matches. Import Matching Translations takes from TMX, XLIFF 1.2, CSV, or Lingobit memories only the entries that match strings in your project, not the whole file.
  • Choose how close. Exact 100%, High 95%, Broad 80%, or your own threshold. Long strings are segmented on import.
  • Many files at once. A whole folder of TMX files or a ZIP archive.
  • Export. The project's translations, or the translation memory, as TMX for a CAT tool or another team.

Reusing a TMX is how many teams switch tools without translating everything again; the other way is to import the localized files they already ship. See Migration.

The same exchange from a build script.

With the command line (Professional and higher), the exchange runs without the window, for example after each build:

localizer.com MyApp.loc -scan -lang:1031 -sendxliff:MyApp_de.xlf -save
localizer.com MyApp.loc -lang:1031 -receivexliff:MyApp_de.xlf -xliffaccept:standard -save
localizer.com MyApp.loc -lang:all -importtmx:agency.tmx -tmthreshold:95 -translate -save

The task settings come from the project: prepare a task once in the wizard with Save settings in project. See Command line interface.

Questions.

What is the difference between XLIFF and TMX?

XLIFF is a work file: the strings of one task, with keys so they go back to the right place, and states that say how far the work is. TMX is a memory: translated pairs without any place in a project, used to suggest or fill translations.

Which CAT tools work with these files?

Any tool that reads and writes XLIFF 1.2, and any that exports TMX. Check that the tool keeps the trans-unit IDs and writes 1.2, not 2.0.

Will an XLIFF still import after the application changed?

Yes, for the strings that still exist: targets are matched by key. Strings removed in the new build are reported in Output, not imported.

Is there a glossary format too?

Terminology is imported from TBX files or from Microsoft terms (Enterprise) and can be exported as TMX, CSV, or text. See Translation assistance.

XLIFF 1.2 or XLIFF 2.0?

Lingobit writes and reads XLIFF 1.2; XLIFF 2.0 is not supported. When a translator's tool offers both versions, choose 1.2.

Do translators need an XLIFF editor?

No. A translator without a CAT tool gets a translator project and works in Translator Edition, which is included with every Localizer license. XLIFF is for translators and agencies who already work in a CAT tool.