Forum Discussion
Opening previous localization products
We often have to translate for grant requirements. We paid big bucks to localize a big project to several languages in one file for each lesson so it would be smooth operation in the student portal (folks just choose from a dropdown if they need another language). The payment period is over, so we no longer have localization credits (which is also annoying because we had a long involved review process that made us "lose" a lot - these should not have a time limit on them). Now, we have received an "issue" that I wanted to look at the file for (more about the SCORM settings than actual edits, but those are surely coming after we launch this to the test group). Now, if I try to open that Storyline file, I get the message below: "You need Articulate Localization to open this project. Alternatively, you can save each language as its own file to access them. Would you like to save them as a separate project files now?" Seriously - are we going to need to save and fix every language separately if we have any edits?
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.
4 Replies
Hi DeLoraReardon​,
I'm sorry to hear that you've run into this setback with Storyline Localization!
The multi-language Storyline file you've created is tied to the Articulate Localization feature. When a project contains languages managed through Localization, Storyline requires Localization access to open the file in that multi-language format. I see that Localization is currently inactive for your Teams subscription.
The option Storyline is offering, to save each language as its own project file, detaches the languages from the Localization workflow. Once they're saved as separate .story files, you'll be able to open and edit them normally. However, any future updates can only be applied to each language file individually. If you expect necessary future updates and prefer to keep everything managed in a single project, re-enabling your Localization subscription is required.
Please let me know if you have any more questions!
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.
Thank you for these ideas. I appreciate the response. We do have access to a good programmer but the scale and short deadlines on this particular project may not be feasible this time, but a possible solution for future projects. Yes, the second solution is probably the route we will end up going. We have had separate language courses in the past, but it was confusing for some participants and does make a bit cumbersome when each has to be edited. I was excited about the idea of everything in one file for those reasons, but I guess that will not be what we can do.
