XLIFF .xliff
Edit XLIFF translation files online
Open your XLIFF files in Stringly and see every language of a key side by side. Find what is missing, edit the text, and download the files. It runs in your browser and your files are not uploaded.
What Stringly does with XLIFF files
- Matches each file to a language and lines up the keys, so one row shows every translation of a key.
- Marks the keys that are missing in a language, and the translations whose placeholders differ from the source.
- Writes your changes back to the same format. Only the entries you changed are rewritten, so the rest of each file stays as it was.
- Exports the project to any of the other nine formats.
File layout
One file per target language, such as fr.xliff or messages.fr.xlf. Both XLIFF 1.2 and 2.0 are read. Inline tags inside the text stay in place, and only the units you change are rewritten.
Plurals
A text that is one ICU plural block, such as {count, plural, one {…} other {…}}, is shown as a plural key with a field per form.
Comments
The <note> of each unit is shown as the translator comment.
Placeholders
Inline tags stay in place. Stringly flags a translation whose {brace} placeholders or printf specifiers (such as %s and %d) differ from the source language.
Example
fr.xliff
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file source-language="en" target-language="fr" datatype="plaintext" original="app">
<body>
<trans-unit id="trip.title">
<source>Trip to {city}</source>
<target>Voyage à {city}</target>
<note>Title of the trip screen</note>
</trans-unit>
</body>
</file>
</xliff>Try it with your own files
Drop XLIFF files or a folder onto Stringly. Nothing is uploaded.