Building Multiple Language Versions in One Course?

Scale is a consideration. Smaller modules with few alternate languages might be perfectly manageable in a single Storyline file. In my experience, the easiest way to handle larger courses is to:

1) Build in a primary language. course-english.story

2) Use translation tools to build alternate packages. course-spanish.story, course-russian.story, course-german.story

3) Publish each course out to a separate SCORM module. Copy each module into a folder that clearly indicates the language.

4) Assemble them all into one SCO by creating a manifest (you could simply copy the manifest files from your primary publish) and pointing this manifest to launch an index.html file that links to a specific language. The LMS will launch this "Menu" and then the participant will receive a payload of the Storyline file in the selected language.

There are a couple of advantages to this. First, it's actually a little easier to manage. You're working and publishing X number of separate simpler files than one monster. Second, it's less wasteful in bandwidth. Since it only loads a single published output instead of all of the languages. Plus each language can have a localized interface. This is described a bit here:

https://community.articulate.com/discussions/articulate-storyline/localization-strategy-and-variables#reply-190324