E-Learning Translation Workflows for Articulate, Adobe Captivate, and All Major LMS Platforms

XLIFF and Translation Memory — The Technical Foundation of Professional E-Learning Translation

Before describing how TheWordPoint works with each authoring tool, one concept underlies all of them: XLIFF and translation memory together determine whether translating a 200-slide course takes 2 days or 2 weeks, and whether a course library update costs the same as the original translation or a fraction of it.

What XLIFF does: XLIFF (XML Localisation Interchange File Format) separates every translatable text segment in your course from the surrounding design, interactivity, and media. The result is a structured XML file where each source segment is paired with its target translation — without any risk of accidentally triggering Storyline triggers, breaking Captivate variables, or corrupting branching logic during the editing process.

Without XLIFF: A translator edits text directly within the authoring tool, slide by slide, manually navigating 200 slides, risking broken triggers and animations with each edit, with no translation memory applied.

With XLIFF: All 200 slides' text is in one structured file. CAT tools apply translation memory automatically — a segment that appeared in a previous course version or in a related course is pre-translated and flagged for review rather than retranslated from scratch. Terminology consistency is enforced automatically via the project glossary. Reimport to the authoring tool takes minutes.

Translation memory (TM) for e-learning libraries: For organizations with ongoing course development, TM is the mechanism that makes maintaining a multilingual course library economically viable. Every new course added to the library benefits from TM matches against all previously translated content — standard navigation text, legal disclaimers, recurring instructional patterns, boilerplate compliance language. On course update projects where 30–40% of content is unchanged, TM leverage typically reduces translation cost by 25–40% compared to full retranslation.

CAT tools TheWordPoint uses: SDL Trados Studio · memoQ · Phrase (Memsource). All handle XLIFF natively. All maintain client-specific TM and glossary. TM leverage reports generated at project start for transparent update pricing.

Authoring Tool Translation Workflows — How TheWordPoint Works With Each

Articulate Storyline and Rise 360

XLIFF workflow: Storyline 360 supports native XLIFF export via File > Export for Translation. All course text — slides, quiz questions and answer options, feedback text, timeline captions, menu and navigation labels — exports as a single XLIFF. TheWordPoint translates with CAT tool TM applied, returns the translated XLIFF for reimport via File > Import Translation. All interactivity (triggers, states, layers, animations, branching), media, and design elements remain untouched in the .story source file.

Articulate Rise 360: Rise exports XLIFF containing all lesson content, block text, and quiz content. Translated XLIFF reimports cleanly. Rise's responsive block layout self-adjusts to translated text length without DTP intervention in most cases.

Output: Translated course published from .story or Rise in SCORM 1.2, SCORM 2004, xAPI, or HTML5 — identical publish settings to the source course.

→ What content types are translated within Storyline courses (quizzes, branching scenarios, compliance content)

Adobe Captivate

Source file workflow: Adobe Captivate stores all course content in the .cptx project file, which is a ZIP archive containing XML files for each slide and course element. TheWordPoint extracts translatable XML from the .cptx, translates using CAT tools with TM and glossary applied, and reinserts translated content into the source file for republication.

Captivate-specific considerations: Software simulations (screen recordings with instructional overlays): UI labels, tooltip text, and instruction overlays translated within the simulation without re-recording. Fluid Box responsive layouts: text area boundaries checked post-reimport and adjusted where German, French, or Spanish text expansion affects the responsive layout. Branching question slides and scored interactions: all branches and all scored items translated with full path verification.

Output: Translated .cptx republished in SCORM 1.2, SCORM 2004, xAPI, or HTML5.

iSpring Suite

PowerPoint-based XLIFF workflow: iSpring courses are authored in Microsoft PowerPoint with iSpring's quiz and interaction layer. iSpring Converter Pro provides XLIFF export of all course text. TheWordPoint translates the XLIFF and returns for reimport, which populates translated text back into the PowerPoint source. The PowerPoint is then republished through iSpring.

iSpring-specific considerations: PowerPoint text box behaviour: unlike Storyline's text fitting, PowerPoint text boxes may overflow on reimport when target language text is longer. Overflow is reviewed and adjusted in PowerPoint before republication. iSpring's built-in text-to-speech (50+ languages): available as a fast, lower-cost narration option for translated courses where full voiceover recording is not required. Quiz integration: iSpring's native quiz builder exports quiz content in the XLIFF — all question types (multiple choice, true/false, drag-and-drop, fill-in-the-blank) translated within the XLIFF workflow.

Lectora

Native XLIFF translation: Lectora (ELB Learning) supports XLIFF export and import as a built-in feature: File > Export > Export Translation / File > Import > Import Translation. All text elements — text blocks, button labels, quiz items, variable values, and reference fields — are included in the XLIFF export.

Lectora-specific considerations: Section 508 and WCAG accessibility: Lectora's accessibility attributes (alt text, tab order, object descriptions) are part of the source file and carry into the translated course — TheWordPoint translates alt text and accessible descriptions alongside main content. Conditional text and variables: Lectora supports adaptive paths via conditional text and variable values. Variable values in the XLIFF are translated with awareness of their conditional function — they are not translated as standalone text but in context of their branching role.

Elucidat

Localization workflow: Elucidat provides built-in localization export, generating a structured text file for each language. TheWordPoint receives the Elucidat text export, translates using CAT tools with TM, and returns for import into Elucidat's localization interface. Elucidat's template-based authoring means translated content inherits all layout formatting automatically — text expansion is managed within Elucidat's responsive block engine.

