localization strategy and variables

Hi, Julie - 

Multi-language in a single package pokes at the edges of the use cases for which the tool is designed. Most tools have trouble with this type of configuration. There are some options, depending on how your packages are built. Does your localization extend to images, video, or audio?

I've recently tackled a couple of projects with this workflow:

• Publish a single storyline file containing text blocks containing variable references.
• Build an Excel file with column headers that correspond to Storyline variables. 
• Use a VBA script to generate a JSON data file with all of the variable contents.
• Build a Javascript trigger to dynamically load the JSON data into the Storyline file on cue. 
• In my case, also make copies of the Storyline publish, create new folders, automatically edit the imsmanifest file, copy in a few dependencies, and automatically zip the contents of the newly generated file into a named Zip / SCO package. 

I'm able to generate 100 individual SCORM packages, each with a custom title and "variable payload" through the automated script in less time than it takes Storyline to publish the origin file. It's possible to go quite a few directions with this kind of an automation and run-time load method.