That is possible. You'd need to start the course with a screen that lets the user choose a language. Put that value into a variable, and use that variable to control what language is shown to the user.
The different languages could be presented in different scenes, so, based on the value of the variable, the Next button would advance to the appropriate scene.
Another option would be to use separate states for objects with text, e.g., have a French state, a Spanish state, etc. Then use the value of the variable to show the appropriate state.
You'll need to use variables and conditions. It's worth learning about those, because they provide the real power in Storyline. These User Guide articles will get you started:
I have a Language variable that is set at the beginning of the course and then each object has mutliple states to reflect the language. What I find works is that If I have the Normal state as English, use the built-in states of Drop Correct and Visited, and then duplicate Normal for a state for each language, the language states adopt the formatting for Drop Correct and Visited. This is without having to have a state for each language and each built-in state, e.g. Chinese Visited, etc. My question is why does this not work for Hover and Selected states?
Thanks for sharing your solution. I want to take a look at a sample slide in a .story file to investigate what's happening with your permission. You can share it publicly here or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
You're referring to built-in states, which are typically built off of your Normal state. Since you have custom states in the mix, I recommend removing the text off of the problematic states you mentioned.
I've edited your first two boxes, With Selected state and With Visited state, on your first slide. I also included a 2nd slide with a visual example of how the built-in states behave.
Anther one of your wonderful supprt people came up with a solution. Create each language state by duplicating the Normal state. Then refresh the built-in state if it is not retaining the formatting when you select or Visit, etc. You guys provide excellent support, many thanks.
7 Replies
Hi, Maryam,
That is possible. You'd need to start the course with a screen that lets the user choose a language. Put that value into a variable, and use that variable to control what language is shown to the user.
The different languages could be presented in different scenes, so, based on the value of the variable, the Next button would advance to the appropriate scene.
Another option would be to use separate states for objects with text, e.g., have a French state, a Spanish state, etc. Then use the value of the variable to show the appropriate state.
You'll need to use variables and conditions. It's worth learning about those, because they provide the real power in Storyline. These User Guide articles will get you started:
I have a Language variable that is set at the beginning of the course and then each object has mutliple states to reflect the language. What I find works is that If I have the Normal state as English, use the built-in states of Drop Correct and Visited, and then duplicate Normal for a state for each language, the language states adopt the formatting for Drop Correct and Visited. This is without having to have a state for each language and each built-in state, e.g. Chinese Visited, etc. My question is why does this not work for Hover and Selected states?
Hi Gael,
Thanks for sharing your solution. I want to take a look at a sample slide in a .story file to investigate what's happening with your permission. You can share it publicly here or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
I created this to demonstrate.
Thanks for sharing a sample.
You're referring to built-in states, which are typically built off of your Normal state. Since you have custom states in the mix, I recommend removing the text off of the problematic states you mentioned.
I've edited your first two boxes, With Selected state and With Visited state, on your first slide. I also included a 2nd slide with a visual example of how the built-in states behave.
Anther one of your wonderful supprt people came up with a solution. Create each language state by duplicating the Normal state. Then refresh the built-in state if it is not retaining the formatting when you select or Visit, etc. You guys provide excellent support, many thanks.
Thanks, Gael. I did not realize you were working with the support team as well. I'm glad Luiza was able to help.