GOMO

Multi-language export/import: GOMO's cloud-based authoring platform supports multi-language course creation with its own structured text export. TheWordPoint translates GOMO exports and returns for import into the GOMO course management interface. GOMO's responsive adaptive layout handles text length variation across languages without manual DTP.

LMS Platform Delivery — How Translated Courses Land in Your Learning Management System

Translating course content is half the workflow. The other half is ensuring the translated SCORM package (or native LMS content) uploads correctly, tracks completions accurately, and integrates with the LMS's multilingual learner management system.

Enterprise corporate LMS platforms:

Cornerstone OnDemand. The most widely deployed enterprise LMS globally. Cornerstone manages multilingual courses via language tracks — each language version uploaded as a separate SCORM package in the Course Catalog, assigned to learners based on their profile's language preference. TheWordPoint delivers translated SCORM 1.2 or SCORM 2004 packages tested for Cornerstone compatibility. Completion tracking, quiz scoring, and certification requirements are preserved in each language package.

Docebo. Enterprise LMS with course branching and AI features. Translated SCORM packages uploaded to Docebo's Content Library. Multilingual learner assignment managed via Docebo's branch or group structure. SCORM 2004 preferred for xAPI-equivalent tracking in Docebo.

TalentLMS. Mid-market corporate LMS. SCORM 1.2 and SCORM 2004 upload supported. Multilingual course delivery managed via TalentLMS's branch structure with language-based learner groups.

SAP SuccessFactors Learning. Integrated with SAP HCM. SCORM 1.2 is the primary upload format for SuccessFactors. Translated SCORM packages uploaded as new Items in the Learning catalog with language-coded assignment.

360Learning. Collaborative learning platform with native multilingual content support. Supports SCORM upload for externally authored content alongside native 360Learning content translation workflows.

Academic and open-source LMS:

Moodle. Three workflows depending on course structure:

1. SCORM package from an authoring tool → upload as a SCORM Activity
2. Native Moodle content (lessons, quizzes, pages) → XLIFF via multilingual plugin
3. Multi-language filter → translated content blocks inserted per language preference

Canvas. SCORM package upload via the Canvas New Quizzes/Modules structure. Canvas's built-in translation feature (for native Canvas content) is supplemented by TheWordPoint's content translation where human accuracy is required.

Blackboard. SCORM 1.2 and 2004 package upload via the Content area. Multilingual course management via separate course shells per language.

Translation Management Systems for Enterprise E-Learning Libraries

For businesses and organizations managing ongoing multilingual course libraries — dozens of courses, multiple languages, continuous update cycles — a Translation Management System (TMS) automates the workflow that would otherwise require manual file management for every project.

What a TMS provides for e-learning translation:

Automated XLIFF processing: XLIFF files uploaded to the TMS are automatically parsed into translation segments, matched against the organization's TM, and routed to translators with TM-matched segments pre-populated.

Real-time TM leverage reporting: Before translation begins, the TMS generates a segment-level report showing how much of the new course is covered by existing TM from the course library — enabling accurate per-project pricing based on actual leverage, not estimates.

Terminology enforcement: The client's approved e-learning glossary is integrated into the TMS and enforced at the translation stage — translators are flagged if a term in the glossary is not used correctly in context.

Workflow automation: Translation → review → DTP → delivery stages managed through the TMS, with automated file routing between stages and deadline tracking.

Version control for course updates: When an existing course is updated, the TMS identifies exactly which segments have changed from the previously translated version, routing only changed segments to translators rather than the entire course.

TMS platforms TheWordPoint uses: Phrase (formerly Memsource) · memoQ Server · XTM Cloud · SDL GroupShare

For enterprise clients with large ongoing course libraries, TheWordPoint establishes a dedicated TMS project space per client organization with accumulated TM across all courses, enabling compounding TM savings that grow with every course added to the library.

Standard XML and XLIFF conventions for LMS export: For organizations building their own content management pipelines for LMS content, TheWordPoint works with XLIFF 1.2 and XLIFF 2.0, generic XML with documented element mapping, and proprietary formats (assessed case-by-case).

How the Authoring Tool Translation Workflow Works — Step by Step

• Export from your authoring tool. Storyline: File > Export for Translation > XLIFF. Lectora: File > Export > Export Translation. iSpring: Converter Pro > Export for Translation. Captivate: Provide .cptx source file — TheWordPoint handles extraction. Elucidat/GOMO: Use platform's localization export.
• Submit XLIFF and source files. Upload at thewordpoint.com/business-free-quote. Specify: tool and version, LMS target and SCORM version, target language(s), any existing TM or glossary, compliance deadline if applicable.
• TM matching and project setup. XLIFF parsed in CAT tool. TM applied — existing matched segments pre-populated. Leverage report generated. Client glossary activated.
• Subject matter expert translation and QA review. Translation by domain-specialist native-speaker translator. QA by second linguist. Glossary adherence and segment consistency verified. All quiz pathways complete.
• Reimport and DTP review. Translated XLIFF reimported into authoring tool. Text expansion reviewed. DTP adjustments made where needed. SCORM package published and tested.
• LMS-ready delivery. Translated SCORM package delivered for LMS upload. TM updated with new translations. LMS platform delivery guidance provided for your specific platform.

Reviewed and updated  on August 25, 2026, by

Christakis Christodoulou