Forum Discussion
localization strategy and variables
I have Update 6: 1407.2208
Part of our localization strategy is as follows, a simple
version:
Create a course in Storyline with English content
English.story
Make a copy of that .story file;...
Hi Ashley -
You'll want to move all of these to the root folder along with your index file. Edit the imsmanifest.xml file (or open it up in something like the reload editor) to direct your SCO to your new initial launch file if you change your initial launch file from the default index_lms.html. Otherwise, make your "SCO chooser" and name that index_lms.html.
No need to delete files out of the sub-folders. Most LMS won't care that they're there. You can just leave those in place unless your LMS freaks out (should be rare, most are pretty sensible when it comes to scorm configuration files).
Thank you, Steve! I really appreciate your knowledge and you taking the time to try to help :-D
Sooooo I've done all this - copied those files into the root folder, left the files in each of the sub-folders, and have 13 sub-folders, and made an index_lms.html to launch the different languages based on the one from your original example.
when I test my SCO launcher index_lms.html I get this error:
JavaScript
An error has occurred:
Error - unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support.
Press 'OK' to view debug information to send to technical support.
Does it look like I'm doing something blatantly wrong? Or is that just because I'm trying to test it locally? Loading it into an LMS might still work?
(Thank you!)
