localization strategy and variables

Hey David,

This is actually fairly simple but isn't without a drawback. In the attached example, I created two language folders with the LMS publish from each one with the exception of the manifest files. In the base of the directory, I added an index_lms.html file that links to each language. The drawback is the student will have to select their language each time they resume. The upside is that no matter what language they select it will restore to the same location, provided that the published structures are identical.

To do this, I published one of the outputs (you may want to title it in a way that makes sense for the whole course) then published each language to LMS / SCORM.

In my main folder, I deleted the content files leaving these in the base folder:

• adlcp_rootv1p2.xsd
• ims_xml.xsd
• imsp_rootv1p1p2.xsd
• imsmanifest.xml
• imsmd_rootv1p2p1.xsd

I created folders for each language in the base folder:

• English
• Spanish
• ...

Then I created a simple HTML file named index_lms.html in the base folder with links to each language and zipped the whole thing with imsmanifest at the base of the zip. The links are simple relative links. These link to the content in the folder and begin the LMS initialization.

In my tests, everything worked well. If your LMS throws errors on a timer if the LMSAPI doesn't initialize it could throw a wrench in the mix. Try a test with the attached SCO to see how it works.