Forum Discussion
Opening previous localization products
Here's a good solution I've seen for translated courses:
- Create a separate source file for each language.
- Publish each as a SCORM package.
- Have someone with the proper coding skills "wrap" those packages into one big SCORM package, with a starting page that allows the user to select a language. (Unfortunately, I don't have any recommendations about who does that sort of programming.)
- Load the big SCORM package into the LMS.
Another option I've seen also involves publishing a separate SCORM package for each language. Those are then bundled into a curriculum within an LMS, with the settings adjusted so that the user only has to complete one of the courses to finish the curriculum. Of course, being able to do this depends on the LMS.
Thanks. I guess we should have looked into this previously. We will now have to separate our portal into various languages. Our "limited time period grants" make this a hard sell for future projects between the restrictions on time use and the taking away of convenience of one file.
Here's a good solution I've seen for translated courses:
- Create a separate source file for each language.
- Publish each as a SCORM package.
- Have someone with the proper coding skills "wrap" those packages into one big SCORM package, with a starting page that allows the user to select a language. (Unfortunately, I don't have any recommendations about who does that sort of programming.)
- Load the big SCORM package into the LMS.
Another option I've seen also involves publishing a separate SCORM package for each language. Those are then bundled into a curriculum within an LMS, with the settings adjusted so that the user only has to complete one of the courses to finish the curriculum. Of course, being able to do this depends on the LMS.