In order to launch a global elearning campaign, I should make a choice between creating one package in different languages or individually creating multiple packages for languages.
Anyone knows if end user would spend more time loading a package developed in multiple languages?
I am assuming that the file size of the package in multiple languages is greater than the individual package in single language so that end users are more likely to experience issues in bigger package.
What are the best practices to produce an elearning package for global use?
I will definitely go with individual packages for different languages. Here are my reasons.
1. Small file size, smoother loading.
2. Much easier to develop individual packages than a single package in multiple languages. Don't forget not only the content needs to be localized, but also all the navigators such as next/previous buttons, menu, resources.
3. Easier to go through localization quality testing, and fasten the developing process. Once the first version got approval, of course you can have multiple translations go at the same time. But you will only able to edit the story files together when they're individual files. I assume that different languages might need different editors or different reviewers.
4. Easier for maintainence. Same reason as points 2&3.
And if you need to deliver multiple languages packages to same sites, I mean if you want end users to be able to choose the language they like, you can just create a home file links to different languages packages. And users can click the link and only download the language version file they chose.
There should not be any problems with loading as Storyline and Presenter only ever load 3 slides ahead
That said I would produce languages in different courses as you cannot change the player language except on a course level and it will be easier to manage and translate.
2 Replies
I will definitely go with individual packages for different languages. Here are my reasons.
1. Small file size, smoother loading.
2. Much easier to develop individual packages than a single package in multiple languages. Don't forget not only the content needs to be localized, but also all the navigators such as next/previous buttons, menu, resources.
3. Easier to go through localization quality testing, and fasten the developing process. Once the first version got approval, of course you can have multiple translations go at the same time. But you will only able to edit the story files together when they're individual files. I assume that different languages might need different editors or different reviewers.
4. Easier for maintainence. Same reason as points 2&3.
And if you need to deliver multiple languages packages to same sites, I mean if you want end users to be able to choose the language they like, you can just create a home file links to different languages packages. And users can click the link and only download the language version file they chose.
There should not be any problems with loading as Storyline and Presenter only ever load 3 slides ahead
That said I would produce languages in different courses as you cannot change the player language except on a course level and it will be easier to manage and translate.
This discussion is closed. You can start a new discussion or contact Articulate Support.