StoryAudit

← Back to storyaudit.app

How to check a Storyline XLIFF translation before you import it

The translated file came back from the vendor. Here is what breaks on import, how to find it by hand, and how to find it in one drop.

How Storyline translation works

Storyline exports the course text as an XLIFF file (File → Localization → Export), in XLIFF 1.2 or 2.0. The translator fills in the target segments and sends it back. Storyline imports it (File → Localization → Import) and replaces the text on every slide. Nothing checks the file in between.

What goes wrong

The manual check

Open the XLIFF in a text editor or a CAT tool, search for empty target elements, then read every segment that contains a percent sign. For a course with 1,500 segments that is an afternoon, and it has to be repeated for every language.

Do it in StoryAudit

Translation Check needs only the XLIFF file. It is the one mode that does not need the .story at all. Drop it and get:

Nothing uploads; the file is read in your browser. No Storyline license needed.

See the checks on the bundled sample course, then run the XLIFF on your desk with a free trial.

Open the live demo →

Vendors who don't take XLIFF

Course Docs exports a two-column translation template (source and translation) from the slide-by-slide contents, for vendors who work in spreadsheets. The XLIFF route is still the one that imports back cleanly, so use the template for review and the XLIFF for the round trip.

↑ Back to top